topic Re: Testing the Account Updater in sandbox with test account in Integration and Testing

Testing the Account Updater in sandbox with test account

pradeep82 — Mon, 11 Dec 2017 18:48:35 GMT

Hi,

We have enabled Account Updater in our sandbox during month of September and as mentioned in the forum to test the changes in Sandbox we can use following cards.

4000001864810239 NAN

5111111015486814 NAN

We made payments using the above cards and still we are unable to see the change in the card number for our testing.

Any help would be appreciated.

Re: Testing the Account Updater in sandbox with test account

bhav — Mon, 11 Dec 2017 19:02:43 GMT

@pradeep82 Do you mean you have enabled account updater in https://account.authorize.net and testing whether the real credit cards updated in your own sandbox env (not Authorize.NET sandbox)?

Re: Testing the Account Updater in sandbox with test account

pradeep82 — Mon, 11 Dec 2017 19:10:59 GMT

No we have enabled the account updater in sandbox(https://sandbox.authorize.net/). This credit cards are test card provided by Aaron.

Below is his reponse for one of the thread.

There's no way to trigger an update, even in sandbox. What I do have for you, though, is a list of credit card numbers that Account Updater will do something about in sandbox. Using this list, you can at least test a variety of scenarios when the process actually does run.

We'll update our online testing guide with this list soon, but in the meantime, here's the card numbers:

Card Number	Expected Result
4000001864810239	NAN
4000007113112087	NED
4000002055487183	ACL
4000003586276236	CCH
5111111015486814	NAN
5111111069713154	NED
5111111018673020	ACL
5111111073508855	CCH

Re: Testing the Account Updater in sandbox with test account

pradeep82 — Wed, 20 Dec 2017 18:40:38 GMT

As a vendor of an enterprise application product we promote Authorize.Net as our vendor of choice for credit card processing and provide a built-in integration. We would like to promote this new account updater feature of Authorize.Net to our customers but are not comfortable doing so if we cannot see that it actually works in the sandbox. We know several customers are interested in it but don't want to be in a situation where we have to tell them 'we haven't been able to get it to work'...which is exactly the situation we are in now. Please help us make this work in the sandbox so we can continue to promote Authorize.Net to our customers.

Re: Testing the Account Updater in sandbox with test account

Anurag — Wed, 20 Dec 2017 21:37:13 GMT

@pradeep82

Thanks for being patient on it .

We have confirmed the AU service is now running in our certTest and you should be able to see the results for it .

Re: Testing the Account Updater in sandbox with test account

hl47 — Tue, 02 Jan 2018 22:27:11 GMT

@Anurag

I am working with @pradeep82 to test the AU service. I've made a payment with a visa credit card

4000001864810239 which is one that should be updated by the AU service. When I logon to the authorize.net sandbox and look at the CIM profile for that customer, I do not see the credit card number updated. How did you confirm that the AU service is running in your test environment?

CIM Profile:

Customer Profile Information

Customer Profile ID:	1813177575
Customer ID:	DP-54-1506708986425
Email:
Description:	Smith, Joe

Payment Profile(s)

1807829868

History | Edit | Delete

100 great oaks
95121

CC: XXXX0239
Expiration Date: 12/21

Payment pfoile History:

Trans ID	Invoice Number	Trans Status	Submit Date	Customer	Card	Payment Method	Settlement Date	Settlement Amount
60037345831		Captured/Pending Settlement	02-Jan-2018 13:44		V	XXXX0239		50.00
60030896387		Settled Successfully	29-Sep-2017 11:20		V	XXXX0239	29-Sep-2017 18:55	804.75
60030896244		Settled Successfully	29-Sep-2017 11:17		V	XXXX0239	29-Sep-2017 18:55	423.25
60030896230	none	Voided	29-Sep-2017 11:17		V	XXXX0239	29-Sep-2017 18:55	0.00

Re: Testing the Account Updater in sandbox with test account

Anurag — Wed, 03 Jan 2018 19:22:35 GMT

Hi @hl47

I just confirmed with the team that the AU job on sandbox runs on every 16th of the month .

Can you check it after the 16th if you still have the issue ?

Thanks

Re: Testing the Account Updater in sandbox with test account

pradeep82 — Fri, 19 Jan 2018 21:05:09 GMT

Thanks it worked.

Re: Testing the Account Updater in sandbox with test account

HeathN — Wed, 31 Jan 2018 23:47:35 GMT

Can we expand on the expected behavior for the provided card numbers?

Card Number	Expected Result
4000001864810239	NAN
4000007113112087	NED
4000002055487183	ACL
4000003586276236	CCH
5111111015486814	NAN
5111111069713154	NED
5111111018673020	ACL
5111111073508855	CCH

Will these account updates occur for any payment profile that has these numbers every month?

Will this update the payment profile and will I need to change this to one of the above numbers again within the CIM for this to run in the following month?

Some form of a testing guide or FAQ and the ability to manually trigger an account updater run would be good.

It has been a painful process to begin to develop against this feature as there is no reliable way to quickly test if our integration is working as intended.

Re: Testing the Account Updater in sandbox with test account

hl47 — Tue, 20 Feb 2018 19:26:06 GMT

Anurag, can you confirm that the AU job ran in the sandbox for February? As of Feb. 20th, I do not see a new account updater report and the test credit cards do not reflect updated numbers.

Re: Testing the Account Updater in sandbox with test account

HeathN — Fri, 23 Feb 2018 02:23:31 GMT

From the testing guide I see the following:

"The Account Updater process in the developer sandbox runs at the same frequency as in production (once per month). Results are available the following month. There is no function to manually trigger an update."

On February 5th, we put in all of the card numbers to generate expected results. From what I can tell by looking at the payment profiles, the updates ran. However, when I look at the account updater in the Sandbox UI, I can only query up to Januray where there are not updates. If I use the API directly and call to February I see the changes I expect. Is there a plan to update the UI to show the latest run as soon as it is done?