Setup and testing
This page covers everything you need to get your Apaleo Pay integration running in a test environment and verify it works correctly before going live.
Prerequisites
- An Apaleo developer account. Create one free here if you do not have one yet.
- Your app registered in Apaleo (either a connect app or a simple client).
Apaleo Pay is pre-configured on every developer account. There is nothing to configure on your side — no separate Adyen environment or merchant account setup is required.
Add Adyen Drop-in to your checkout page
Apaleo Pay uses Adyen’s Drop-in component to render the payment form and securely collect card details from the guest. You integrate Drop-in directly into your checkout page.
Follow the Adyen Drop-in integration guide to add it to your web page. Drop-in handles card encryption, 3D Secure challenges, and alternative payment methods out of the box.
When initialising Drop-in, you will need the Client Key and the Checkout URL from the test credentials below.
Test credentials
Use the following credentials to test your integration against the Apaleo Pay sandbox.
Online payments
| Field | Description | Value |
|---|---|---|
| Merchant Account | The company-level merchant account. | ApaleoGmbHCOM |
| Sub-merchant ID | The property-level identifier used in every payment request. | CWWVG78PRG8AWNK |
| Checkout URL | The test checkout endpoint. Format: https://checkout-test.adyen.com/[version]/[method] |
https://checkout-test.adyen.com/checkout/V52/payments |
| API Key | Used to authenticate server-side API requests to Adyen. | AQEshmfxLoLNaxZBw0m/n3Q5qf3VaZtMAZZFf2hU7t5zpA3osDxUhMnBXPo7mA8QwV1bDb7kfNy1WIxIIkxgBw==-QntgDhQ4FG0tGiMbnfX1KdPl6u4Fg/tHwAas6p5aJ8c=-L4KdmwfD7T6EKyNQ |
| Client Key | A public key used to initialise Adyen Drop-in on the client side. | test_MW2GQ44S2VGYXNSZDK52HLAZTIW73AQB |
| Web Service User | The web service user for your account. | ws_183033@Company.ApaleoGmbH |
| Allowed Origins | The domain(s) from which client-side requests are accepted. HTTP is allowed in test; HTTPS is required in production. If you are using a domain other than http://localhost:8080, contact support@apaleo.com to whitelist it. |
http://localhost:8080 |
Test credit cards
Adyen provides a full list of test card numbers in their documentation. The most commonly used ones for Apaleo Pay testing are:
| Scenario | Card number | CVC | Expiry |
|---|---|---|---|
| With CVC | 4111 1111 1111 1111 |
737 |
03/2030 |
| Without CVC | 4111 1111 4555 1142 |
— | 03/2030 |
What to test
Before going live, verify the following scenarios against the sandbox:
- Add a payment account to a reservation or booking.
- Trigger a payment for a reservation folio using the payment account stored on the reservation.
- Make a prepay booking through the IBE and confirm that the payment account is stored on the reservation and the prepayment amount is automatically captured.
Next step — go live
Once you are confident your integration works correctly in the sandbox, contact support@apaleo.com to request your live credentials for our mutual customer. Make sure the customer is included in the email chain and provides their consent. Include the domain(s) your application runs on so Apaleo can whitelist them. You will receive:
- Merchant account per property
- Sub-merchant ID per property
- URL prefix per account
- API key per account
- Client key per account