Account Updater

You will need to successfully tokenise details on your initial (INIT) transaction in order to test the Account Updater solution - take a look here how to do this.

The test cases for the Account Updater solution use the expdate you send in the initial (INIT) authorisation request to simulate a specific response. To get started, please use the following test cardnumbers to get a successful response and tokenise a card:

Cardnumber	Response	Response Message	Description
4000011180138710	1	Transaction Success	Payment successfully authorised.
5100019221455924	1	Transaction Success	Payment successfully authorised.

To bypass the expiry date check in our test environment when processing the initial (INIT) request you must set the amount value to 233. If you do not set the amount value to 233, you will receive a 204 response code.

Setting the expdate to the values listed below will allow you to simulate the required response when the ACCOUNT_UPDATER request is submitted.

Visa

Expiry Date	Description	Status	New Cardnumber	New Expiry Date	Response Code
012017	Account number change.	1	Yes	Yes	A
022017	Closed account advice.	2	No	No	C
032017	Expiration date change.	1	No	Yes	E
042017	Non-participating BIN.	2	No	No	N
052017	Participating BIN, no match.	2	No	No	P
062017	Contact cardholder.	2	No	No	Q
072017	Match made, no change.	2	No	No	V

MasterCard

Expiry Date	Description	Status	New Card	New Expiry Date	Reason Identifier	Response Indicator
012016	Match made, update data (replacement card).	1	Yes	Yes	UPDATE	R
022016	Match made, udpated data (brand change).	1	No	Yes	UPDATE	B
032016	Closed account advice.	2	No	No	CONTAC	C
042016	Match made, expiry date update only.	1	No	Yes	EXPIRY	E
052016	Account valid, no update.	2	No	No	VALID	V
062016	Unable to find account - participating BIN.	2	No	No	UNKNWN	P
072016	Unable to find account - non-participating BIN.	2	No	No	UNKNWN	N

Auto Update

If you have chosen for Acquired.com to submit the ACCOUNT_UPDATER requests on your behalf and want to test this functionality, please see below:

The first step is to generate a 402 (Declined: Lost or Stolen Card) or a 325 (Declined: Card Expired) response code when processing against your successful initial (INIT) transaction – achieved by setting the expdate as detailed above.

The 402 / 325 response can be returned by simply setting the amount value to either 402 or 325 in your recurring (REBILL) request - so for a 402 (Declined: Lost or Stolen Card), set the amount to 402. Here is an example:

JSON

{
    "timestamp":"20170612200234",
    "company_id":"113",
    "company_pass":"password",
    "request_hash":"cc8882cb0437863f711432a1d143fe6e9f92ce74080a0f30a0dac3a718ad1c28",
    "transaction":{
        "merchant_order_id":"20170612200234",
        "transaction_type":"AUTH_CAPTURE",
        "original_transaction_id":"1234567",
        "subscription_type":"REBILL",
        "amount":"402",
        "currency_code_iso3":"GBP"
    },
}