How to find and interpret replay transaction in CA Transaction Manager
Article ID: 111489
Updated On:
Products
CA Payment Security
ARCOT ECOMMERCE
Issue/Introduction
How to find and interpret replay transaction in CA Transaction Manager in All transaction report or Transaction Report By Card number
This document helps in understanding below scenario:
1. What is Replay Transactions
2. How to identify Replay transactions What is Replay Transactions
This document helps in understanding below scenario:
1. What is Replay Transactions
2. How to identify Replay transactions What is Replay Transactions
Environment
CA Transaction Manager
Resolution
1. What is Replay Transactions?
A : When observe the "Purchase XID" field in the transaction report the numeric value prefixed to the value. Integer is prefixed to the value(Purchase XID) for all the duplicate transactions[REPLAY] attempts and callout status is always blank for Replay transactions[Duplicate Transaction].
e.g. Original Transaction : Purchase XID: NDgxNDYwMjg4NzkxNzk0OXXXXXAA=
Replay Transaction : Purchase XID: 6945:100:NDgxNDYwMjg4NzkxNzk0OXXXXXAA=
2. How to identify Replay transactions What is Replay Transactions
A : [REPLAY] Duplicate PAReqs(Payer Authentication Request) i.e. duplicate transaction request coming in with same Transaction Proxy-Pan are referred to as Replay Transaction inside CA product.
3D Secure Protocol documentation should contain information on duplicate transaction processing. As per the protocol specification, if a PARes(Payer Authentication Response) has already been sent for a transaction proxy pan then same PARes will be sent for the duplicate request coming in.
Product does not trigger duplicates, and in-fact has no control over the origin of such requests.
Duplicate PAReq can be due to multiple reason including the below:
A. Customer clicked the refresh button on the page multiple times.
B. Customer clicked the back button,.
C. Abnormal browser behavior causing to POST the same PAReq multiple times,
D. An issue with merchant application or a fraudulent attempt, etc.
A : When observe the "Purchase XID" field in the transaction report the numeric value prefixed to the value. Integer is prefixed to the value(Purchase XID) for all the duplicate transactions[REPLAY] attempts and callout status is always blank for Replay transactions[Duplicate Transaction].
e.g. Original Transaction : Purchase XID: NDgxNDYwMjg4NzkxNzk0OXXXXXAA=
Replay Transaction : Purchase XID: 6945:100:NDgxNDYwMjg4NzkxNzk0OXXXXXAA=
2. How to identify Replay transactions What is Replay Transactions
A : [REPLAY] Duplicate PAReqs(Payer Authentication Request) i.e. duplicate transaction request coming in with same Transaction Proxy-Pan are referred to as Replay Transaction inside CA product.
3D Secure Protocol documentation should contain information on duplicate transaction processing. As per the protocol specification, if a PARes(Payer Authentication Response) has already been sent for a transaction proxy pan then same PARes will be sent for the duplicate request coming in.
Product does not trigger duplicates, and in-fact has no control over the origin of such requests.
Duplicate PAReq can be due to multiple reason including the below:
A. Customer clicked the refresh button on the page multiple times.
B. Customer clicked the back button,.
C. Abnormal browser behavior causing to POST the same PAReq multiple times,
D. An issue with merchant application or a fraudulent attempt, etc.
Additional Information
Quick Overview
1. All Purchase XID is unique for every Transaction Proxy PAN.
2. For Original transaction Proxy PAN :/yr1vOgpSSKd6KGoP9eHbQQHBQg=
Original Purchase XID : NDUxNTM0NDcyOTUyMTYzNgAAAAA= & if same transaction is denoted as Replay then
Replay Purchase XID : 2977:84:NDUxNTM0NDcyOTUyMTYzNgAAAAA=
>>Replay transaction Purchase XID: <A numeric value with colon ":"><XID>
3. The correct way to identify replay transaction is by looking at the purchase XID column. A replay transaction has a random number prefixed to the value of purchase XID.
Feedback
Yes
No
Powered by
