Apply a single payment to multiple invoices (atomic create)
Authorizations
API key issued per entity via Settings > Developers > API Keys.
Each key carries scopes (e.g. orders:read, products:write).
Bearer token format: Authorization: Bearer ark_live_ent_Test keys use ark_test_ent_. Both are issued per entity
via Settings > Developers > API Keys.
Headers
Client-generated unique key for idempotent POST/PATCH/DELETE operations. Alias for the Idempotency parameter. Max 255 chars. On retry with the same key, the original response is returned without re-executing the operation. Keys expire after 24 hours.
255Body
The customer account receiving this payment.
Tender method for this payment.
check, ach, wire, external, cash, credit Total payment amount in dollars (cash actually received). The sum of applications[].amount_applied must be <= amount; any surplus requires route_unapplied='credit'.
5000
When true (and applications omitted), the server allocates the payment oldest-first across the account open invoices. The response returns the computed applications[].
true
When 'credit', any surplus (amount beyond what open invoices absorb) is held as a credit-on-account via a balanced journal entry in the same transaction. Without it, a surplus is refused (no silent cap).
credit Per-invoice application lines (manual override). Omit when auto_apply=true. Sum of amount_applied must be <= amount; any remainder requires route_unapplied='credit'.
1 - 50 elementsCheck number (for check payments).
Check date (YYYY-MM-DD).
External reference (ACH trace number, wire memo, etc.).
Internal notes for this payment.
Payment date for GL posting (YYYY-MM-DD; defaults to today).

