Forex API · TatvaPay Docs

Coming next. Forex runs against a simulated AD Category-II partner in the sandbox. Purpose codes, TCS and limits are sandbox values to be confirmed with the partner. Nothing is live.

Forex and travel requests are files (fxo_…) with an AD Category-II partner: a trip's forex, an LRS remittance, a buy-back, or a corporate trip. The agent prepares the file; only the partner's named dealer, a person, books it.

Step	REST	MCP tool
Rates	`GET /v1/pay/forex/partners/{id}/rates`	`get_forex_rates`
Quote with a rate lock	`POST /v1/pay/forex/quotes` (+ `Idempotency-Key`)	`forex_quote`
Documents	`POST /v1/pay/forex/orders/{id}/documents`	`upload_document`
Submit to the dealer	`POST /v1/pay/forex/orders/{id}/submit`	`submit_file`
Status and checklist	`GET /v1/pay/forex/orders/{id}`	`file_status`

Rates are integer ten-thousandths of a rupee (885000 is ₹88.5000); foreign amounts are decimal strings.
The rate lock holds 15 minutes; submit before it lapses or ask for a fresh quote.
Documents are PDFs or photos, up to 5 MB each, as base64 or (MCP) a public https URL. Aadhaar is never collected.
A PAN is stored only as a salted hash and a masked form (******234F).
Every file ends with a hash-chained receipt, like a payment's.