404 on cardData endpoint for provisioning google pay

[quentinLi]

when i try to call the in-app provisioning google pay api，i got result "404", this is the detail,

url:  https://sandbox.api.visa.com/inapp/provisioning/cardData/googlePay?apikey=UUF9MVTUYD3EA9TD8SS321y6ro...

request: {
"vCardID": "v-123-f98b91af-77c9-4e78-a1fe-345268939401",
"deviceID": "MTcwOTIwMTMyMDA4NTIwZDZI",
"clientCustomerID": "iBzxylvWTDyR8jzZd1Hdlg",
"tokenServiceProvider": "V"
}

{"errorResponse": {
"reason": "notFound",
"message": "The requested resource does not exist.",
"status": 404
}}

can anybody kindly help me,  if any api need to be called or any init condition need to be configured before i call this endpoint

[jenn_kh]

Hi @quentinLi, Thank you for reaching out. One of our agents will get back to you soon. Until then, if any community member knows a solution, please feel free to reply in this thread. 

[API_Products]

Hey @quentinLi,

To address the issue you are experiencing with calling the In-App Provisioning Google Pay API and receiving a "404 Not Found" error, here are some steps and considerations based on the Visa Developer Platform documentation:

1. Endpoint URL Verification: Ensure that the URL you are using is correct and corresponds to the specific API endpoint for Google Pay provisioning. The URL should be:
```
https://sandbox.api.visa.com/inapp/provisioning/cardData/googlePay?apikey=<YOUR_API_KEY>
```
Verify that there are no typos and that the API key is correctly included.

2. API Key: Ensure that the API key you are using is valid and has the necessary permissions to access the Google Pay provisioning endpoint. The API key should be correctly configured in the Visa Developer Portal.

3. Service Activation: Confirm that the In-App Provisioning service is activated for your project in the Visa Developer Portal. You might need to enable this specific API in your project settings.

4. Request Payload: Verify that the request payload is correctly formatted and includes all required fields. Here is the sample structure of the request:
```json
{
"vCardID": "v-123-f98b91af-77c9-4e78-a1fe-345268939401",
"deviceID": "MTcwOTIwMTMyMDA4NTIwZDZI",
"clientCustomerID": "iBzxylvWTDyR8jzZd1Hdlg",
"tokenServiceProvider": "V"
}
```
Ensure that the `vCardID`, `deviceID`, `clientCustomerID`, and `tokenServiceProvider` are correctly specified.

5. Sandbox Environment: Make sure that you are using the correct sandbox environment URL. Sometimes, the sandbox environment might have different configurations or limitations compared to the production environment.

6. API Documentation: Refer to the official Visa Developer documentation for the In-App Provisioning API for Google Pay to ensure that you have followed all prerequisites and configurations. This includes any initial setup or configuration steps that might be required.

7. Error Response Analysis: The error response indicates that the resource does not exist. This could mean that either the endpoint URL is incorrect, the resource you are trying to access is not available in the sandbox environment, or there is a configuration issue with your API key or project setup.

8. Contact Visa Developer Support: If the above steps do not resolve the issue, it is recommended to contact Visa Developer support for further assistance. They can provide more specific guidance based on your account and project configuration.

Summary:

Ensure the URL is correct and corresponds to the specific API endpoint. Verify the URL and API key are correct. Ensure the API key is valid and has necessary permissions. Check API key configuration in the Visa Developer Portal. Confirm that the In-App Provisioning service is activated. Enable the API in your project settings. Verify that the request payload is correctly formatted and includes required fields. Ensure all fields are correctly specified. Ensure you are using the correct sandbox environment URL. Verify sandbox environment configurations.
Refer to the official Visa Developer documentation for all prerequisites. Follow all setup and configuration steps. The resource does not exist indicates a potential configuration issue. Check endpoint, resource availability, and configurations.