Bank Payment Rules

Each bank guide lists the validations and allowed data formats for Acme payments to that bank. Acme validates every payment against these rules, and the bank validates it again. The rules may be stricter than what the bank requires.

How to read a bank guideCopy Anchor Link

• Each payment type has its own section, with a table of fields.
• M is mandatory and O is optional.
• Conditional (or C) says when the field becomes mandatory.
• Fields written as payments[N].… belong to each payment in a batch payment. The other fields belong to the batch, or to a single payment.
• amount is always in minor units. See Minor units format.
• API: single payments, sent through the bank's API with Create a Payment.
• H2H: batch payments, sent to the bank as host-to-host files with Create a Batch Payment.
• API and H2H: the bank takes both. The guide's Channel note lists the payment types that go through the API.
• Each guide title ends with its channel.

BanksCopy Anchor Link

Purpose code listsCopy Anchor Link