Those who made the effort of implementing Stripe into their software can now pass the payment token to Cloudbeds in order to enable subsequent charges, lessen the guest and staff effort, wave goodbye to manual entry mistakes and send payment data without compromising PCI compliance.
Use case example
A custom built booking engine takes a deposit during the booking process and stores the card securely in Stripe account.
Reservation is posted into Cloudbeds together with the Stripe token. Cloudbeds account is connected to the same Stripe account.
Guest can now pay for the rest of the stay during the check-in without presenting the card again.
Customer token
To save a credit card for further reuse, you must, before anything else, tokenize a credit card. This can be done on Stripe backend API itself, but using Stripe JavaScript SDK (or iOS SDK or Android SDK) to tokenize the credit card directly without submitting the credit card data to your backend is most recommended.
After tokenization, you can use it to create a customer or attach it to an existing customer. This guide covers this approach.
Charge token
A charge represents the final object generated by a payment. There are many ways to create a charge, such as the old Charge API itself, but currently using a Payment Intent is the most recommended approach as it’ll allow you to deal with authenticated payment flows (3D Secure, for example).
In the case of a Payment Intent usage, the Charge is created after the payment is confirmed and the authentication is either dismissed or fulfilled.
Important: Deposit rules
The rules described on Manage > Payment Options > Processing Methods > Mybooking Reservations are NOT APPLIED to reservations created via the API.
It means that if a cardToken
is sent, the deposit won't be charged. The payment needs to be added manually in the reservation.
Comments
0 comments
Please sign in to leave a comment.