Update 2/18/206
This release is now live in production.
Update: 2/2/2016
This release will be delayed. At present we don’t have a new release date but will update this post when one is available.
I'd recommend subscribing to this article so that you'll be alerted via email if there are updates. To subscribe, click Article Options at the top of this thread and then select Subscribe. You'll receive an email when there are updates.
As previously announced, we are finalizing work that will allow you to use Customer Information Manager (CIM) profiles with our Automated Recurring Billing (ARB) service and vice versa. This means that if you are using both CIM and ARB, you can now use customer profiles for recurring subscriptions as well as one-time payments.
The last stage of this project is being released between January 28 and February 2, 2016. As part of that release, we are creating customer profiles for your existing ARB subscriptions. Those newly created profiles will be viewable in the CIM section of the Merchant Interface along with any other profiles you’ve already created.
To view which ARB subscription (if any) a profile is associated with, simply check the Description field of the profile—any associated subscription ID will be viewable there.
You can edit and update the customer profiles with new payment and customer information. Any new information entered on a profile tied to a subscription will be used for the next recurring payment.
Also, please note that if you try to delete a profile that has been created based on an active or suspended ARB subscription, you will receive the error, “The specified customer/payment profile is associated with a subscription and cannot be deleted.” However, you will still be able to delete any profiles that are associated with expired, canceled or terminated ARB subscriptions.
As a reminder, Authorize.Net permanently deletes all expired, canceled or terminated ARB subscriptions (and their associated profiles) that are more than two years old.
Additional API Enhancements
Along with the changes above, we will be updating the following three API calls in a future release:
- ARBCreateSubscriptionRequest will be able to accept Customer Profile IDs to populate the customer and payment information.
- ARBUpdateSubscriptionRequest will also be able to accept Customer Profile IDs.
- CreateProfileFromTransactionRequest will allow updates to the customer information, if it is missing from the original transaction.
Once the API enhancements above have been released, we will make another blog post in the Developer Community.
