Payment initiation and direct-debit message mapping.
Next. ISO 20022 messaging is built and on its way to Live. Tell us if you need it, and we'll tell you honestly when it will be ready for you.
Banks and large companies exchange payments as structured ISO 20022 messages. If your platform can't read and write them, every bulk payment and status report becomes a manual file conversion.
ISO 20022 messaging on Bridge will map payment initiation (pain.001), direct debits (pain.008 and pacs.003) and requests to pay (pain.013) to and from Bridge payments, with status reports back.
It is built, and on its way. It carries no conformance certification.
A pain.001 file from a corporate customer, by API or file transfer.
Duplicates and malformed messages will be rejected with a reason.
Each instruction becomes a Bridge transfer.
Status reports tell the sender what happened to each line.
pain.001 bulk credit transfers.
pain.008 and pacs.003 mappings.
pain.013 mapping.
Per-line status back to the sender.
The same message sent twice will be recognised and refused.
Follow a payment by its reference.
Illustrative businesses, not customers. Figures are made up to show the flow.
A bank's corporate desk in Lagos · Banks, MFBs & PSBs
Corporate customers send payroll as pain.001 files, and the bank re-keys them into its payments system.
Corporate files will flow straight into payments.
An insurer collecting premiums in Abuja · Lenders & BNPL
The insurer's collection partner expects pain.008 files. Building them by hand is error-prone.
Premium collection will run in the format partners expect.
A utility in Port Harcourt · Merchants & e-commerce
The utility wants to send structured payment requests customers can approve.
Bills will arrive as requests customers approve.
Not yet. It is built and on its way; tell us your message types.
No. It carries no conformance certification.
We'll come back with what's live for you today, and what's next.
Bridge