PMS Integration

Connect your Property Management System to TurnStay to accept guest payments, process virtual card charges, handle refunds, and store cards for returning guests.

Integration types

Hosted Payments

Accept guest payments through TurnStay’s hosted checkout page. Create a payment intent from your PMS, redirect the guest to the payment URL, and receive a webhook when payment is complete.

• No PCI scope — card details are handled entirely by TurnStay.
• Supports all card brands and local payment methods.
• Customizable redirect URLs for success and failure.

Get started with Hosted Payments →

---

Virtual Card (S2S)

Charge virtual cards issued by OTAs (Booking.com, Expedia, etc.) server-to-server. Your PMS submits the virtual card details directly to the Secure Card Service — they never pass through the TurnStay API.

• Set payment_type to "Virtual Card" when creating the payment intent.
• Card details are submitted to the confirm_endpoint_url returned by SCS.
• Processing currency must match the virtual card currency.

Learn about Server-to-Server payments →

---

Refund

Issue full or partial refunds for completed payments. TurnStay routes refunds back through the original payment provider. For bank deposit payments, the customer submits their bank details and the payout is disbursed automatically.

• Card refunds go back to the original card.
• Bank deposit refunds collect customer bank details and disburse via the payouts service.
• Use idempotency_key to prevent duplicate refunds.

Refund integration guide →

---

Card on File

Save a guest’s card during their first stay and charge it for future bookings without re-entering details. Tokenization happens via a hosted form or server-to-server — card data is stored in the Secure Card Service, never in the TurnStay API.

• Create a Payment Method Token Intent to start tokenization.
• Use the returned card_token on future payment intents.
• Supports both hosted form and S2S flows.

Card on File guide →