Hi,
We have been testing the Visa In-App Provisioning (VIAP) API, specifically the behavior of the nameOnCard field in CardInfo, which is documented as a conditional parameter. Below are our findings based on different scenarios.
Additionally, we confirmed that for card number 4382140000007538, the corresponding nameOnCard is "CHJHHB" based on our card system.
Scenario 1: Apple Pay - Without nameOnCard
CardInfo Used in Request:
{
"accountNumber": "4382140000007538",
"cvv2": "731",
"expirationDate": {
"month": "01",
"year": "2031"
}
}Response:
{
"errorResponse": {
"status": 422,
"reason": "nameOnCardUnavailable",
"message": "Name on Card is Unavailable"
}
}Observation:
Apple Pay requires nameOnCard, otherwise, it fails with a 422 error.
Scenario 2: Apple Pay - With nameOnCard
CardInfo Used in Request:
{
"accountNumber": "4382140000007538",
"cvv2": "731",
"nameOnCard": "CHJHHB",
"expirationDate": {
"month": "01",
"year": "2031"
}
}Response:
{
"errorResponse": {
"status": 422,
"reason": "nameOnCardUnavailable",
"message": "Name on Card is Unavailable"
}
}Observation:
Even when nameOnCard is included, Apple Pay still fails with the same 422 error.
Scenario 3: Google Pay - Without nameOnCard
CardInfo Used in Request:
{
"accountNumber": "4382140000007538",
"cvv2": "731",
"expirationDate": {
"month": "01",
"year": "2031"
}
}Response:
Success
Observation:
Google Pay does not require nameOnCard, and the request succeeds when omitted.
Scenario 4: Google Pay - With nameOnCard
CardInfo Used in Request:
{
"accountNumber": "4382140000007538",
"cvv2": "731",
"nameOnCard": "CHJHHB",
"expirationDate": {
"month": "01",
"year": "2031"
}
}Response:
{
"errorResponse": {
"status": 404,
"reason": "notFound",
"message": "The requested resource does not exist."
}
}Observation:
When nameOnCard is included, Google Pay fails with a 404 Not Found error.
Key Questions:
For Apple Pay:
- The API documentation states nameOnCard is conditional, yet Apple Pay always fails with nameOnCardUnavailable regardless of whether it is included.
- Could this be related to a missing issuer configuration, or is there another requirement we should check?
For Google Pay:
- Google Pay succeeds when nameOnCard is omitted but returns 404 Not Found when it is present.
- Is nameOnCard unsupported for Google Pay, or is there an API configuration issue?
Would appreciate any insights on whether these behaviors align with Visa’s API expectations or if there’s a possible misconfiguration on our side.
