Recurring billing and customer profiles enhancements

by Administrator Administrator on ‎03-21-2016 08:18 AM (22,833 Views)

Several new API enhancements for recurring billing and customer profiles are now available.


Subscription IDs included with profile requests

Subscription IDs will be returned with all profile requests (customers, payment and address).




Enhanced ARBCreateSubscriptionRequest

Use a customer profile for the payment information when creating a new subscription.




Enhanced ARBUpdateSubscriptionRequest

When updating a subscription, you can now specify a customer profile for the payment information.




Enhanced CreateProfileFromTransactionRequest

Specify information that will update a customer profile with new or updated information (customer email, ID or description) that may be missing from the original transaction.





Improved createTransactionRequest

As requested, we’ve enhanced createTransactionRequest to allow you to specify address information and a payment profile for a particular transaction. If you include an address, it will be used for the transaction, but will not create a new address profile. 


Example: sending the order to a different address than the one on file, e.g. a gift for Mom or a friend.





Keep those suggestions coming! We continue to monitor our Ideas forum and other channels for enhancements.


Sample Code and SDK updates supporting these enhancements are available on Gitbhub.

by ctdavis
on ‎04-18-2016 06:23 AM

Hello today I am seeking why all sandbox authorize and capture transactions fail since first failure seen March 22 2016.  New customer profile creates fine, but upon authorize and capture I am given at 65/2 indicating failure of enhanced CCV.  The CCV works fine when creating customer profile, but then as part of profile (not retyped at auth & capture) supposedly is no good a moment later at authorize and capture. Makes no sense. Now I see new Authorize.Net changes available March 21. Maybe there is bug?  I set all four enhanced CCV option to approve, and that "fixes" issue  but when Authorize.Net changes roll to production I cannot do same "fix" there .

transaction IDs:


by kbrewer
on ‎05-17-2016 01:22 PM



I have also had issues recently with procesisng payments using a customer payment profile.  Prior to about 4/1/16 my clients were able to charge an account using a previously created customer payment profile without having to supply a CCV code.  This worked regardless of the CCV settings in their account.  After 4/1/16 they started receiving the error 2-65 specifying that a CCV code is required.


Was this change intended?  Is it a bug?  In order to remain PCI compliant my company does not store credit card information and has been using the customer payment profile to allow our clients to automatically processing payments.