Process payments at scale
Make high-volume payment collection efficient, on a cycle that suits the business.
Process large volumes of card-not-present transactions together, instead of one at a time in real time.
What it is
Bulk processing, on a schedule
Batch processes large volumes of card-not-present transactions together as a scheduled batch, rather than requiring each one to be authorised in real time. It's built for merchants collecting the same type of payment from many customers on a regular cycle.
The merchant problem it solves
The same payment, from thousands of customers, every cycle
The merchant collects a recurring payment — premiums, membership fees, subscriptions — from a large customer base, and doing it one transaction at a time is slow, manual, and error-prone.
How it works
From sign-up to live in days, not months.
Key benefits
Handles real volume
Built for processing many transactions in one pass, not one at a time.
Less manual work
Removes the need to key in or authorise each payment individually.
Fits a billing cycle
Designed around scheduled, recurring collection — monthly, weekly, or however the merchant bills.
Clear reconciliation
Results are reported per transaction, so nothing gets lost in the batch.
Qualifying questions to ask
Use these to confirm the fit before you pitch.
- How many payments does the merchant collect in a typical cycle?
- Is the amount and timing predictable — like monthly premiums?
- How are they collecting today — manual EFT, debit order, one by one?
- Do they need real-time authorisation per transaction, or is a scheduled batch acceptable?
Explain it in 30 seconds
“Batch is designed for businesses processing large volumes of card-not-present payments or regular customer collections.”
Common objections
That's exactly the volume Batch is built for — one file instead of hundreds of individual transactions.
Batch reports results after processing, not instantly — if true real-time confirmation per transaction matters, Enterprise may be the better fit.
Yes — BackOffice shows the outcome of every transaction within the batch, not just an aggregate result.
Downloads & resources
Sales resources
- Batch Product Brief Download
Product & technical resources
- Batch developer guide View
- Batch Back Office User Guide View
Example merchant scenario
An insurance underwriter collects monthly premiums from thousands of policyholders. Instead of processing each payment manually, they submit one batch file each month and reconcile the results the same day.