I have used your authorize.net plugin to complete standard transactions and found it pretty easy to use. My question though, is it advisable for me to leverage that functionality beyond just completing the initial transaction? I am interested in being able to programatically add/modify/delete a user in the Authorize.net Automated Recurring Billing (ARB) system. I realize this would require new API calls that are not part of your plugin.
I was hoping I might be able to leverage the API integration you already had and implement these as additional calls instead of having to rebuild it from scratch.
Here is how I envision it working:
1) We build a standard Chronoforms form that obtains the information from the user
2) The form uses your existing A.net plugin to complete the initial one-time transaction.
3) Upon successful completion of that transaction, it would then call the additional API methods to register a user in the ARB system.
Any advice or suggestions would be greatly appreciated.
Steve
I was hoping I might be able to leverage the API integration you already had and implement these as additional calls instead of having to rebuild it from scratch.
Here is how I envision it working:
1) We build a standard Chronoforms form that obtains the information from the user
2) The form uses your existing A.net plugin to complete the initial one-time transaction.
3) Upon successful completion of that transaction, it would then call the additional API methods to register a user in the ARB system.
Any advice or suggestions would be greatly appreciated.
Steve