Ezus Pay is built on Stripe. The difference is everything around it.
Payments run on the same infrastructure: same card networks, same 3DS authentication, same PCI-DSS compliance. What separates the two is the work around the payment: tying a collection to a travel file, following the deposit and the balance, and getting all of it back into Ezus.
- Built on Stripe
- Deposit and balance per file
- No development
In short
Ezus Pay runs on Stripe's infrastructure. Both therefore collect the same way, with the same security. What separates them is the travel layer. Stripe gives you an API and a dashboard, and you build the rest. Ezus Pay ships the deposit, the balance and the automatic matching in Ezus, already done.
Ezus Pay
Ezus Pay is the right fit if…
- You want to follow deposit and balance per file without having the integration built.
- You want payments to come back into your Ezus files on their own.
- You have no technical team free to wire up an API and then maintain it.
Stripe
Stripe direct is the right fit if…
- You have a technical team and you want to keep control of the integration.
- You want to offer payment methods beyond card and SEPA transfer.
- You need all of Stripe: subscriptions, custom fraud rules, in-store payments.
Ezus Pay does not replace Stripe, it sits on top of it. If you already have a Stripe account for other collections, nothing forces you to close it.
What Stripe does not know about your files
Collecting is identical on both sides. What changes is what happens before and after the payment.
The link to the file already exists
Stripe knows how to collect an amount. It does not know that this is the balance of one specific file, or that two services are still to be paid on it.
You attach each payment to a file through the API, with metadata you define and maintain.
The deposit, the balance and custom amounts are generated from the Ezus file. Paid and outstanding update themselves.
Nothing to build, nothing to maintain
A Stripe integration is code to write, then to follow at every API change and every new edge case.
API keys, webhooks, handling failures and refunds: your team writes them and your team maintains them.
The account is already connected to Ezus. No code, no webhook to watch.
A payment page that knows the trip
Travelers often pay months before departure, and in instalments. They need to know where they stand.
Stripe Checkout takes your logo and your colors, but knows nothing about the trip: the summary and the client space are yours to build.
The traveler finds their dates, their travelers and what they have already paid, on a page in your colors and in their language.
Ezus Pay and Stripe, point by point
What each one covers for an agency selling tailor-made trips.
| Feature | Ezus Pay | Stripe |
|---|---|---|
| Collecting for a trip | ||
| Payment link ready to use | ✓ | ✓ |
| Deposit and balance followed on the same file | ✓ | ✗ |
| Extra services attached to the file | ✓ | ✗ |
| Range of payment methods | Card and transfer | Much wider |
| Tracking and accounting | ||
| Payment attached automatically to the file | ✓ | ✗ |
| Synchronization with Ezus | ✓ | ✗ |
| File status updated with no action | ✓ | ✗ |
| Accounting export | ✓ | ✓ |
| Setting up | ||
| Ready to use with no development | ✓ | ✗ |
| Ezus integration shipped and maintained | ✓ | ✗ |
| Full control of the Stripe configuration | ✗ | ✓ |
| Security | ||
| 3DS authentication (PSD2) | ✓ | ✓ |
| PCI-DSS compliance | ✓ | ✓ |
This table does not compare rates, deliberately: the two rate cards do not line up. They do not slice card types the same way, they do not cover the same bank methods — we do SEPA transfer, Stripe does direct debit — and Stripe negotiates interchange++ above a certain volume. Ask for both rate cards and compare them on your real mix of cards and amounts. To compare for yourself: Stripe's published rate card.
Ezus Pay or Stripe
Yes. Payments run on Stripe's infrastructure: card networks, 3DS authentication, PCI-DSS compliance. No card data ever passes through you or through us.
You can, and some agencies do. You then have to write the integration: attach each payment to a file, handle the webhooks, deal with failures and refunds, then maintain all of it over time. Ezus Pay ships that layer already built and connected to Ezus.
Not line by line, and it is worth saying plainly. The two rate cards do not slice card types the same way, they do not cover the same bank methods, and Stripe negotiates interchange++ above a certain volume. On our side it is 1,19 % to 1,39 % + 0,30 € on a European consumer card and 0,3 % + 0,30 € by SEPA transfer, with no subscription and no payout fees. For the rest, ask for both rate cards and compare them on your real mix.
No, since Ezus Pay sits on Stripe. If you already have a Stripe account for other collections, you can keep it for those.
Card and SEPA transfer, with more on the way. Stripe offers more: that is one of the points where going direct makes sense if your business depends on it.
Yes, a public API and webhooks, to plug in your own tools. So you keep a door open without having to rebuild the collection layer.
A few minutes. Your account is already connected to Ezus and there is nothing to build. Four one-minute videos explain the rest at docs.ezuspay.io.
Other comparisons
Compare Ezus Pay with the other ways of collecting payments.