The B2B Virtual Account Payment Method has APIs that allow you to use virtual accounts to automate business-to-business spend. You can use these APIs to develop flexible solutions across use cases, industries, and segments. Whether it is a virtual account embedded within the procure-to-pay cycle, a virtual account used for payer-to-provider payments or a virtual account used in the travel booking process, this method will streamline the payment process.
Consumers of the B2B Virtual Account Payment Method can choose to integrate to a majority of the available APIs to enable development of an end-to-end payables solution that includes: managing suppliers, accounts, and submitting payments. You can also integrate to a smaller subset of the APIs for specific needs such as requesting an account with specified authorization controls to reduce risk. You can tailor this solution set to your unique needs.
The B2B Virtual Account Payment Method supports multiple payment options and handles both supplier-initiated and buyer-initiated payments. It also supports multiple account control options using authorization controls and credit limit adjustments at the processor. The B2B Virtual Account Payment Method also supports pseudo accounts (a type of Commercial token), TSYS VANs, and processor-based PANs. Pseudo accounts allow added security for cardholders by having merchants process payments using pseudo accounts rather than a regular PAN. Pseudo accounts are generated internally at Visa, using Visa's Token Vault, rather than at the processor.
Issuers, processors, fintechs, third party payment providers or Travel agencies, can use the B2B Virtual Account Payment Method APIs.
Note: Any third party implementing the B2B APIs must have an issuer. You can select a subset of our endpoints to code to based on your desired use case. Once you setup a VDP account, Visa can provide you with consultative support.
With these APIs, you can request accounts with authorization controls and provide the accounts to the end accountholder yourself, or you can use a more comprehensive set of APIs to automate the process of paying your suppliers. Additionally, you can perform supplementary tasks like setting up suppliers, buyers, and account pools for single use accounts via APIs.
Use the API explorer in the API Reference section to understand how to use APIs in the Sandbox. When we are ready to promote your project to CTE or production, complete the details requested in the Project promotion form. A Visa implementation manager will set up the data required and promote your project to the requested environment. To get started, refer to the Getting Started section in the Visa Developer Center.
To make calls to the B2B Virtual Account Payment Method APIs, you need multiple IDs to identify the corporation and their accounts (Client ID, Buyer ID, and situationally Proxy Pool ID). For the sandbox environment, the system will display the IDs to use. For other environments, your Visa implementation manager will complete the setup and provide the required IDs.
Note: The sandbox environment is designed to provide a general view and guide of the endpoint request and response structure. The data in the sandbox covers a small subset of possible requests. There are systematic environment limitations, and you cannot execute all API functionality or see the full list of accurate error codes through the API explorer in sandbox. Please code using the API specifications, including error codes, rather than mimicking the API explorer.
See the error codes page for the full list of accurate codes related to the B2B Virtual Account Payment Method.
The following table lists the regional availability for B2B Virtual Account Payment Methods. To view availability of all products, refer to the Availability Matrix.
Available in entire region
Limited availability in region
|Asia-Pacific||Processor integration / adjustable limit functionality not available in Asia-Pacific. Multibyte characters are not supported.|
|Europe||Functionality Includes: Visa Payment Controls, Adjustable Credit limit (processor integration required), and Visa Pseudo Accounts. Note: Reconciliation data only available for transactions flowing through VisaNet. May offer additional option through VCF file.|
|LAC||Processor Integration /adjustable limit account functionality not available in LAC|