Visa MoneyLink Simulation

A cardholder presents $60 at a retail store to load on their GPR card.

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 Visa MoneyLoad with trans_code: PMVL.

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`	`60`
`association`	`visa`
`merchantName`	`CornerDrug`
`mcc`	`6540`
`transType`	`7`

{
	"echo": {
    	    "provider_timestamp": null,
    	    "provider_transaction_id": "",
    	    "transaction_id": "c56941d6-cd9f-4c3f-bbba-56e1eeda26e6"
	},
	"processing_time": 4.752,
	"response_data": {
    	    "auth_id": 221,
    	    "auth_response_code": "00",
    	    "auth_response_description": "Success"
	},
	"rtoken": "13591383-bcdd-4e85-9d64-082b787572e0",
	"status": "Success",
	"status_code": 0,
	"system_timestamp": "2025-02-26 14:35:41"
}

View the authorization

Call Get Authorization History to see the authorization:

{
	"status_code": 0,
	"status": "Success",
	"processing_time": 0.454,
	"response_data": {
    		"authorizations": []
	},
	"echo": {
          "provider_transaction_id": "",
          "provider_timestamp": null,
          "transaction_id": "4f090c0a-ae70-4a96-927e-dad930905c6e"
	},
	"system_timestamp": "2025-02-26 14:36:40",
	"rtoken": "a14f32d7-cb11-431a-87a8-1a1039dc0546"
}

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. If the endpoint returns your transaction in the authorizations object, it means that the endpoint ignored the value in transType and created a conventional authorization instead of a card load, which debits the account instead of credits it. Verify that you have IOANV enabled for your product ID so that the endpoint will respond properly to the value in transType.

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:35:40",
            "amt": 50,
            "source_id": "221",
            "type": "VL",
            "type_description": "Visa Load",
            "trans_code": "PMVL",
            "arn": "",
            "merchant_id": null,
            "external_trans_id": "",
            "calculated_balance": 1050,
            "ach_trans_id": null,
            "auth_ts": "2025-02-26 14:35:40",
            "prior_id": "0",
            "card_id": "254",
            "formatted_merchant_desc": null,
            "network_code": "?",
            "auth_id": "221",
            "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
        }
]