API Change Log
Can't find what you're looking for? See our System Change Log
September 3, 2019
- The Authorize.Net API now supports the Card-on-File Mandate.
June 27, 2019
- In the production environment, the transHash element no longer sends a value. Use transHashSHA2 instead.
March 3, 2019
- In the sandbox environment, the transHash element no longer sends a value. Use transHashSHA2 instead.
September 20, 2018
- Changes to Accept Hosted:
- The expiration date field accepts expired dates, and changes the color of expired dates to red.
- The billing address includes a field for company name.
- The field labels are in Title Case for improved readability.
- The card number field supports the new series of Mastercard numbers.
- The eCheck.Net name of account field is marked as mandatory.
- The cursor no longer jumps between the credit card and expiry date fields in iOS devices.
- Scrolling issues on many mobile devices have been resolved.
- Security fixes.
- Changes to Accept Customer:
- Users of the legacy Hosted CIM service have been migrated to Accept Customer.
- The fax number field is no longer displayed in the billing address.
- The option to pay or add a new card is disabled until the customer completes all mandatory fields.
- The expiration date field accepts expired dates, and changes the color of expired dates to red.
- The billing address includes a field for company name.
- The field labels are in Title Case for improved readability.
- The card number field supports the new series of Mastercard numbers.
- The eCheck.Net name of account field is marked as mandatory.
- Scrolling issues on iOS have been resolved.
- Security fixes and enhancements.
- Changes to the Accept.JS UI:
- The scroll position in the pop-up window is fixed.
- The expiration date field accepts expired dates, and changes the color of expired dates to red.
- The card number field supports the new series of Mastercard numbers.
November 2, 2017
- New mobile optimized, hosted payment form option for our JavaScript library.
October 17, 2017
- Added the ability to include a list of transactions generated by a subscription as part of ARBGetSubscription.
July 28, 2017
- Developers can now access Account Updater Job Summary and Account Updater Job Details reports
July 7, 2017
- Developers can now obtain the Issuer Identification Number for customer profiles
“GetCustomerProfile, GetCustomerPaymentProfile now accept an input parameter includeIssuerInfo. When included in the request and set to true, these API methods will return the Issuer Identification Number (also known as the IIN or BIN). Default behavior, when the parameter is not passed, will remain unchanged”.
May 15, 2017
- getMerchantDetails now returns the Public Client Key
March 28, 2017
- GetTransactionList, GetUnsettledTransactionList and GetTransactionDetails APIs will now return the customer profile and payment profile IDs used to create a transaction.
- New API method GetTransactionListForCustomer returns all transactions created by a specified customer profile (and optionally a specific customer payment profile).
- CreateTransaction and CreateSubscription now support using a default payment profile if one exists.
- GetCustomerProfile now supports searching by the merchant-specified merchantCustomerId or email address if they are unique when created.
December 15, 2016
- New Fraud Management API to list and update transactions held for AFDS review
- New getMerchantDetailsRequest reporting method returns gateway configuration details
- Specify a default payment and shipping profile for a customer profile
- Including a Customer Profile ID with createTransactionRequest will add a new Payment Profile
November 30, 2016
- Initial release of Webhooks support for system event notification
November 7, 2016
- Paging introduced for Reporting APIs with addition of <totalNumInResultSet> and paging request parameters
- SOAP API is now deprecated, developers should begin moving to the Authorize.Net API
- Hosted CIM End-of-life scheduled for on March 1, 2018
August 10, 2016
- Accept.js payment nonce can now be used with create subscription and create customer profile requests
- getCustomerProfile will return an unmasked expiration date if <unmaskExpirationDate> is true
- Expanded support for IP address whitelisting to customer profiles, recurring billing and reporting API requests and will return E00118, "The transaction was submitted from a blocked IP address" if not on the whitelist.
July 13, 2016
- We now return the card type with every customer profile request: GetCustomerPaymentProfile, GetCustomerProfile and GetCustomerPaymentProfileList.
- eCheck.Net settlement is now enabled in the sandbox along with simulation of Returns and Notifications-of-Change using our updated Testing Guide.
June 29, 2016
- New Authorize.Net Accept.js library provides developers with control over the user experience while reducing PCI DSS scope.
June 6, 2016
- The entryMode field in the transaction response is only returned for card present transactions.
- Enhanced Visa Checkout to allow developers to override the original intent amount when using createTransactionRequest. This is useful for adding shipping and handling to a transaction.
- Deprecated Hosted CIM and replaced with Authorize.Net Accept Customer
May 18, 2016
- Resolved issues with PayPal, added new response field for Email.
- Enhancements and bug fixes for customer profile transactions.
March 15, 2016
- 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.
February 18, 2016
- Customer Profiles associated with subscriptions are now visible within the Merchant Interface
- Subscriptions associated to a profile are displayed in the description field for a profile
- Payment Profiles can be removed if they are not assciated to an active or suspended subscription
November 3, 2015
Recurring billing now uses customer profiles for payment data
- GetCustomerPaymentProfile can return 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
June 23, 2015
Added authenticateTestRequest which can be used to validate API Login ID and Transaction Key.
June 8, 2015
Added support for Visa Checkout.
March 15, 2015
Added support for Charge a Tokenized Credit Card.
March 3, 2015
Added additional API options for Hosted Profile Page (hostedProfileBillingAddressRequired & hostedProfileCardCodeRequired).
January 4, 2015
Maintenance release including updates to GetSubscriptionList (paging issues), CreateProfileFromTransaction
(profile data in MINT) and ApplePay (creating profiles).
November 17, 2014
Added beta support for JSON message format.
September 16, 2014
Ability to create a customer payment profile WHILE creating a transaction with that same payment data, simply by passing a createProfile flag.
Ability to create a customer payment profile FROM a previous payment transaction, simply by passing the transaction ID of the existing transaction.
September 9, 2014
Added support for Apple Pay.
July 22, 2014
Added ARBGetSubscriptionList method to return list of subscriptions for a specific merchant.
Pass customer profile IDs with createTransaction as the source for payment.
May 15, 2014