Release Notes - 8.0.0 - June 2026

Release Date: June 2026

TL;DR

NGN collections now require first_name and last_name instead of the name field, plus a bank_code to select the issuing bank for the virtual account
ZAR collections payment_method_type has changed from eft to bank

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:

name
account_name

New required fields:

first_name
last_name
account_name
bank_code

Supported bank codes

Bank Code	Bank Name
17001	78 Finance Company Limited
17002	Fidelity Bank Limited
17003	Globus Bank Limited

Example request

{
  "client_id": "client_id",
  "params": {
    "account_name": "Joseph Mike",
    "amount": "10000",
    "bank_code": "17001",
    "callback_url": "https://example.com",
    "country_id": 17,
    "currency": "NGN",
    "first_name": "Joseph",
    "last_name": "Mike",
    "mobile": "234xxxxxxxxx0",
    "payment_method_type": "virtual_account",
    "third_party_reference_1": "",
    "third_party_reference_2": ""
  },
  "salt": "salt_value",
  "sender": "Integration_name",
  "timestamp": 1234567890,
  "signature": "0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx5"
}

Implementation checklist:

Remove the name field from all NGN collection requests.
Add first_name and last_name with the customer’s split name.
Add bank_code using one of the supported bank codes listed above.
Requests missing any of these fields will be rejected.

See: NGN Virtual Account Collections

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:

"payment_method_type": "eft"

New value:

"payment_method_type": "bank"

Example request

{
  "client_id": "your_client_id",
  "params": {
    "amount": 500,
    "bank_code": "0001",
    "callback_url": "https://webhook.site/",
    "country_id": 15,
    "currency": "ZAR",
    "mobile": "276xxxxxxxx8",
    "name": "John Doe",
    "payment_method_type": "bank",
    "third_party_reference_1": "ZAR_DEPOSIT",
    "successful_url": "https://yoursite.com/payment/success",
    "failure_url": "https://yoursite.com/payment/failure"
  },
  "salt": "unique_salt",
  "sender": "Integration Name",
  "timestamp": 1234567890,
  "signature": "generated_signature"
}

Implementation checklist:

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.

See: South Africa ZAR Bank Collections

​TL;DR

​Breaking Changes

​1. NGN Collections (Virtual Accounts) — first_name, last_name, and bank_code Now Required

​Supported bank codes

​Example request

​2. ZAR Collections — payment_method_type Changed from eft to bank

​Example request

TL;DR

Breaking Changes

1. NGN Collections (Virtual Accounts) — `first_name`, `last_name`, and `bank_code` Now Required

Supported bank codes

Example request

2. ZAR Collections — `payment_method_type` Changed from `eft` to `bank`

Example request