Question about how Chargify creates/handles ARB in Auth.net
Hello,
In our current application, we create ARBs in Authorize.net by using their ARB API. However, the initial charge is made using the billing API. Thus it is technically possible for the initial charge to succeed, but the ARB creation to fail. One example is if the initial charge is made with a credit card that will expire before the next recurring billing date. And below is the XML response back from Authorize.net containing the error:
<?xml version="1.0"
encoding="utf-8"?>3590ErrorE00018Credit Card
expires before the start of the subscription.
How would Chargify handle something like this?
And, when we create ARBs in Chargify, does Chargify essentially
hold the ARB data, and just issue one-time charges on
Authorize.net? Or does Chargify actually create an ARB on
Authorize.net? (Since technically, the former option is just as
workable, and might even be better depending on one's
perspective.)
Thanks!
Jason
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by David H. - Chargify on 10 Mar, 2010 03:25 PM
Jason,
Thank you for the email and question around Authorize.net ARB, Chargify does not use ARB at all so the case would be handled with no problem as we are sending the charges as they happen to the gateway. The first charge is what creates the subscriptions and then charges continue from there, even if the person changes the card in the future.
David H. - Chargify resolved this discussion on 10 Mar, 2010 03:25 PM.
jkwon re-opened this discussion on 10 Mar, 2010 06:48 PM
3 Posted by jkwon on 10 Mar, 2010 06:48 PM
This is the answer I was hoping to hear. Thanks! :)
Support Staff 4 Posted by Lance W. - Chargify on 11 Mar, 2010 02:46 AM
Glad to hear that's the answer you wanted :-).
I'm going to close this ticket, but just reply or create a new ticket if you have further questions.
Thanks.
--- Lance
Lance W. - Chargify resolved this discussion on 11 Mar, 2010 02:46 AM.