Virtual Account Numbers #

Virtual accounts are virtual subledgers within one physical depository account that can be utilized in a variety of ways. Virtual Account Numbers (VANs) allow clients to provide a routing and account number that can be used to allow ACH transactions to and from a Dwolla Balance. The routing and account number is tied to a Dwolla Client’s Master Balance, or one of their Verified Customer's balances. Virtual accounts hold no funds—they are simply a mechanism to route funds into a single Dwolla Balance. Dwolla’s Virtual Account Number feature performs two crucial functions:

• Eliminate the need to deposit funds into an intermediary depository account before transferring funds in or out of your Dwolla Balance.
• Keep transaction data separate and organized within the Dwolla Balance.

Items To Note:

• VANs cannot be used as a source or destination when calling the /transfers endpoint.
• Users that are enabled for VANs will currently not have access to RTP, wire or Push-to-debit features.
• Many virtual account numbers can route to a single Dwolla Balance. If you need to designate a portion of funds within a balance, reference the Labels API.
• Dwolla has no transaction limit for externally initiated transfers.

Interacting With Virtual Accounts #

The Dwolla API supports methods for creating a VAN for a Verified Customer and creating a VAN for a Master Account, as well as retrieving routing details and removing a virtual account.

Once a virtual account is created, a unique account and routing number pair will be available for use to create external transactions (reference example below). A virtual account will be represented as a Funding Source in the Dwolla API, however, it cannot be used when calling the Dwolla API to initiate transfers. Your Dwolla Balance is the only funding source you can use for transfers using the funds in that account within the Dwolla system, and you'll only be able to use the VAN to initiate transfers affecting the funds in that account from a third party system. Upon creation of a virtual account as a Funding Source, it will immediately be available for use with a verified status.

A VAN can be removed at any time via the API. A new VAN can be created in its place if needed.

Example Routing Details Response:

{
  "_links": {
    "self": {
      "href": "https://api-sandbox.dwolla.com/funding-sources/e6d68efb-c49b-43db-8867-e1ca58c6ee8c/ach-routing",
      "type": "application/vnd.dwolla.v1.hal+json",
      "resource-type": "ach-routing"
    },
    "funding-source": {
      "href": "https://api-sandbox.dwolla.com/funding-sources/e6d68efb-c49b-43db-8867-e1ca58c6ee8c",
      "type": "application/vnd.dwolla.v1.hal+json",
      "resource-type": "funding-source"
    }
  },
  "accountNumber": "9619991490430833",
  "routingNumber": "084106768"
}

Tracking Virtual Account Transfers #

Externally initiated transactions will be represented by transfers that are automatically created and available in the transaction listing endpoint when Dwolla is notified of the transaction by the ACH Network.

Adding funds into a balance will be represented by a new transfer where the source is the VAN funding source and the destination is the Dwolla Balance funding source.

Withdrawals from the Dwolla Balance will be represented by a new transfer where the source is the Dwolla Balance and the destination is the VAN funding source. Each new transfer will trigger a bank_transfer_created or customer_bank_transfer_created webhook. The creation webhooks will be triggered approximately 30 minutes prior to any completed webhook event of bank_transfer_completed or customer_bank_transfer_completed.

Transfers will be created in a pending or failed status depending on whether the customer record or VAN has been deactivated, suspended, or removed. Pending transfers will be processed automatically during the following times (subject to change).

• 11 a.m. CT
• 1:15 p.m. CT
• 5:45 p.m. CT

Additional details about an external transaction will be available in the achDetails JSON object when retrieving the transfer from the API. Either the source or the destination will be present in the object depending on the direction of the funds transfer.

ACH Details Optional Fields

Example Response Object

{
  ...
  "achDetails": {
    "source": {
      "addenda": {
        "values": [
          "string"
        ]
      },
      "beneficiaryName": "string",
      "companyId": "string",
      "companyName": "string",
      "companyEntryDescription": "PAYMENT",  // will differ depending on originator
      "effectiveDate": "YYYY-MM-DD",
      "postingData": "string:string:string", // suggested memo line, fields are companyName:companyDiscretionaryData:beneficiaryName
      "routingNumber": "string",             // of originating bank
      "traceId": "string"
    },
    "destination": {
      // same fields as source
    }
  }
}