Disputes and refunds
Liability shift, chargeback handling, and refunds for Google Pay payments.
Liability shift and fraud protectionAsk
The fraud liability outcome of a Google Pay transaction depends on the credential type. CRYPTOGRAM_3DS payments carry inherent liability shift from the moment they are processed. PAN_ONLY payments gain liability shift only if VINR's 3D Secure step-up passes.
| Credential | SCA compliant? | Fraud liability |
|---|---|---|
| CRYPTOGRAM_3DS | Yes — device-authenticated | Issuer bears fraud liability |
| PAN_ONLY — 3DS step-up passes | Yes | Issuer bears fraud liability |
| PAN_ONLY — 3DS step-up fails | N/A | Not applicable — VINR declines; payment never completes |
Liability shift covers fraud chargebacks. It does not remove a dispute from card scheme monitoring programs such as Visa VAMP. All disputes — including liability-shifted ones — count toward scheme dispute activity that VINR monitors on your behalf.
DisputesAsk
Google Pay payments are card payments on the VINR platform. If a customer disputes a transaction through their bank, VINR creates a dispute object and the standard dispute lifecycle applies — evidence submission, deadlines, outcomes, and fees all work the same as for any card payment. See Disputes for the full lifecycle, how to submit evidence, and how to keep your dispute rate low.
To identify a Google Pay payment in a dispute:
{
"payment_method": {
"type": "card",
"card": {
"wallet": {
"type": "google_pay"
}
}
}
}Evidence strategy by credential type
The credential type affects the strength of evidence you can provide for "fraudulent" or "unrecognized" disputes:
- CRYPTOGRAM_3DS — the one-time cryptogram and device authentication are strong counter-evidence for fraud claims. The cardholder actively authenticated on their device using biometrics or a PIN.
- PAN_ONLY after 3DS step-up — the 3DS authentication record provides liability shift and is valid counter-evidence. Include the authentication reference in your dispute evidence bundle.
Common dispute reasons for Google Pay
| Reason | Most likely credential | Notes |
|---|---|---|
fraudulent | PAN_ONLY | Card number was known to an attacker without device possession |
unrecognized | Either | Customer doesn't recognize "Google Pay" on their statement |
product_not_received | Either | Fulfillment or delivery issue — unrelated to credential type |
duplicate | Either | Check for double-submission on your side |
Clear statement descriptors prevent most "unrecognized" disputes — set a recognizable descriptor in your VINR account settings.
RefundsAsk
You can partially or fully refund any successful Google Pay payment. The refund goes to the underlying card, not to the Google Pay wallet specifically. The refund process is identical to a standard card refund — see Refund and cancel payments for instructions.
Refunding a payment that is already disputed does not resolve the dispute and can result in the customer being paid twice. Respond to the dispute instead; only issue a refund if you intend to concede.
Preventing disputesAsk
- Clear billing descriptors — set a recognizable statement descriptor so customers identify the charge. "Unrecognized" is the most preventable dispute type.
- 3D Secure — VINR routes PAN_ONLY transactions through 3DS automatically and CRYPTOGRAM_3DS is pre-authenticated. Both credential paths provide SCA compliance and dispute protection when authentication succeeds.
- Prompt fulfillment and tracking — keep shipping and delivery data on hand to rebut "product not received" claims.
- Easy cancellation for subscriptions — cancellation friction is the primary driver of
subscription_canceleddisputes.
See alsoAsk
Authentication methods
How CRYPTOGRAM_3DS and PAN_ONLY affect SCA and liability.
Disputes
Full lifecycle, evidence submission, and fees for any payment dispute.
Refund and cancel payments
Partially or fully refund a completed payment.
Last updated on