Batch Payments
This page is a first-pass draft describing batch payments at a conceptual level. All specifics — file format, submission channel, processing SLA, error response format — require product team confirmation before publication. Do not treat any claim on this page as authoritative until this admonition is removed.
What are batch payments?
Batch payments let merchants submit multiple payments in a single operation rather than calling the API once per transaction. This pattern is useful for recurring billing runs, invoice settlement cycles, payroll-style disbursements, and any other workflow where many payments are processed at a known time.
When to use batch payments
Batch processing fits scenarios where:
- Multiple payments are ready at the same time (end-of-day, end-of-cycle, after an invoice run)
- The timing of each individual payment is not latency-sensitive
- Merchant-side batching simplifies reconciliation compared to per-transaction reporting
Batch processing is not a good fit for:
- Interactive checkout flows
- Per-customer payments triggered by customer action
- Any scenario requiring an immediate per-transaction response
How it works (high level)
At a conceptual level, a batch submission contains a list of payment instructions, each with its own amount, customer reference, and payment method or stored token. Zenith processes each entry, returns a batch-level status, and emits per-transaction results through the usual callback, webhook, or GET /v2/payments paths.
The exact batch format, submission endpoint, response schema, error handling, retry semantics, and pricing model for batch payments are not yet documented here. Contact your Zenith integration representative for current batch payment specifications.
Related
Under Construction
Our developers are furiously typing. Results may vary.