Integrations

Plug Ezus Pay into your tools

Start with a link you share, put the checkout on your website, or drive everything from your own system with the API and webhooks. Each level works on its own.

QuickstartAPI reference
Check your key
curl https://api.ezuspay.app/v1/ping \
  -H "x-api-key: $EZP_KEY"

{
  "success": true,
  "data": {
    "status": "ok",
    "agency": { "name": "Voyages Horizon" },
    "mode": "TEST",
    "apiKey": {
      "scopes": ["bookings:write", "payment-links:write"]
    }
  }
}

Five ways to connect

No code needed for the first three. The last two are for teams with their own software, such as tour operators and DMCs.

No code

Payment links

A secure checkout URL to send by email, message or in a client space.

  • Card, SEPA Direct Debit, Apple Pay and Google Pay
  • 8 languages, your logo and colors
  • Your questions to the traveler before payment
How links work
One line of code

Embedded checkout

The checkout on your own site, in the page or as a payment button.

  • One script tag, no dependency
  • Works on any site that accepts a script tag
  • An event when the payment succeeds
Embed the checkout
Built in

Ezus

Your Ezus projects become bookings, and payments go back to the right project.

  • Projects, alternatives and client synced
  • Links shown in the Ezus client space
  • Your Stripe account taken over, history included
Connect Ezus
Developers

REST API

Create bookings and payment links, read payments and refund them from your own software.

  • Keys with limited scopes, separate test keys
  • JSON, amounts in cents, ISO dates
  • 600 reads and 60 writes per minute per key
Read the reference
Developers

Webhooks

A signed HTTPS call the moment something happens to a payment.

  • HMAC-SHA256 signature
  • Up to 5 endpoints, retries for 8 hours
  • Delivery log, resend and test button
Set up webhooks

What the API does

  • POST/v1/bookingsCreate a booking, with its first option
  • POST/v1/bookings/:id/resyncRefresh a booking from Ezus
  • POST/v1/bookings/:id/payment-linksCreate a payment link and get its URL
  • GET/v1/payment-links/:idRead a link, its plan and what it collected
  • GET/v1/checkout-fieldsList the questions asked on the checkout
  • GET/v1/transactionsList payments, filtered by date, status and source
  • GET/v1/transactions/:idRead a payment, its refunds and the traveler's answers
  • POST/v1/transactions/:id/refundsRefund all or part of a payment
API reference

Events you receive

Every event is signed and carries the booking, the alternative and, for a plan, the installment concerned.

  • payment.succeeded

    A payment went through, including each installment of a plan.

  • payment.failed

    A payment attempt was declined.

  • payment.refunded

    A refund actually went through.

  • booking.fully_paid

    A booking option has been paid in full.

See the payloads

Try it in test mode

Create a free account, switch to test mode and make your first API call in a few minutes. Nothing is collected.

Create a free account