One object from cart to settlement
An order carries the payment, FX, duties, risk and payout state together, so you never stitch five APIs back into one story.
Why it matters
One source of truth
Every amount, fee and status in one object.
Predictable events
A single event stream covers the whole order lifecycle.
Typed SDKs
Six server languages generated from one specification.
What's inside
Lifecycle
- Created, authorized, captured, settled, refunded
- Partial captures and refunds
- Idempotency keys on every write
How it works
- 1
Create
POST an order with amount, currency, shopper market and items.
- 2
Collect
Use any checkout surface against that order.
- 3
Observe
Receive webhooks as risk, payment and FX steps complete.
- 4
Settle
See exactly what you received, net of each fee.
curl https://api.international-orders.com/v1/orders \
-u $IO_SECRET_KEY: \
-H "Content-Type: application/json" \
-d '{
"amount": 12900,
"currency": "EUR",
"settlement_currency": "USD",
"shipping": { "country": "DE" },
"items": [{ "name": "Wool scarf", "hs_code": "6117.10", "quantity": 1, "unit_amount": 12900 }]
}'Customer story
Copperline Components
−63%
shipments held at customs · Illustrative
Classification and screening used to happen after the order. Moving them before it changed everything downstream.
Jonas Becker, Director of Global Trade Read the story: Copperline Components
Questions about Unified Orders API
Put Unified Orders API to work
Test it in the sandbox today, or talk to us about your markets.