Ezus integration
Connect Ezus Pay to Ezus: your projects come in on their own, payment links go into the client space and every payment goes back to the right project.
Checked against the API code on October 13, 2026
What the connection does
Ezus is the travel software where your team builds trips and quotes. Once the two are connected:
- A project in Ezus becomes a booking in Ezus Pay, with its options (alternatives), amounts, dates and client.
- Payment links are created from Ezus and shown in the traveler's Ezus client space.
- Each payment is matched to the right project and alternative in Ezus, without anyone typing it in.
Your team keeps working in Ezus. Ezus Pay handles collection, follow-up and matching.
Connect your agency
An admin opens Settings → Integrations → Ezus in Ezus Pay and enters two things:
- the email of your Ezus account,
- your Ezus API key.
Your Ezus password is never asked for. The connection is made on your live account; test mode is never connected to Ezus.
An Ezus account can be linked to one Ezus Pay agency only. If the key is already linked to another agency, the screen tells you which one.
You can also start from Ezus: an agency already on Ezus can open Ezus Pay from its Ezus settings.
What comes from Ezus
Data flows one way, from Ezus to Ezus Pay.
| In Ezus | In Ezus Pay |
|---|---|
| Project title | Booking name |
| Client of the main alternative | Booking client (company name, or first and last name) |
| Each alternative | An alternative, with its name |
| Trip start and end dates | Departure and return dates |
| Number of travelers | Number of travelers |
| Main alternative | Main alternative |
| Current budget | Total amount to collect |
| Client space text and image | Shown on the checkout, while the client space is online |
Bookings that come from Ezus are read-only in Ezus Pay: change them in Ezus. You can still create payment links, add notes and choose the main alternative.
An alternative removed in Ezus is marked as orphan in Ezus Pay. It is never deleted, so its payments stay visible.
Each alternative keeps its own client. The person notified about a payment is the client of the alternative being paid.
When Ezus Pay reads Ezus again
- When someone opens the booking in Ezus Pay, if the last sync is more than a minute old.
- When someone opens the window to create a payment link, under the same rule.
- With the Resync button on a booking, or Sync from Ezus on the booking list.
- When Ezus creates a payment link through the API, if the booking is more than a minute old.
- Through the API:
POST /v1/bookings/:id/resync.
If the total changes in Ezus and the booking has a payment plan, the unpaid installments are recalculated.
Payments back to Ezus
Ezus Pay sends Ezus a signed event for each payment, failed payment, refund and fully paid booking. These events carry ezus_project_id and ezus_alternative_id, so Ezus attaches them to the right project. Ezus can also read payments through the API at any time.
These are the same events your own systems can receive. See Webhooks.
Your Stripe account
If your agency already collected payments through Stripe in Ezus, Ezus Pay can take over that Stripe account, with its history. This works only if you connect Ezus before you start Stripe onboarding in Ezus Pay. An agency can hold only one Stripe account.
Payments made earlier through Ezus are imported as history. They appear in your transactions with the source EZUS_LEGACY.