These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Travel Expense Optimizer
- Features
- Payments and confirmation
Payments and confirmation
Record payment events from your provider and confirm a booking only when verified payment evidence exists.
OverviewPayment Events×
Travel Expense Optimizer · Payments and confirmation
New
Payment Events
Payment evidence
| Parent | Provider event ID | Type | Amount USD | Occurred at | Provider reference | |
|---|---|---|---|---|---|---|
| BKN-30461 | PEI-267 | Authorization | 860 | 20 Oct | PR-394 | |
| BKN-25128 | PEI-761 | Capture | 280 | 05 Oct | PR-878 | |
| BKN-80331 | PEI-228 | Refund | 710 | 10 Oct | PR-671 | |
| BKN-51211 | PEI-583 | Void | 850 | 07 Oct | PR-613 | |
| BKN-17280 | PEI-266 | Authorization | 130 | 21 Oct | PR-547 |
6 of 6 records
PEI-267Payment evidence · PE-59664
AuthorizationParentBKN-30461
Amount USD860
Occurred at20 Oct
Provider referencePR-394
What you can do
Confirm on payment the provider has recorded
A held trip becomes a booking the company is committed to only when payment is real. Payment events arrive from your card or payment provider with the provider’s event identifier, the type, the amount in US dollars, the date and the provider’s reference. The type is Authorization, Capture, Refund or Void. Each event identifier is recorded once, so a repeated message from the provider does not add a second payment.
The coordinator confirms the booking only when verified payment evidence exists. The supplier’s confirmation date is then recorded on the reserved lines. Refunds and voids are recorded against the same booking, so the payment history explains what was finally spent.
How the work is organized
- Events by provider identifier. Each payment event carries the provider’s identifier and reference, and is never entered twice.
- Confirm on verified payment. A held trip is confirmed only with verified authorization or capture evidence.
- Refunds stay with the trip. Refunds and voids are recorded on the booking they reverse.
What to agree during setup
Agree which payment events count as verified for confirmation: an authorization, a capture or both. Agree how provider references are recorded so finance can trace each payment. Agree who records payment events and who investigates a payment that does not match the quoted amount. Agree how quickly a capture must follow a hold before the hold expires.
Check the handoff on an actual case
The Chicago trip is held at 10:00 for 1,450 USD. At 10:20 the card provider sends an authorization for 1,450 USD with event identifier PX-55102, and at 16:00 a capture with event PX-55871. The Payments Analyst records both. The coordinator confirms the booking on the verified capture.
Two days later the provider sends the capture message again. Its identifier is already recorded, so nothing is added. When the traveler later shortens the stay by a night, the hotel refunds 189 USD; the refund is recorded against the same booking, and the payment history shows 1,261 USD spent.
What your team sees
- Payment Events — Authorizations, captures, refunds and voids by booking, with provider identifier and reference.
- Captured Payments — Captured amounts by booking and date.
Follow the work through
- Hold to confirmed booking: Hold the trip, verify payment and confirm.
Connect your payment provider before the pilot.
What it keeps track of
Data model- Payment evidence
- Provider payment events reconciled against a booking.
- Bookings
- Travel booking records with lifecycle, quoted amount and counterparty.
- Booking resources
- Reserved resource lines attached to a booking parent.
- Exchange rates
- Read-only effective exchange rates for this app.
Who uses it
Permissions- Payments Analyst
- Records and checks payment events.
- Travel Coordinator
- Confirms bookings on verified payment.
- Travel Manager
- Reads captured spend.
- Admin
- Corrects access.
Set up Travel Expense Optimizer your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.