Global Account
Global Account
Cross-border remittances: corridors and currencies, payee registration, quotes, orders, supplementary information and reconfirmation, plus merchant currency conversions for funding.
Guides
Global Account OverviewCross-border remittance starts with a payee, then an estimate, then an order. Each step has its own potential blocker.Core ConceptsCorridors, quotes, locked amounts, and slippage reserves define how this product works.Supported Corridors and CurrenciesAvailable corridors change dynamically and may go offline temporarily. Do not hardcode your own list.Create PayeesPayee field schemas are dynamic. Query the corridor before rendering a form instead of hardcoding the documentation's example.Personal Line: Setup and UsePersonal Remittance (POBO) sends funds in the member's own name and first requires an upstream subaccount.EstimatesEstimates only calculate. They create no order, freeze no funds, and have no quote_id. The execution price is fixed at dispatch.Place an OrderPlacing an order commits funds. Member-funded orders lock member balances; merchant-funded orders lock merchant prepaid funds.Order Lifecycle15 order states, terminal outcomes, and where funds sit at each stage. Alert on unknown states; never silently substitute another.Supplementary Documents and ReconfirmationSupplementary documents and reconfirmation are two reasons an order pauses for human action. Neither automatically times out into a refund.Merchant FXMerchant FX prepares funds in your own prepaid account. It is separate from a member's internal currency exchange.Integration FAQSix common questions when integrating this product.
Webhook
Remittance Order StatusEmitted when a remittance reaches a terminal state: completed, failed or refunded.Remittance Action RequiredA remittance is awaiting action: supplementary information or reconfirmation after a price change.
API Reference · 25 endpoints
Corridors and Rates Corridors & Rates
GET
/v1/remit/corridors
Available corridors, filtered by merchant authorization
GET
/v1/remit/rates
Rate board: no order or payee required
GET
/v1/remit/conversion-dates
Available settlement dates: an advance indication of arrival date
GET
/v1/remit/swift-search
Bank directory search: BIC / bank name → name + address
Payees Payees
GET
/v1/remit/payee-form-schema
Required fields for a corridor: validate the corridor before returning the form
GET
/v1/remit/payees
Payee list, including the name_mismatch risk flag
POST
/v1/remit/payees
Create or link a payee: local creation does not call the upstream
GET
/v1/remit/payees/{id}
Single payee, including upstream_status
PATCH
/v1/remit/payees/{id}
Update a payee nickname / favorite flag: only these two fields are editable
DELETE
/v1/remit/payees/{id}
Remove the association, not the payee entity
POST
/v1/remit/payees/{id}/verify
Submit the payee for upstream onboarding early: moves no funds
Quotes Quotes
GET
/v1/remit/products
Ordering prerequisites for both remittance lines: purpose codes / slippage / minimum amount / limits
POST
/v1/remit/quotes
Remittance estimate: no order or fund hold; read applied_rate
Remittance Orders Remittances
GET
/v1/remittances/{id}
Remittance order details
GET
/v1/remit/vp/agreement
Personal remittance account agreement: six languages; users must read it before submission
GET
/v1/remit/vp/applications
Check personal-line account-opening progress
POST
/v1/remit/vp/applications
Submit a personal remittance (POBO) account application
GET
/v1/remittances
Remittance order list
POST
/v1/remittances
Create an order: payment retries reuse the same idempotency key
Moves funds
POST
/v1/remittances/{id}/cancel
Cancel: only needs_reconfirm is cancellable
Moves funds
POST
/v1/remittances/{id}/reconfirm
Accept a price increase and hold the difference: 4-hour window
Moves funds
GET
/v1/remittances/{id}/pending-action
What this order requires from the user: reconfirmation / documents / nothing