With Orchestra, guests pay on your Booking Engine through your own payment provider (Stripe, Adyen, Worldpay and more). HotelSync never holds your money — funds settle directly in your account. Setup takes about 30 minutes.
The setup produces 4 values you will paste into HotelSync at the end:
Payment Gateway Account Name (created in Step 2) — e.g.
myHotelStripeCard Wallet Name (created in Step 3) — e.g.
card-paymentsAPI Key (created in Step 4)
Environment (chosen in Step 5) — Test or Live
Before you start, you need an account with a supported payment provider with API access (no provider yet? Step 2 includes a test option), and access to your HotelSync dashboard.
Step 1 — Create your Orchestra account
Enter your name, a username and your email. Leave "Is Sandbox" ticked.
Click the confirmation link in your email, set a password (8–16 characters), then click Activate User.
ℹ️ A sandbox account is for testing — no real money moves. You will switch to a production account in Step 7.
Step 2 — Connect your payment provider
In the Orchestra Portal, go to Payment Gateway Accounts → Create and fill in:
Name — pick any name, e.g.
myHotelStripe(3–64 letters/numbers, no spaces)Payment Gateway Name — select your provider from the list
Credentials — from your provider's dashboard. Every provider issues different ones (Stripe: secret key
sk_test_…for testing; Adyen: merchant account, username, password and company name)
Click Save.
✅ Value #1 — write down the Name you chose (e.g. myHotelStripe).
ℹ️ Providers also differ in what they support — for example, some don't offer pre-authorization, and some allow refunds only in live mode. If unsure, confirm credentials and capabilities with your provider.
💡 No payment provider yet? Create a test account instead: Name testSuccess, Gateway NULLSuccess. It approves every test payment, so you can finish setup today and connect your real provider later.
Step 3 — Create your card wallet
Go to Resources → eWallet Accounts → Add Account and fill in:
Name — e.g.
card-paymentseWallet Type —
CardPayMerchant Identifier — a unique ID in reverse-domain style, e.g.
com.yourhotel.paymentsMerchant Display Name — your hotel name (guests see this on the payment form)
Click Save.
✅ Value #2 — write down this wallet Name (e.g. card-payments).
3-D Secure (recommended — required for EU/UK cards)
Tick "Perform 3Ds?" and "I Have 3DS Merchant Details".
Enter your Merchant Url (your website).
Add one row per card brand with Bin, Brand, MCC and Merchant Id — request your 3DS merchant details (Acquirer BIN, Merchant ID and MCC, issued per card brand) from your payment provider or acquiring bank.
⚠️ Never tick "Perform 3Ds?" without filling in the merchant details rows — every 3-D Secure payment would fail. Your payment provider must also support 3-D Secure.
Step 4 — Generate your API key
Go to API Keys in the portal and create a new key.
Name it
HotelSync.Click Save and copy the key from the popup.
✅ Value #3 — the API key. It is shown only once. Treat it like a password — don't share it anywhere. If you lose it, create a new key.
Step 5 — Connect in HotelSync
In your HotelSync dashboard, open Marketplace → Orchestra Payments → Connect and fill in:
API Key — Value #3
Payment Gateway Account Name — Value #1, e.g.
myHotelStripeCard Wallet Name — Value #2, e.g.
card-paymentsEnvironment — Test (you'll switch to Live in Step 7)
Click Save, then Test Connection.
⚠️ Names must match Orchestra exactly — copy-paste them to avoid typos.
Step 6 — Make a test booking
Open your Booking Engine and make a booking.
Pay with a test card. With
testSuccessany card details work. With a real provider in test mode, test cards are specific to each provider — e.g. Stripe4242 4242 4242 4242, Adyen4111 1111 1111 1111— so check your provider's docs for their test cards and how to run test payments.Check that the payment appears in your Orchestra Portal and the booking is confirmed in HotelSync.
Step 7 — Go live
Contact Orchestra at [email protected] to upgrade to a production account.
Create a new Payment Gateway Account with your provider's live credentials (e.g.
myHotelStripeLive).Create a new API key for production.
In HotelSync, update the API Key and Payment Gateway Account Name, and switch Environment to Live.
Make one small real booking with a real card, then refund it.
Optional: add Google Pay
In the Google Pay & Wallet Console, create a business profile, register your website and wait for Google's approval.
Copy your Merchant ID.
In Orchestra, go to Resources → eWallet Accounts → Add Account: Name
google-pay, TypeGooglePay, Merchant Identifier = your Google Merchant ID, plus your display name.In HotelSync, paste
google-payinto Google Pay Wallet Name.
ℹ️ Testing works before Google approves you; live payments need approval and a 3-D-Secure-capable provider. The button only appears on supported devices (Chrome, Android).
Optional: add Apple Pay
Requires an Apple Developer Program membership ($99/year).
In the Apple Developer portal, create a Merchant ID (e.g.
merchant.com.yourhotel).Verify the domain your Booking Engine runs on. Apple gives you a verification file that must be placed on that domain — contact HotelSync support and we will host it for you.
Create the Payment Processing and Merchant Identity certificates and convert them to PEM format (exact commands in Orchestra's Apple Pay guide).
In Orchestra, add a wallet: Name
apple-pay, TypeApplePay, with your Merchant ID, display name, domain and the four certificate/key PEM values.In HotelSync, paste
apple-payinto Apple Pay Wallet Name.
ℹ️ The button only appears in Safari on Apple devices.
Optional: add PayPal
With a PayPal Business account, sign in to the PayPal Developer Dashboard.
Under Apps & Credentials, create a Merchant app (Sandbox for testing, Live for production).
Copy the Client ID and Secret.
In Orchestra, add a wallet: Name
paypal, TypePayPal, Merchant Identifier = Client ID, Secret = Secret.In HotelSync, paste
paypalinto PayPal Wallet Name.
Troubleshooting
"Test Connection" fails — API key pasted wrong or revoked. Create a new key and paste it again.
Environment mismatch warning — a sandbox account works only with Test; a production account only with Live.
Payment buttons don't appear — wallet names in HotelSync must match the names in Orchestra exactly.
Every 3-D Secure payment fails — "Perform 3Ds?" is enabled but merchant details are missing. Complete Step 3 or untick it.
Payments rejected — check your provider credentials in Orchestra, and don't use real cards in Test or test cards in Live.
Google Pay / Apple Pay button missing — normal: these buttons only show on supported browsers and devices.
Need help?
Orchestra account or portal: [email protected] · developers.orchestrasolutions.com Your Booking Engine or the HotelSync connection: message us in the chat — we're happy to help.
