Identifying transaction uniquely

[Jyothi844]

Hi,

I am using Fund Transfer API . How to identify a transaction uniquely with Pull Funds Post or Push Funds Post or Reverse Funds Post.

I have found a reference in VISA DIRECT documentation saying "Visa expects unique values for retrievalReferenceNumber, acquiringBin, cardAcceptor.terminalId or cardAcceptor.idCode to avoid the duplicate transaction and consistency errors."

1. What is  retrievalReferenceNumber, acquiringBin are same but cardAcceptor.idCode varies? In this case whether the transaction is considered as duplicate or not?

2.Is the combination of  retrievalReferenceNumber, acquiringBin, cardAcceptor.terminalId or cardAcceptor.idCode has to unique or only retrievalReferenceNumber has to be unique?

3.What to use cardAcceptor.terminalId or cardAcceptor.idCode as unique parameter?

[SLi · Accepted solution]

Hi @Jyothi844,

I have reached out to our product team for answers to your questions. I will get back with an update as soon as I have the answers. Thanks.

[SLi]

We have answered the questions via email. Sharing it here with the community.

Question:

What are the parameters to identify a Pull Funds Post as unique. Is it by retrievalReferenceNumber, acquiringBin, cardAcceptor.terminalId or cardAcceptor.idCode? If yes, among cardAcceptor.terminalId or cardAcceptor.idCode, which one will be considered is terminalId or idCode in what scenarios?

Answer:

We have duplicate detection logic at API layer and VIP layer both if the same payload is sent within 24hours.

• At API layer - it is "Txn type + BIN+STAN+RRN"
• At VIP Layer- even if the txn has unique parameters which could skip the duplicate check at API side, VISANet does check on CAID and Amount details sent in the previous txn for the given ACQBIN and recipient card. VisaNet can respond back with RC94 with an error message "Consistency Er" which can range from 600,601 & 597
• As of current code logic at API side, Visa Direct API checks duplication on a few fields - transaction type (AFT, OCT etc), acquiringBIN, RRN, STAN, CAID, terminalID, transactionDate.
• We have a logic at API to check if all the above combination exactly matches , however for the request to really not get VIP reject, user should ensure to use unique RRN every time.