# Dedicated Virtual Accounts

> Reference information for reusable customer-linked virtual accounts on Paystack.

<callout type="info">
<localized-block regions="ng">

Dedicated Virtual Accounts settle in ****.

</localized-block>

This feature requires your business to have completed the [go-live process](https://support.paystack.com/hc/en-us/articles/360009881220).

</callout>

Dedicated Virtual Accounts (DVAs) are reusable bank account numbers assigned to individual customers. When a transfer lands in a customer's DVA, Paystack automatically records it as a transaction from that customer.

## What DVAs are

A DVA is a persistent virtual account used for repeated inbound transfers. It is available on the Paystack Dashboard and API and is designed for businesses that want account-based payments tied to a known customer record.

DVAs suit wallet top-ups, repeat deposits, and customers who prefer bank transfers to cards. Each customer keeps a stable payment destination, so you don't generate a new payment instruction for every payment.

## Supported banks and providers

DVA creation uses supported providers returned by the Fetch Providers endpoint. Paystack does not hard-code the bank list in the product guide; the available provider set depends on the merchant's market and enabled DVA providers.

Inbound transfer approval is available only on Paystack-Titan Virtual Accounts.

## Customer assignment model

A DVA is assigned to a customer record. In the multi-step model, the flow consists of:

1. Creating or updating the customer record with identity details
2. Validating the customer where compliance requires it
3. Creating the Dedicated Virtual Account for that customer

<localized-value page-key="payments/channels/dedicated-virtual-accounts" path="validation_note">



</localized-value>

 Customer consent is also required because DVA creation uses personal customer information.

In the single-step model, Paystack handles customer creation, validation where needed, and account assignment in one request.

## Account behavior

- Incoming transfers are reported through `charge.success`
- Successful assignment is reported through `dedicatedaccount.assign.success`
- Failed assignment is reported through `dedicatedaccount.assign.failed`
- Customer requery is rate-limited to one request every 10 minutes
- Default account creation limit is 1,000 dedicated bank accounts per business, subject to review for increase

When an account is created, the account name generally follows the format **Product Name / Customer Name**.

For the operational setup flow, see **Create and Assign Dedicated Virtual Accounts**.

## How DVAs differ from regular bank transfers

The main difference between DVAs and Pay with Transfer is lifespan and ownership.

<table>
<thead>
  <tr>
    <th>
      Feature
    </th>
    
    <th>
      Dedicated Virtual Accounts
    </th>
    
    <th>
      Pay with Transfer
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Account scope
    </td>
    
    <td>
      Customer-level
    </td>
    
    <td>
      Transaction-level
    </td>
  </tr>
  
  <tr>
    <td>
      Reuse
    </td>
    
    <td>
      Reusable
    </td>
    
    <td>
      Expires after payment or timeout
    </td>
  </tr>
  
  <tr>
    <td>
      Matching
    </td>
    
    <td>
      Always linked to assigned customer
    </td>
    
    <td>
      Linked to one active charge
    </td>
  </tr>
  
  <tr>
    <td>
      Typical use
    </td>
    
    <td>
      Wallet funding, repeat deposits, account-based reconciliation
    </td>
    
    <td>
      One-off checkout transfers
    </td>
  </tr>
</tbody>
</table>
