Virtual Reference Numbers

VRNs act as aliases for accounts, enabling unique use cases like accounts receivable segmentation or reconciliation.
Endpoints:

• GET List Virtual Reference Numbers: GET /virtual_reference_numbers
• POST Create a new Virtual Reference Number: POST /virtual_reference_numbers
• GET Get a single Virtual Reference Number: GET /virtual_reference_numbers/{uid}
• PUT Edit a Virtual Reference Number: PUT /virtual_reference_numbers/{uid}
• DELETE Archive a Virtual Reference Number: DELETE /virtual_reference_numbers/{uid}
• PUT Lock a Virtual Reference Number: PUT /virtual_reference_numbers/{uid}/lock
• PUT Unlock a Virtual Reference Number: PUT /virtual_reference_numbers/{uid}/unlock

Virtual Reference Numbers (or VRNs) are virtualized account numbers that point to a single deposit account. They are aliases to a Synthetic Account and can form a many-to-one relationship with their parent Synthetic Account.

Common VRNs Use Cases:

• This is to reference a stored funds product that is client-managed on a separate ledger. Clients can then provide VRNs to external merchants or counterparties who wish to pay for that stored fund's product.
• This provides Clients with another layer of network-addressable account numbers with which to accept payments. This many-to-one relationship affords Clients account segmentation. For instance, one VRN is utilized for Accounts Receivable (AR) while the other is used for Accounts Payable (AP), all while referencing the same underlying Account.

These same VRNs can then be aligned with Custodial Accounts transactions to allow for quick reconciliation or accounting.

Note For certain payment rails, like Instant Payments, VRNs must be registered with Newline and Fifth Third before being used, as this will allow for network acceptance. Please review the fields in each API reference to confirm Instant Payment registration.