Partners
Invoices
Create payment invoices for your merchants and use hosted checkout.
Create an invoice for one of your merchants. Customers pay on hosted checkout. Fulfill when you receive invoice.paid — see Webhooks and Invoice lifecycle.
Create an invoice
curl -X POST http://api.localhost:4000/v1/partner/invoices \
-H "Authorization: Bearer pt_test_..." \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"merchantId": "…",
"amount": "10.00",
"token": "USDC",
"successUrl": "https://your-app.example/success",
"cancelUrl": "https://your-app.example/cancel"
}'| Field | Notes |
|---|---|
merchantId | Required — must belong to your partner |
amount | Decimal major units, e.g. "10.00" (max 6 dp) |
networkId | Optional — lock to one network |
token | Optional — USDC or USDT |
referenceId / metadata | Optional — echoed on webhooks |
successUrl / cancelUrl | Optional — return URLs after checkout |
Do not send environment — it comes from the Partner API key.
Response includes id, checkoutUrl, expiresAt, and deposit addresses when routes are known.
Checkout
Send the customer to checkoutUrl. Partner invoices use hosted checkout without Orqpay merchant branding (your return URLs apply when set).
Get and status
curl http://api.localhost:4000/v1/partner/invoices/{id} \
-H "Authorization: Bearer pt_test_..."
curl http://api.localhost:4000/v1/partner/invoices/{id}/status \
-H "Authorization: Bearer pt_test_..."Invoices for merchants you do not own return 404.
Prefer webhooks over polling. Fulfill on invoice.paid only.