PSP integration
Atlantic AI can connect regional and local payment providers to the hospitality payment backbone. Your hotel remains the direct PSP merchant account holder and requests the required technical information from your PSP.
Before technical review
- Merchant relationship Your hotel remains the direct PSP account holder. Atlantic AI does not request merchant-only documentation on your behalf.
- Technical documentation Please request API docs, hosted checkout details, callback and webhook documentation directly from your PSP.
- Sandbox access Test credentials or sandbox environment are required before development starts.
- Technical contact Please ask your PSP to provide a technical contact for integration questions.
You may share this template with your PSP
Dear PSP Team,
We are preparing to connect our hotel’s direct booking channel to our payment setup. Our technology partner for this project is Atlantic AI, which provides the hospitality integration layer for website, booking engine, PMS and payment orchestration.
Our hotel remains the direct merchant account holder with your organization. To assess and plan the technical integration, please share the following information with us.
1. Merchant agreement and access
Please confirm whether a signed merchant agreement is required before technical documentation or sandbox access can be shared.
Please also confirm whether sandbox or test access is available and who the technical integration contact person or team is.
2. Checkout model
Which payment flow options do you support for online hotel bookings: hosted payment page / redirect, embedded payment iFrame, direct API checkout, or another model?
Which option do you recommend for a hotel direct booking website?
3. Payment session creation and reference fields
How is a payment session or transaction created?
Which request fields are required and which optional fields can be included?
Examples may include amount, currency, booking reference, guest name, guest email and metadata / custom reference fields.
Please also confirm whether our booking or payment session ID can be submitted as merchant reference, the maximum allowed length, supported characters, whether multiple custom reference or metadata fields can be submitted, and whether those values are returned unchanged.
4. Payment confirmation, redirect and callback
How is successful payment confirmed?
Do you support browser redirect URLs, server callbacks and/or webhooks?
Please confirm exactly which data fields are returned after payment, including payment status, transaction ID, merchant reference, session ID, amount, currency, authorization code, guest email and timestamp where available.
Please confirm whether merchant reference or session ID values are returned unchanged.
If webhooks are supported, please share event types, payload structure, retry behaviour, signature / authentication method and expected response requirements.
Please also confirm how duplicate callbacks or retry events are handled.
5. Settlement
Please confirm settlement timing, supported settlement currencies, merchant fee structure and any reserve or holdback arrangements.
6. Security and compliance
Please confirm 3D Secure support, SCA support where applicable, and PCI requirements for merchant websites.
7. Technical documentation and sample payloads
Please share API documentation, hosted checkout / iFrame documentation, webhook documentation, sandbox credentials, test cards or test wallets, and any integration guides or sample requests.
Please also include sample JSON payloads where available, especially payment session creation request, payment session creation response, successful payment callback or redirect response, webhook event payload for successful payment, webhook event payload for failed or cancelled payment, and refund or payment reversal response if supported.
If authentication headers, signatures or idempotency keys are required, please include sample requests showing the expected format.
Thank you very much.
Best regards,
[Hotel name]