Bien Nguyen
Mar 7, 2017
  2850
(4 votes)

[Authorize.Net payment gateway] Enable the Transaction Details API setting requirement

In the next EPiServer Commerce release (10.4.0), we've done some improvements for the Authorize.Net built-in payment gateway. Now when processing a payment, we send request to the authorize.net server to get transaction details of the payment. It helps us to know what status of the transaction is, that has never been done before. So that in case the transaction is processed manually on the Authorize.net web page, for example if the transaction was already captured or settled, then we don't need to process it in the gateway. Therefore it requires to enable the Transaction Details API on Authorize.Net accounts, including yours. Please enable it by following these simple steps:

1) Log on to the Merchant Interface at https://account.authorize.net .
2) Select Settings under Account in the main menu on the left.
3) Click the Transaction Details API link in the Security Settings section. The Transaction Details API screen opens.
4) If you have not already enabled the Transaction Details API, enter the answer to your Secret Question, then click Enable Transaction Details API.
5) When you have successfully enabled the Transaction Details API, the Settings page displays.

Regards.

Mar 07, 2017

Comments

Please login to comment.
Latest blogs
Boosting Graph Query Performance with Stored Templates

Stored Templates offer a solution by pre-generating and storing translated queries. This bypasses the time-consuming translation process, leading t...

Jonas Bergqvist | Feb 27, 2025

Exploring Optimizely SaaS CMS – What’s New & How to Accelerate your Build

In my latest video, I take a fresh look at Optimizely SaaS CMS , covering some of the recent improvements aimed at enhancing the editor experience....

Minesh Shah (Netcel) | Feb 27, 2025

Adaptive Images with Optimizely CMP

Images from Optimizely CMP can now be seamlessly integrated into Optimizely CMS through Adaptive Images, with the all same features that web editor...

Ted | Feb 27, 2025 |

Using the 1996 text-based Browser 'Links' to optimize website accessibility

Use a text-based browser from the late 1990s to improve the accessibility of your modern Optimizely website!

Tomas Hensrud Gulla | Feb 25, 2025 |

Using the 1996 text-based Browser 'Links' to optimize website accessibility

Use a text-based browser from the late 1990s to improve the accessibility of your modern Optimizely website!

Tomas Hensrud Gulla | Feb 25, 2025 |

Convert media type in a migrationstep

I needed to convert the type for some media files. Suddenly webp files were sent to the CMS from an external system and webp was not added to the...

Jeroen Stemerdink | Feb 24, 2025 |