# Verify an account number

> Confirm a customer's bank account details before you create a transfer recipient.

Confirm a customer's bank account details before you create a transfer recipient, so you don't send money to the wrong person or to an invalid account. Small input mistakes, such as a swapped digit or the wrong bank, are common when customers enter their own details. Checking the account turns those mistakes into a visible confirmation step instead of a failed or misdirected transfer, and the support work that follows it.

<localized-block regions="ng, gh">

Use the account name that Paystack returns to confirm the account with the sender before you save the recipient:

<table>
<thead>
  <tr>
    <th>
      Stage
    </th>
    
    <th>
      What to do
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Collect details
    </td>
    
    <td>
      Ask for the account number and bank
    </td>
  </tr>
  
  <tr>
    <td>
      Resolve account
    </td>
    
    <td>
      Call <a href="#resolve-account-number">
        Resolve account number
      </a>
      
       and read the returned <code>
        account_name
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Confirm with the sender
    </td>
    
    <td>
      Show the resolved name and ask the sender to confirm it before you continue
    </td>
  </tr>
  
  <tr>
    <td>
      Create recipient
    </td>
    
    <td>
      <a href="/disbursements/transfers/recipients#create-recipient">
        Create the transfer recipient
      </a>
      
       only after the sender confirms the name
    </td>
  </tr>
  
  <tr>
    <td>
      Initiate transfer
    </td>
    
    <td>
      <a href="/disbursements/transfers/single-transfers">
        Send money
      </a>
      
       to the verified recipient
    </td>
  </tr>
</tbody>
</table>

## Resolve account number

The [Resolve Account Number](/api/bank#resolveAccountNumber) endpoint takes the customer's account number and bank code and returns the customer's account details. To resolve an account number, make a `GET` request to the `/bank/resolve` endpoint:

<localized-request-response src="disbursements/recipients/resolve-account">



</localized-request-response>

<callout title="Pricing" type="info">

This endpoint is free to use.

</callout>
</localized-block>

<localized-block regions="za">

Use account validation to confirm that the account exists, is open, can receive credits, and belongs to the customer:

<table>
<thead>
  <tr>
    <th>
      Stage
    </th>
    
    <th>
      What to do
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Collect details
    </td>
    
    <td>
      Ask for the account number, bank, account holder name, and identity or business registration number
    </td>
  </tr>
  
  <tr>
    <td>
      Check bank support
    </td>
    
    <td>
      <a href="#fetch-supported-banks">
        Fetch the banks that support validation
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      Validate account
    </td>
    
    <td>
      <a href="#validate-account">
        Validate the account
      </a>
      
       and check the returned fields
    </td>
  </tr>
  
  <tr>
    <td>
      Create recipient
    </td>
    
    <td>
      <a href="/disbursements/transfers/recipients#create-recipient">
        Create the transfer recipient
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      Initiate transfer
    </td>
    
    <td>
      <a href="/disbursements/transfers/single-transfers">
        Send money
      </a>
      
       to the verified recipient
    </td>
  </tr>
</tbody>
</table>

## Account validation

The [Validate Account](/api/bank#validateAccountNumber) endpoint lets you validate both personal and business accounts. It checks if the provided customer details are correct and returns the status of the check. However, not all banks support account verification, so you need to confirm whether the customer's bank supports it.

### Fetch supported banks

To confirm the banks that support account validation, make a request to the [List Bank](/api/bank#list) endpoint and pass the `enabled_for_verification` query parameter:

<localized-request-response src="disbursements/verification/list-verification-banks">



</localized-request-response>

The `data` object in the response contains the banks that support account validation. The `supported_types` field in each bank object contains an array of the account types that can be validated. Some banks only support personal accounts, while others support both personal and business accounts. If the customer's bank is returned in this response, then you can go ahead with account validation. Otherwise, account validation can be skipped.

### Validate account

To validate an account, make a `POST` request to the [Validate Account](/api/bank#validateAccountNumber) endpoint. This endpoint can be used for both personal and business account validation with the following request parameters:

<table>
<thead>
  <tr>
    <th>
      Name
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        account_name
      </code>
    </td>
    
    <td>
      String
    </td>
    
    <td>
      Customer's first and last name registered with their bank
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        account_number
      </code>
    </td>
    
    <td>
      String
    </td>
    
    <td>
      Customer's account number
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        account_type
      </code>
    </td>
    
    <td>
      String
    </td>
    
    <td>
      One of <code>
        personal
      </code>
      
       or <code>
        business
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        bank_code
      </code>
    </td>
    
    <td>
      String
    </td>
    
    <td>
      The bank code of the customer's bank. You can fetch bank codes using <a href="/api/bank#list">
        List Bank
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        country_code
      </code>
    </td>
    
    <td>
      String
    </td>
    
    <td>
      The two-digit ISO code of the customer's bank
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        document_type
      </code>
    </td>
    
    <td>
      String
    </td>
    
    <td>
      Customer's mode of identity. One of <code>
        identityNumber
      </code>
      
      , <code>
        passportNumber
      </code>
      
      , or <code>
        businessRegistrationNumber
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        document_number
      </code>
    </td>
    
    <td>
      String
    </td>
    
    <td>
      Customer's identity document number
    </td>
  </tr>
</tbody>
</table>

When validating a personal account number, the customer can either provide their passport or identity number. You can specify the mode of identity by passing either `identityNumber` or `passportNumber` as the `document_type` parameter.

For business account validation, the `document_type` should be `businessRegistrationNumber`.

<localized-request-response src="disbursements/verification/validate-account">



</localized-request-response>

The response contains fields that describe the account capabilities and the validation status. Use these fields to determine whether the account meets your expectations.

<table>
<thead>
  <tr>
    <th>
      Name
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        accountAcceptsDebits
      </code>
    </td>
    
    <td>
      boolean
    </td>
    
    <td>
      Indicates that the account can accept debit orders
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        accountAcceptsCredits
      </code>
    </td>
    
    <td>
      boolean
    </td>
    
    <td>
      Indicates that the account can accept credits. This is useful when you want to use <a href="/api/transfer">
        Transfers
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        accountOpenForMoreThanThreeMonths
      </code>
    </td>
    
    <td>
      boolean
    </td>
    
    <td>
      Indicates that the bank account has been open for more than three months
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        accountHolderMatch
      </code>
    </td>
    
    <td>
      boolean
    </td>
    
    <td>
      Indicates that the account holder details match the provided identity number or business registration number
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        accountOpen
      </code>
    </td>
    
    <td>
      boolean
    </td>
    
    <td>
      Indicates that the account is still open and functional. Dormant accounts can cause debit orders or transfers to fail.
    </td>
  </tr>
</tbody>
</table>

<callout title="Pricing" type="info">

This endpoint costs **ZAR 3** per successful request regardless of the account validation status.

</callout>
</localized-block>
