Skip to main content
PATCH
Update Tier 1 bank account

Overview

Add or replace the bank account attached to a customer’s completed Tier 1 KYC. Use this when the customer finished Tier 1 without bank details, when their previous bank details need to be corrected, or when an older verification needs the customer’s phone number added. This endpoint does not repeat BVN or selfie verification, and it does not create a funding account. It starts a new asynchronous Paystack bank account verification for the submitted details, even when the customer does not yet have a permanent NGN funding account. If Paystack is temporarily unavailable, Daya keeps the verification pending and starts it automatically after the provider recovers.

Authentication

string
required
Your merchant API key

Path Parameters

string
required
Customer ID (UUID)

Request Body

string
required
Customer’s phone number. Send the 11-digit national form or the +234 international form.Example: +2348012345678
object
required
NGN bank account belonging to the customer. This is not the funding account the customer will receive.
Before submitting bank_account, get the supported bank_code from GET /v1/banks and verify the account with POST /v1/banks/resolve. Then send the verified account_number and bank_code together.

Request Example

Response

Returns the customer with paystack_funding_account_readiness.status set to READY when the bank details are accepted locally. This does not mean Paystack has completed verification.
200 OK
The response shows only the last four digits of the account number, not the full account number.

Verification Result

Subscribe to:
  • customer.bank_account_verification.succeeded
  • customer.bank_account_verification.failed
Each result includes an identity_version. A later bank detail update increments the version, so ignore a result for an older version after you have received a newer result. Failed results include failure_code and failure_message that you can use to explain what the customer should correct. If verification succeeds and the customer already has a permanent NGN funding account, Daya starts creating its Paystack instruction. Daya sends funding_account.active when Paystack makes a pending account usable, or funding_account.updated when another instruction was already active. If the customer does not have a permanent account, Daya retains the successful verification until you create one. See Bank Account Verification Events for the payload fields and examples.

Next Steps

Webhook Events

Handle the asynchronous verification result

Create Funding Account

Create a permanent NGN funding account when the customer needs one