Visa Money Transfer Simulation
A cardholder cashes out $50 received from a peer-to-peer cash-transfer app.
This a similar transaction to Scenario 21: Card Load (Visa). However, the transaction in Scenario 21 is a Visa Money Transfer with trans_code: PMVH, whereas this is a Visa Money Transfer with trans_code: PMVT.
Prerequisites
Before performing this simulation, you must have the VSALD product parameter enabled.
Authorization
Call Create Simulated Card Authorization with these parameters:
| Parameter | Value |
|---|---|
accountNo | PAN or PRN |
amount | 50 |
association | visa |
merchantName | DollarSend App |
mcc | 6051 |
transType | 8 |
{
"echo": {
"provider_timestamp": null,
"provider_transaction_id": "",
"transaction_id": "472a0682-f594-4fd5-a2b3-d995f9fe4fc0"
},
"processing_time": 4.564,
"response_data": {
"auth_id": 222,
"auth_response_code": "00",
"auth_response_description": "Success"
},
"rtoken": "71866ac2-fc6d-45d1-b22f-65c424b3b7e6",
"status": "Success",
"status_code": 0,
"system_timestamp": "2025-02-26 14:40:13"
}
View the authorization
Call Get Authorization History to see the authorization:
{
"status_code": 0,
"status": "Success",
"processing_time": 0.388,
"response_data": {
"authorizations": []
},
"echo": {
"provider_transaction_id": "",
"provider_timestamp": null,
"transaction_id": "640dd87c-2010-43e0-9351-ec25168e20ba"
},
"system_timestamp": "2025-02-26 14:41:12",
"rtoken": "720f35d1-af5b-4add-a503-1d2218e24be2"
}
Card loads in the authorizations table are created in status: T, and Get Authorization History does not return entries in this status, neither in CV nor in Production.
Settlement
If you call Create Simulated Card Settlement with the auth_id from the simulated auth, the endpoint will return this error: 544-03: Authorization is already settled or in the wrong status.
Because the card load is in status: T, the simulator cannot settle it. This is different from how card loads operate in Production. In Production, the settlement batch file, which arrives a day or two after the card load authorization, settles the card load, and Galileo sends the SETL: setl event message.
Transaction created
Call Get All Transaction History to see the ledger entry.
transactions:[
{
"is_savings": false,
"deny_code": null,
"disputable": false,
"details": "Visa Money Transfer",
"act_type": "PM",
"act_type_description": "Payment",
"post_ts": "2025-02-26 14:40:13",
"amt": 50,
"source_id": "222",
"type": "VT",
"type_description": "Visa Money Transfer",
"trans_code": "PMVT",
"arn": "",
"merchant_id": null,
"external_trans_id": "",
"calculated_balance": 1100,
"ach_trans_id": null,
"auth_ts": "2025-02-26 14:40:13",
"prior_id": "0",
"card_id": "254",
"formatted_merchant_desc": null,
"network_code": "?",
"auth_id": "222",
"local_amt": null,
"local_curr_code": null,
"settle_amt": null,
"settle_curr_code": null,
"billing_amt": null,
"billing_curr_code": null,
"pmt_ref_no": "999102163165",
"credit_ind": null,
"mcc_code": null
}
]
Updated 17 days ago
