Hi Visa Developers,
I am helping my organization to migrate to Visa's JSON version From Issuer API right now. Now I am having an issue with Token Inquiry GET request (POST request endpoints work perfectly fine for me). Do you know what could cause this issue?
Note:
1. x-pay-token seems OK as I don't receive invalid token from Visa.
2. The TokenRequestorId and TokenReferenceId used in the Token Inquiry GET request are taken from an active Visa token returned from TokenInquiryByPAN POST request. Assume Visa knows this token for sure.
Thank you!
Solved! Go to Solution
Hi @oyuan,
Are you an issuer, processor, or fintech? Which countries will you be using Visa Token Service for?
Hi Diana,
My organization is an Australian payment company, both an issuer(issuing our own cards) and also a processor(selling our services to other banks or financial institutions).
In terms of VTS JSON version api (Inbound to Visa) usage, our must-haves are:
1. PAN Lifecycle (POST)
2. Token Inquiry (GET)
3. Token Inquiry by PAN (POST)
4. Token Lifecycle (POST)
5. Update Cardmetadata (POST)
Nice-to-haves are:
1. Token Requestor Report
2. Retrieve Network Hub Push Provisioning Profiles
My question is about the Token Inquiry (GET).
FYI, I am referring to VTS API version 3.7 (23.05)
Hi @oyuan,
Please kindly let us know if you're an issuer, processor, or fintech? Also, which countries will you be using Visa Token Service for? Once you provide me with this information, I can provide you with more direction on who to reach out to for these answers.
HI @oyuan,
Glad to hear that you reached out to your regional point of contacts at Visa. That is the best route to take. Have a good day.