Navigate to...

Alternative Integration Options

Visa File Exchange Service and Swift FIN+ are alternative integration options available for integrating Visa Direct for Account. Both integration options provide a flexible way to exchange payment related messages between clients and Visa.

A payout request sent via the Visa File Exchange System (VFES) or Swift network (FIN+ service), once received by Visa, is transformed from a payment request into API format. The same process is followed for the response sent back to the client.

These alternative options are currently available for Visa Direct for Account.

Alternative Integration Payment Flow

1	Sender initiates a payment to the Recipient.
2	The Originating Entity receives the payment request and performs internal processing and screening. The payment request is captured, verified, and submitted to Visa via VFES or Swift.
3	Visa Direct Gateway processes the payment request and sends it to its Network Partner, who provides access to local settlement services.
4	The Recipient Financial Institution receives the payout and credits the Recipient.
5	Payment is received by the Recipient.

Sending Payouts using Swift

Clients who integrate using Swift will have a secure connection to make transactions. Client will continue to have communication, reconciliation and management of financial transactions. Single payment requests are transformed into the Visa Direct for Account Send Payout API. The transaction then continues to follow the existing route of a Visa Direct for Account transaction.

Refer to Onboarding for help implementing Swift.

Sending Payouts using Visa File Exchange Service

Clients who use Visa File Exchange Service will be able to send single or bulk transactions using the ISO 20022 standard. The payment files are in CBPR+ format where responses can be acknowledged and confirmed at a single file transaction level. Visa File Exchange Service enables the payment files to be transformed into readable data, which is sent to Visa Direct for Account Send Payout API, proceeding to follow the existing Visa Payments Limited (VPL) flow.

Refer to Onboarding for help implementing Visa File Exchange Service.

Availability

Clients can choose to use Swift as their integration option in all regions where Visa Direct for Account is available:

Asia Pacific
CEMEA
Europe
LAC
North America

VFES will be made available to clients shortly.

Onboarding

To onboard to VFES or Swift, Clients must follow the same steps to onboard to the Visa Direct for Account and Wallet APIs. Click here to see the implementation overview. Other tasks to be completed include:

Program Information Form (PIF) - The PIF forms part of a client’s contract and is specific to each program. Contact your Visa Representative for more information.
Solution Requirement Form (SRF) - The SRF is where a client can specify either Visa File Interface or Swift Client Interface as their preferred choice of payment initiation. The SRF can be completed at the same time as the PIF. Contact your Visa Representative for more information.
For clients wishing to use VFES, the VFES form - To onboard to VFES, the client must complete the VFES form. Contact the Visa representative to obtain the form.
For clients wishing to use Swift - Make sure the payout message format is compliant with Visa's standard specified in MyStandards. Contact your Visa Representative for more information.
Accessing the Visa Direct Portal

Considerations

Integration using Visa File Exchange Service or Swift is currently available for Visa Direct for Account only.

Clients integrating to Visa File Exchange Service or Swift can still connect to the optional Visa Direct for Account APIs offered on the Visa Developer Center. These include the Payout Status Notification, Query Payout, Ledger Notification, Get Account Balance and Get Posting Calendar APIs. See APIs.

Error Codes

See Error Codes for Swift and VFES Error Codes.