Skip to main content
POST
Create a batch secure payment for multiple outgoing payouts

Headers

x-api-key
string

API key for authentication (optional if using Client ID or session)

x-client-id
string

Client ID for frontend authentication (optional if using API key or session)

Authorization
string

Bearer token for session authentication (or use the session_token cookie). Only consulted when no x-orchestrator-key, x-api-key, or x-client-id header is present.

Origin
string

Origin header (required for Client ID auth, automatically set by browser)

Body

application/json
tokens
string[]
required

Tokens of existing pending single payout secure payments to combine into one batch payment link

Minimum array length: 2
Minimum string length: 1
redirectUrl
string

URL the payer is redirected to after a successful payment

redirectLabel
string

Optional label describing the redirect destination

Required string length: 1 - 255
Pattern: ^[^<>&"'`]*$

Response

Batch payout secure payment created successfully

requestIds
string[]
required

Array of request IDs created for this secure payment

securePaymentUrl
string<uri>
required

URL to the secure payment page

token
string
required

Secure payment token

feePlan
object | null
required

Resolved fee plan snapshot. Null when fees don't apply — e.g. non-stablecoin currency, or a batch that spans multiple currencies (not yet supported).