Recurring Billing Payment Data Converted to Customer Profiles
Many developers have told us they would love to use their Automated Recurring Billing (ARB) data with the Customer Information Manager (CIM). Some have even asked if we could move all their ARB card data over to CIM to provide more flexibility with recurring billing scenarios. The good news is that it’s already underway.
As of August 1, 2015, we completed phase two of this project where all recurring billing subscription payment information was converted to customer profiles. In future phases, we’ll add new features to our API, such as the ability to create a subscription from a customer profile.
Steps You Should Take Today
If you have an existing ARB integration, you should ensure that you are populating the customer fields (Merchant Defined Customer ID, Email) with real data and passing valid (and most likely unique) information when it is available. Going forward, we plan to use Customer Profiles as the main source of customer data, making it even more important to have accurate information on file.
What do you think about these changes?
If you have more ideas on how to improve the Authorize.Net API, visit our Ideas forum and let us know.
Richard
