0
votes

I'm using the ARBUpdateSubscriptionRequest method via XML and Coldfusion. When I update an existing ARB record with a new credit card number and expiration date, the response I get back is successful and without error. When I look at the ARB record after the update via the Authorize.net interface the card number has not been updated. I can only see the masked number but have tested with different numbers to verify that the last four digits do not update.

I'm able to create ARB records and cancel ARB records successfully. If I pass an invalid SubscriptionID I get an error in the response and also if I try to update a canceled record I also get an error in the response. Why on a update do I get a success response, but the ARB record is not updated? It is possible to update credit card and expiration date on an existing ARB record, correct?

I'm passing the following values: amount, subscriptionID, totalOccurrences, cardNumber, expirationDate, customerID

My response messagecode is I00001. My response messagetext is "successful" and the response result code is "OK". It does not appear that any ARB record info is actually updated when viewing the record through the Authorize.net ARB interface on their website.

1
If you check the merchant interface, do your changes appear correct?rhldr
No, that is the issue, when I check the merchant interface no changes have taken place when I use the ARBUpdateSubscriptionRequest method. If I use the ARBCreateSubscriptionRequest or ARBCancelSubscriptionRequest method I do see the results immediately in the merchant interface.John Sieber
If you wait a few minutes, does the corrected information appear in the merchant interface?rhldr
@rhldr - unfortunately, not. Even a day or later the record is not updated. If I use the create or cancel methods the results update right away.John Sieber
I've tested this further in the sandbox and I'm able to update the subscription amount, but not the card number, expiration date or customer name. The api documentation lists that those values may be updated.John Sieber

1 Answers

1
votes

The issue was in the Authorize.net Recurring Billing API CFC that I was using. It is not adding the card number and expiration date when creating the XML to send during update calls.