Hi, if our service gateway times out while calling Push Funds/Pull Funds API is there anyway to get the status of the submitted(but unknown status) transaction? As per the GET API doc, it says need to pass "StatusIdentifier", is it same as RetrievalReferenceNumber sent in the POST API request?
Solved! Go to Solution
Hi Srinivas,
Thanks for exploring out Visa Direct functionalities.
Below are the replies to your queries.
1. If our service gateway times out while calling Push Funds/Pull Funds API is there anyway to get the status of the submitted(but unknown status) transaction?
Yes. If your gateway connection terminated abrubtly due to any reason before receiving any response from Visa, what you can do is to to re-submit the same request with exact request payload values. Visa will send you a response with "StatusIdentifier" value if the initial transaction you submitted is still processing at Visa.
Otherwise it will send the transactionIdentifier.
By re-submitting the exact payload, it does not make duplicated the transaction. Instead it will only return the status of the initial request.
Alternatively you can use the Reports API to retrieve status of all the transactions you have submitted to Visa.
2. As per the GET API doc, it says need to pass "StatusIdentifier", is it same as RetrievalReferenceNumber sent in the POST API request?
No. Status identifier is a value returns by the Visa if the api call you make times out at the Visa end. It is not same as the RetrievalReferenceNumber.
Hope my answers helps. Please let us know if require further clarifications/information.
Best regards
Lakshan
Hey @anor,
To implement 3-D Secure (3DS) with Visa Direct API, you will need to follow specific steps to ensure the sender confirms the transaction securely. Here’s a general outline to help you:
Initiate the PullFunds API Call: When you call the pullFunds
API, ensure that you have all required fields filled, including the redirectUrl
for 3DS.
Redirection to Issuer’s 3DS Page: After the pullFunds
API call, the server will return a URL where the sender needs to be redirected for 3DS authentication. Redirect the sender to this URL.
Sender Authentication: The sender will be prompted to confirm the transaction on the issuer’s 3DS page. This usually involves entering a password, OTP, or using another authentication method.
Handling the Response: Once the sender completes the 3DS authentication, they will be redirected back to your redirectUrl
. You need to handle the response at this endpoint to finalize the transaction.