Update - 11/12/2015
These changes are coming soon to our SDKs. We'll update here again when they are available.
Today we are announcing several new and improved Authorize.Net API methods and features:
- Recurring billing now uses customer profiles for payment data
- New GetCustomerPaymentProfile option returns unmasked expiration dates
- New GetCustomerPaymentProfilesList method provides consistent reporting API for customer profiles and subscriptions
- New GetSubscription method returns all information about a subscription including its status and customer profile IDs
- Improved CreateCustomerPaymentProfile will return ID of a duplicate profile if one already exists
Recurring Billing and Customer Profile Integration
Recurring billing now uses customer profiles for secure payment data storage. This means that customer profiles can now be used for both subscriptions and one-time payments. This release also provides enhanced API support for customer profiles within subscriptions as well as providing a new API method to report on customer payment profiles:
GetCustomerPaymentProfile
The enhanced GetCustomerPaymentProfile now returns an unmasked expiration date if you set the unmaskExpirationDate flag.
GetCustomerPaymentProfilesList
This is a new API method that is based on the recently added ARBGetSubscriptionsList. It provides a consistent reporting API for customer profiles and subscriptions. For example, using this method, developers can obtain a list of cards expiring this month along with their payment profile IDs.
GetSubscription
This is a new API method that returns subscription information including status and associated customer profile IDs. Please note: This method will supersede ARBGetSubscriptionStatus, which will be deprecated sometime in the future.
Sample Request and Response
CreateCustomerPaymentProfile
The error response for CreateCustomerPaymentProfile now returns the profile ID if a duplicate profile already exists.
8 Comments
