TL;DR
- NGN collections now require
first_nameandlast_nameinstead of thenamefield, plus abank_codeto select the issuing bank for the virtual account - ZAR collections
payment_method_typehas changed fromefttobank
Breaking Changes
The changes below require immediate integration updates.1. NGN Collections (Virtual Accounts) — first_name, last_name, and bank_code Now Required
The single name field for Nigerian (NGN) collections has been replaced with separate first_name and last_name fields. In addition, a bank_code is now required to specify which bank should issue the virtual account.
Previous required fields:
nameaccount_name
first_namelast_nameaccount_namebank_code
Supported bank codes
| Bank Code | Bank Name |
|---|---|
| 17001 | 78 Finance Company Limited |
| 17002 | Fidelity Bank Limited |
| 17003 | Globus Bank Limited |
Example request
- Remove the
namefield from all NGN collection requests. - Add
first_nameandlast_namewith the customer’s split name. - Add
bank_codeusing one of the supported bank codes listed above. - Requests missing any of these fields will be rejected.
2. ZAR Collections — payment_method_type Changed from eft to bank
The payment method type for South Africa (ZAR) collections has changed. Any request still passing payment_method_type: "eft" will be rejected.
Previous value:
Example request
- Find all ZAR collection requests in your integration.
- Replace
"payment_method_type": "eft"with"payment_method_type": "bank". - Retest your South Africa collection flow in sandbox before deploying to production.

