What has been verified
Running against the provider’s production API.
Integrations
Stripe payments tied to the booking that produced them
Boris creates the charge from the booking, follows it through Stripe webhooks and writes the result back onto the reservation, so the payment status you see in the calendar is the one Stripe holds.
Integration status
Provider website ↗
Available Running against the provider’s production API.
Technical page reviewed
Integration status
Requires an active provider account, credentials and any plan required by the provider.
The workflow and limitations documented on this page are the supported scope; validate it with test data before production.
What it gives you
Charge from the booking
Deposits, balances and full payments are raised against a reservation, not typed into a separate dashboard.
Status that stays true
Stripe webhooks update the reservation, so paid, pending and failed mean the same thing on both sides.
Reconciliation without exports
Every payment keeps its booking, customer and invoice reference for the end of the month.
How to connect it
- 1
Add your Stripe keys in Integrations and register the webhook endpoint in one click.
- 2
Choose when Boris charges: at booking, at check-in or on a payment link you send.
- 3
Let Stripe confirm the payment while Boris updates the reservation and the invoice.
Frequently asked questions
Does Boris store card numbers?
No. Cards are handled by Stripe; Boris keeps the payment reference and its status, never the card data.
Can I take a deposit now and the balance later?
Yes. A booking can carry more than one payment, each with its own amount, moment and status.
Related integrations
Connect it to your own space
Create a workspace, add your resources and connect the tools you already pay for. No credit card required.
Create your workspace