Question
Synechron
IN
Last activity: 10 Jul 2024 20:58 EDT
Pega Smart Dispute for issuer - (functionality : pending auth txns)
Pega Smart Dispute (functionality : pending auth txns)
-------------------------------------------------------------------------
1. What is the significance of GUIDHigh and GUIDLow in Pega Smart Dispute?
2. Does this fields used to fetch pending transaction from end system or every bank will have another field rather than GUIDHigh and GUIDLow from PegaCardFS-Data-Transaction-Card ?
3. Does this field used for invoking the VROL APIs
"AccountDetails": {
"AccountNumber": "4752999999999991",
"TxnList": [
{ "GUIDHigh": "2128617835103245123",
"GUIDLow": "2128617835103245124",
Pegasystems Inc.
IN
Pending auth transactions in the Smart Dispute were implemented by taking into account of these 2 fields namely GUIDHigh and GUIDLow. The significance of these 2 fields is that while identifying the posted transactions for the pending transactions being disputed these 2 values will act as the identifier. Generally its the Issuing bank's implementation team that need to populate these 2 values in both the places and this is only used for identifying the correct posted transaction for the pending auth transaction being disputed, otherwise these are not used in any of the VROL API's.
Synechron
AU
@dhans1 Thank you for your response. I have a few follow-up questions for clarification:
- If the issuing bank has only one unique identifier for identifying a pending authorization transaction, should this identifier be mapped to GUIDHigh or GUIDLow?
- When processing Straight Through Processing (STP) for pending authorization transactions, both GUIDHigh and GUIDLow are required. Can we use the issuing bank's unique identifier instead of these two fields, and make the necessary changes in the mapping rule? Or should we enter this unique identifier into both GUIDHigh and GUIDLow?
- I noticed that for Visa Resolve Online (VRAD), the Dispute submission uses the TransactionID to submit the fraud report, and GUIDHigh is set to the TransactionID field sent to Visa. Could you please explain the significance of this?
Thanks,
Ashwani