Currently, looks like VISA API can only take one merchantName per request?
Can it also take multiple ?
Eg: Can I send merchantName1,merchantName2,merchantName3....in a single payload and get the responses accordingly?
Solved! Go to Solution
I'll take a look and get back to you soon.
For Merchant Search, sandbox is used for testing purposes and you are only seeing a merchant show up in the response because this is a sandbox limitation. Merchant’s data is limited to USA only and sandbox data is limited to a few merchants only.
@DianaTran-Yee : Thanks for your reply. BUt let me put my question in another way.
1. ) Here is the sample request Payload where I can send only 1 merchantName. Is there any other way to send it multiple merchants say Starbucks and HomeDepo in the same payload?
2. Also, currently via the sandbox I'm only getting one matched response at a time.
Yes, multiple merchants can appear in the response payload. For information please visit Merchant Search documenation here - https://developer.visa.com/capabilities/merchant_search/docs
Please note that sandbox is used for testing purposes, you are not seeing more than one result in the response because this is a sandbox limitation.
Things to Know
Merchant Search helps enhance the power of your services by providing access to Visa- accepting merchant identification data that uses Visa’s transaction data, third party data, and other systematic intelligence to improve data quality across the Visa payment network.
The Merchant Search API lets clients find the merchant identification information using the acquirer provided Merchant Name and other attributes such as address and card acceptor identifiers.
All merchants will be assigned one or more Group Name(s) that are configured with attributes. When the clients specify the Group Name in the request, the attributes assigned to such Group Name will be sent in the response.
The clients can use the wildcard search with the Merchant Name when at least the first 3 characters of the Merchant Name are known.
Max Records per Request
The clients can use the maximum record functionality to limit the number of records returned in response to each request. When maximum record is not defined, a default of up to 50 records will be sent in the response.