Verify the payment for a reservation created with instant charge. When the /instant-charge endpoint is called with initialPaymentMethodId (for GuestyPay, MerchantWarrior or HYP payment providers) and the returned payment has status PENDING_AUTH, this endpoint validates whether the 3DS challenge was successful for the cardholder. If the 3DS verification succeeds, the payment is charged and the reservation is confirmed. If the verification fails, the reservation is closed. The initialPaymentMethodId is created using our dedicated tokenization endpoint. This endpoint is used after the frontend completes the 3DS challenge flow initiated by the threeDSChallenge response from the /instant-charge endpoint..
Important
Before using the Booking Engine (BE) API reservation endpoints, ensure your Guesty account is properly activated by following these steps:
- Activate Manual Source (skip this step if you already have direct reservations in Guesty account):
- Create a manual reservation directly in the Guesty UI. This step is required to activate the "Manual" booking source in your account.
- Activate BE API Source:
- Create your first reservation using the Booking Engine API endpoints.
- This step is essential to initialize the BE API source, which allows you to set up additional fees, taxes, auto payments and automated messages.