Pay for a booking
Pay for a booking by invoice, payment link or Stripe Connect.
You will pay for a booking so that Transferz starts processing its journeys. You need the booking
id from Create a booking and at least one payment method
enabled for your account.
A booking that is not paid stays NOT_PAID and nobody drives. Once it is paid, its journeys move to
PENDING (or AWAITING_APPROVAL while Transferz checks them) and Transferz looks for a transfer
company.
Step 1: Choose a payment method
| Method | Who takes the money from the booker | How you pay | Call |
|---|---|---|---|
| Invoice | You | Transferz invoices you periodically for the journeys | Pay by invoice |
| Payment link | Transferz | The booker pays on a page hosted by Transferz | Generate payment link |
| Stripe Connect | You, in your own Stripe account | You pass the Stripe payment intent to Transferz | Pay by Stripe Connect |
Each method is enabled per partner account by Transferz. Invoice payment needs agreement with your partner success manager; Stripe Connect is set up on request. If none of these fits how you collect payment, other set-ups are arranged with Transferz: ask in a support ticket.
Step 2: Pay
Use the section for your method.
Step 3: On invoice
Call Pay by invoice with the booking id. There is no request body.
/bookings/312840/pay-by-invoiceReferencecurl --request POST \ --url 'https://warpdrive.staging.transferz.com/partners/bookings/312840/pay-by-invoice' \ --header 'Accept: application/json' \ --header 'X-API-Key: YOUR_STAGING_API_KEY'{ "id": 312840, "code": "TZ7K4QM", "partnerReference": "ORDER-10023", "journeys": [{ "id": 488213, "code": "TZ7K4QM-1", "status": "PENDING" }]}The response is the booking. The payment is processed asynchronously, so a journey can still show
NOT_PAID in this response. A 200 response means the payment was accepted.
Step 4: With a payment link
Call Generate payment link and send the booker to the url.
Optionally give the locale of the payment page and a returnUrl to send the booker back to your
site after paying.
/bookings/312840/generate-payment-linkReferencecurl --request POST \ --url 'https://warpdrive.staging.transferz.com/partners/bookings/312840/generate-payment-link' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --header 'X-API-Key: YOUR_STAGING_API_KEY' \ --data '{ "locale": "nl", "returnUrl": "https://shop.example.com/payment-complete"}'{ "url": "https://test.adyen.link/PLTZ7K4QM0001", "expiresAt": "2026-11-21T10:50:00"}The link stops working at expiresAt. The journeys move to PENDING once the booker has paid,
usually within seconds. Do not treat the booking as paid when you generate the link; wait for the
status change (see the last step).
Step 5: With Stripe Connect
Transferz links its Stripe account to yours. You take the payment from the traveller in your own Stripe checkout and pass the id of the payment intent (opens in a new tab) to Pay by Stripe Connect:
/bookings/312840/pay-by-stripe-connectReferencecurl --request POST \ --url 'https://warpdrive.staging.transferz.com/partners/bookings/312840/pay-by-stripe-connect' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --header 'X-API-Key: YOUR_STAGING_API_KEY' \ --data '{ "paymentIntent": "pi_3TzExample0000000001"}'{ "id": 312840, "code": "TZ7K4QM", "journeys": [{ "id": 488213, "code": "TZ7K4QM-1", "status": "PENDING" }]}Step 6: Check that the booking is paid
Wait until each journey has left NOT_PAID before you confirm the order to the traveller. Either
receive the journeyStatusChangedEvent for each journey, or
call Get booking and read journeys[].status:
/bookings/312840Referencecurl --request GET \ --url 'https://warpdrive.staging.transferz.com/partners/bookings/312840' \ --header 'Accept: application/json' \ --header 'X-API-Key: YOUR_STAGING_API_KEY'{ "id": 312840, "code": "TZ7K4QM", "journeys": [{ "id": 488213, "code": "TZ7K4QM-1", "status": "PENDING" }]}Errors
| Problem | Cause | What to do |
|---|---|---|
400 with PAYMENT_ON_INVOICE_NOT_ALLOWED | Invoice payment is not enabled for your account. | Use another method, or ask your partner success manager to enable it. |
400 with STRIPE_PAYMENT_FAILED | The payment intent could not be used. | Check the intent in your Stripe dashboard (amount, currency, status) and retry with a valid one. |
400 with BLANK_VALUE and field paymentIntent | The payment intent is empty. | Send the intent id. |
403 with INSUFFICIENT_PERMISSIONS | The booking belongs to another partner. | Check the booking id and the API key. |
Journeys stay NOT_PAID after a payment link | The booker has not paid, or the link expired. | Generate a new link and send it to the booker. |
Next steps
- Follow a journey now that it is paid.
- Cancel a journey or a booking if the traveller no longer needs it.