How to Block Duplicate Transactions on CyberSource REST API

MurbiesWalto — Tue, 23 Aug 2022 11:43:48 GMT

he CyberSource payments system seems to have a method of preventing duplicate transactions, as covered here:

This functionality looks at the Merchant Reference Number (MRN) of successful orders submitted within the last 15 minutes of a previous order, and blocks any duplicate transactions submitted with the same MRN.

and here:

Reason Code 104: The access_key and transaction_uuid fields for this authorization request match the access_key and transaction_uuid fields of another authorization request that you sent within the past 15 minutes.

Although ome glz API it's obvious you need to use transaction_uuid for earlier APIs such as KVP, it's not clear which field to use for the REST API.

Re: How to Block Duplicate Transactions on CyberSource REST API

gjped2 — Thu, 25 Aug 2022 12:13:01 GMT

Good Morning Developer

The field I believe that you are looking for in the JSON based Rest API server is

/processorInformation/transactionId

this is grouped with the Auth server as well as when you put a capture with the Auth service

API Field Reference | REST API (cybersource.com)

we have found this a bit helpful as well but it is far from complete to be honest

topic How to Block Duplicate Transactions on CyberSource REST API in cybersource APIs

How to Block Duplicate Transactions on CyberSource REST API

Re: How to Block Duplicate Transactions on CyberSource REST API