Payment links

The simplest integration: a secure checkout URL you share by email, message or in a client space. No code. What a link can do, and what the traveler sees.

Checked against the API code on October 13, 2026

A payment link is a checkout page attached to a booking. You create it in the app in a few clicks, copy its URL and send it however you like: email, WhatsApp, a quote, or the traveler's client space.

Text
https://app.ezuspay.io/lnk/your-agency/8K3QZ7M2XR4T

The last segment is a random 12-character token. Anyone holding the URL can open the checkout, so share it only with the people who pay.

OptionWhat it does
AmountFrom 1 unit up to 999,999.99, in the booking's currency
LabelShown to the traveler, for example "Deposit 30%"
Payment methodsCard, SEPA Direct Debit, or both. SEPA is available in EUR
Expiry datePast that date, the link can no longer be paid
Reusable linkCan be paid several times, by several people. Each payment records the payer's name
Checkout fieldsQuestions the traveler answers before paying: passport, dietary needs, room type… Up to 10, 7 field types

A payment plan uses the same kind of URL. The page then shows the full schedule, and the link always collects the installment that is due.

What the traveler sees

  1. A summary of the trip: dates, number of travelers, the amount and your pre-payment message. A checkbox to accept your terms (a PDF you upload, or a link to your page).
  2. Your questions, if the link has checkout fields.
  3. The payment form, handled by Stripe. 3D Secure runs on every card payment. Apple Pay and Google Pay appear on devices that support them.

The page carries your logo and colors. It is available in 8 languages: French, English, Spanish, Italian, Portuguese, German, Dutch and Norwegian. You choose which ones are offered, and the traveler switches with a menu. The traveler never creates an account.

On the traveler's bank statement, a card payment shows EZUS* followed by your agency name, or the label you set in your settings.

After the payment

  • The traveler gets a confirmation email, in the language they paid in.
  • The payment is attached to the booking and the amount due is updated.
  • A single-use link becomes Paid. A reusable link stays open.
  • Your webhooks receive payment.succeeded, then booking.fully_paid if the booking is now fully paid.

A SEPA debit takes several working days to be confirmed. The page tells the traveler the payment is in progress, and the webhook arrives once Stripe confirms it.

Everything above is also available through the API, with POST /v1/bookings/:id/payment-links. The response contains checkoutUrl, ready to send. See the API reference.

To show the checkout on your own website instead of sending a URL, see Embedded checkout.