Trip Payment Operations

Taxi & Private Hire › Products › Trip › Trip Payment Operations

Generally available

HTTP endpoints to manually trigger booking-time preauth, trip-end capture, or refund on a specific segment. Out-of-band controls — most preauths fire automatically at booking and most captures fire at archive — but operators sometimes need to retry a failed preauth or force a capture when the automated path stalled.

Example request

POST /client/{clientId}/tripsegment/{tripSegmentId}/capture ▷ Try it

See the API reference for the full request and response schema.

Endpoints

Method	Path
POST	/client/{clientId}/tripsegment/{tripSegmentId}/capture · primary	▷ Try it
POST	/client/{clientId}/tripsegment/{tripSegmentId}/preauth	▷ Try it

Full request/response schemas and an interactive explorer will live in the API reference (coming soon).

Use cases

Operator flows that exercise this feature.

Capture payment

action risk: high approval required

Capture the held funds at trip end. Moves money — requires approval.

1. POST /client/{clientId}/tripsegment/{tripSegmentId}/capture

Pre-authorise a fare

action risk: medium

Place a pre-authorisation hold on the customer's payment method before the ride.

1. POST /client/{clientId}/tripsegment/{tripSegmentId}/preauth

Related

• Payment Preauthorisations
• Payments
• Trip Charges