cancel
Showing results for 
Search instead for 
Did you mean: 

eCheck.Net Return Codes in the Transaction Details API

We’ve updated the Transaction Details API to return information about the reasons for an eCheck.Net transaction failure. Coupled with our recent enhancements adding subscription information to the Transaction Details API, you now have similar reporting capabilities available to you through an API as you do through the Merchant Interface.

 

eCheckReturns.png

 

eCheck.Net Return codes are available using the Transactions Details API XML Interface or by using our latest SDKs available on GitHub. You can also test the new functionality using the API Reference Guide. Later this year, we will update the Error Generation Guide to include the ability to simulate specific eCheck.Net return codes.

 

Mobile SDK Updates for Android and iOS

We’re also excited to release the latest versions of our mobile SDKs. These SDKs allow you to build a mobile payment acceptance application using Authorize.Net APIs. The Authorize.Net mPOS Application is built on these same SDKs. 

 

Lastly, the SDKs are open-sourced on GitHub, and we invite your collaboration to support next generation apps using the Authorize.Net platform.

New Getting Started Guides

To complement our new API Reference Guide, we have added several new Getting Started Guides designed to help with specific transaction types, including:

 

  • One-Time Transactions
  • Recurring Billing
  • Customer Information Manager (Tokenization)

 

More Getting Started Guides will be added in the coming months. We hope you will provide feedback regarding the guides and any suggestions on what we should work on next.

Developer Center Home Page Refresh

Last, but not least, you may have noticed that our Developer Center home page has undergone a makeover. The new look is designed to provide access to what you need most, right up front, and better organize the resources available to you. Be sure to check it out today!

 

We hope you find all of these enhancements beneficial. Once you’ve had a chance to review these enhancements, let us know what you think. And while you’re at it, let us know what you think our next API enhancement should be.

 

RichardH
Administrator Administrator
Administrator
2 Comments