Batch Payment Processing
Email-based batch intake with explicit confirmation rules.
The operating model for this release: structured files, a designated mailbox, and records only after verification.
Book a call →Batch file
CSV or EFT text for the operations desk. Sending mail is not settlement.
Batch payment processing is the centre of the current service. Customers prepare a file, protect it according to their security policy, and send it to the configured batch address. Sending mail does not itself mean the batch was accepted, processed, or settled. Operators record outcomes only after the external processing system confirms them.
- →Published mailbox for batch intake
- →Supported CSV and text formats
- →Troubleshooting for missing headers or duplicate files
- →History that stays empty until confirmation arrives
Use cases
Weekly supplier payment runs
Month-end collection files
One-off correction batches after a returned item
FAQ
If I email a file, is it processed?
Email delivery is not processing confirmation. Wait for an operator update or a confirmed record in the portal.
Should I put account numbers in ordinary email?
Prefer an encrypted channel your security team approves. Unprotected email is not a suitable default for sensitive banking data.
Book a call with our payments team
Tell us how you run files today. We will walk through the customer portal, batch intake, and what is not yet live — including origination and API access.