> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-document/readme/booking-overview/payment-and-ticketing.md).
# Payment & Ticketing
{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva on ATRIP for instant diagnostics.
Ask Eva
{% endhint %}
Use this page to complete payment and wait for ticket issuance.
Start here when you need to:
* pay an existing order
* choose the correct payment method
* track final ticketing after `pay.do`
### FAQ
#### What do I need before `pay.do`?
You need a valid `orderNo`, a supported payment method, and card data when the method is card-based.
The order must still be unpaid and still support the selected payment path.
#### Does payment success mean ticketing is already complete?
No.
Payment success does not always mean the airline PNR and ticket numbers are already final.
Use order follow-up until the final ticketing state is confirmed.
### Main API
* `pay.do`
### Use this when you need
* Deposit payment
* VCC pass-through payment
* BYOA payment
* MoR payment
* Ticket issuance tracking after payment
### Before you call
Confirm these points first:
* the order already exists
* the order is still unpaid
* the order supports the selected payment method
* card data is ready if you use card-based payment
For standard flows, call `order.do` before `pay.do`.
### What should you keep in mind after payment?
Keep using `orderNo` for order follow-up.
Read the final ticketing state from order query.
Do not send duplicate payment requests when payment may already be in progress or completed.
### Payment methods
* `1`: Deposit
* `3`: VCC passthrough
* `4`: BYOA
* `5`: MoR
### Key inputs
Always send:
* `orderNo`
* `paymentMethod`
Send `creditCard` when using:
* VCC passthrough
* MoR
`threeDS.ip` is only relevant for MoR.
### What comes next?
After `pay.do`, use [Query Order](/api-document/readme/booking-overview/query-order.md) until the final ticketed state is confirmed.
Use webhook as a supplement, not as the only confirmation path.
### What to watch
* supported payment methods vary by airline and fare
* card brand must match the order requirements
* payment can fail if the booking is past deadline
* payment success does not always mean ticketing is already finished
* you still need order follow-up until the final ticketing state is confirmed
### Best practice
* read supported payment methods from the booking flow before payment
* use deposit when you need fare guarantee after payment
* use VCC only when the fare supports it
* poll order status after payment until ticketing completes
* handle payment retries carefully to avoid duplicate charges
### Safe retry rule
If payment may already have started, query the order first.
Do not retry payment blindly after `402`, `404`, `406`, or similar order-state errors.
### Common failure cases
Common payment response failures include:
* invalid request data
* payment after deadline
* unsupported payment method
* order already paid
* payment already in progress
* missing passenger data
* card not supported
* card mismatch
* order not confirmed in FR flow
Use the API response `status` as the source of truth.
### Related pages
* [Create Order](/api-document/readme/booking-overview/create-order.md)
* [Confirm Order](/api-document/readme/booking-overview/confirm-order.md)
* [Query Order](/api-document/readme/booking-overview/query-order.md)
* [Hybrid Payment Guide](/api-document/readme/booking-overview/payment-and-ticketing/hybrid-payment-guide.md)
* [Error Codes](/api-document/troubleshooting-and-support/errors-handing.md)
* [Booking APIs](/api-document/api-reference/booking-apis.md)
### Full API reference
See endpoint-level details here:
* [Payment & Ticketing](/api-document/api-reference/booking-apis/payment-and-ticketing.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://resources.atriptech.com/api-document/readme/booking-overview/payment-and-ticketing.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.