Visa Money Transfer (VMT) Request & Response Fields
This section outlines the request and response fields specific to VMT transactions, Account Funding Transaction (AFT), Watch List Screening (WLS), and Original Credit Transaction (OCT).
Request Fields
The request fields are organized into tag-length-value (TLV) fields, which in turn consist of multiple tags. Accordingly, this section is organized by TLV field and tag.
|
NOTE: This section provides a summary of the important transaction fields. For comprehensive information about all VMT fields, refer to the Transaction Specs - Visa Money Transfer guide. |
TLV tags
Visa requires Money Transfer data to be presented in type-length-value (TLV) format, which is a method of encoding information in a single string, versus multiple EPX tags.
TLV data is grouped into a TLV_SETS tag, which is a set of two or more TLV elements. Various types of TLV sets exist, as described in the Transaction Specs - Visa Money Transfer guide.
TLV tag 007 from TLV set “SENDER”
Within the TLV set “SENDER,” TLV tag 007 contains the Sender Country Code. The originator must provide the sender’s country in this field on cross-border transactions and U.S. domestic transactions. This will use the 3-digit ISO numeric country code.
This is for the TLV set “SENDER”
- Mandatory: OCT and WLS Transactions
- Length: 3
- Format: Alphanumeric
TLV tag 011 from TLV set “SENDER”
Within the TLV set “SENDER,” TLV tag 011 contains the Sender Account Number. If the sender’s account number is available, the originator must provide it in this field. If the sender’s account number is not available, the originator must provide the Sender Reference Number in the SPECIAL_3 field.
- Mandatory: OCT and WLS Transactions
- Length: 34
- Format: Alphanumeric
TLV tag 012 from TLV set “SENDER”
Within the TLV set “SENDER,” TLV tag 012 contains the Sender Reference Number. If the sender’s account number is not available, the originator must provide the Sender Reference Number in this field. Even when the Sender Account Number is available, it is strongly recommended that the originator provides the Sender Reference Number in addition to the Sender Account Number.
- Mandatory: OCT and WLS Transactions
- Length: 16
- Format: Alpha-Numeric
TLV tag 001 from TLV set “TRAN_DATA”
Within the TLV set “TRAN_DATA,” TLV tag 001contains a numeric code that indicates the funding source. The possible values are provided in the table below.
Funding Source Code Values
| Value | Definition |
|---|---|
| 04 | Cash |
| 05 | DDA Account |
| 06 | Mobil Money Account |
| V1 | Visa Credit |
| V2 | Visa Debit |
| V3 | Visa Prepaid |
- Mandatory: OCT transactions
- Length: 2
- Format: Alphanumeric
TLV tag 005 from TLV set “TRAN_DATA”
Within the TLV set “TRAN_DATA,” TLV tag 005 contains the Business Application identifier. The table below provides the values for OCT and AFT transactions.
|
NOTE: Additional business application identifiers may be supported by the EPX platform please confirm with your relationship manager or integration specialist. |
Applicable OCT Business Application Identifier Values
| Value | Definition |
|---|---|
| AA | Account to Account / Sender and Recipient are tde same person |
| BA | I Value Description |
| BB | Business to Business |
| BI | Money transfer—bank-initiated |
| BP | Non-card bill payment |
| CP | Card bill payment* |
| FD | Funds disbursement* |
| GD | Government disbursement |
| GP | Gambling payout (other than online gambling) |
| LO | Loyalty and offers |
| MD | Merchant disbursement* |
| MI | Money transfer—merchant-initiated |
| OG | Online gambling payout |
| PD | Payroll/pension disbursement |
| PP | Person to Person / Sender and Recipient are not the same person |
| TU | Top-Up for enhanced prepaid loads* |
| WT | Wallet transfer (digital wallet) |
*U.S. domestic enhanced OCTs with the additional BAI values will be subject to the same conversion logic to merchandise returns, and network processing on both network 0002 and network 0003, as enhanced money transfer OCTs with a BAI value of AA or PP.
- Mandatory: OCT and AFT transactions
- Length: 2
- Format: Alpha
Applicable AFT Business Application Identifier Values
| Value | Definition |
|---|---|
| AA | Account to Account / Sender and Recipient are the same person |
| BI | Money transfer—bank-initiated (MCC 6012 - Only) |
| PP | Person to Person / Sender and Recipient are not the same person |
| TU | Top-up for enhanced prepaid loads |
| WT | Wallet transfer (digital wallet) |
- Mandatory: OCT and AFT transactions
- Length: 2
- Format: Alpha
REFERENCE_NBR
The REFERENCE_NBR field contains the Transaction Identifier from the WLS or AFT response. Having the transaction identifier from the WLS transaction is preferred over having it from an AFT transaction. The value is taken from the AUTH_SPECIAL_1 field in the response from the AFT or WLS request.
Optional: OCT Transactions
Response Fields
AUTH_SPECIAL_1
The AUTH_SPECIAL_1 field contains the Transaction Identifier. When a WLS is done, the transaction identifier from the response must be provided in the REFERENCE_NBR field of the OCT transaction request. When an AFT is done and there is no WLS transaction, the transaction identifier from the AFT must be provided in the REFERENCE_NBR field of the OCT request.
AUTH_SPECIAL_10
The AUTH_SPECIAL_10 field contains the WLS Data. When available this data would need to be sent in the SPECIAL_10 field during an OCT request.