Google Pay™️ Payments Error Status Code CANCELED: Canceled
The user dismissed the Google Pay sheet without authorizing, the browser/Google account is unsupported, the sheet was already open, or the PaymentDataRequest config was rejected. The loadPaymentData promise is rejected; no charge was made.
What it means
The CANCELED status code is a client-side response indicating that the Google Pay payment sheet was closed before a payment could be authorized. This occurs most commonly when the user explicitly dismisses the prompt, but it can also be triggered by an unsupported browser, an insecure HTTP context, or an invalid PaymentDataRequest configuration. Because this failure happens at the API layer, no authorization request is ever sent to the card network or issuer.
Classification & retryability
Automatic programmatic retries will fail if the underlying API configuration or HTTP context is flawed. Retries should only occur when triggered by the customer re-initiating the Google Pay process or selecting an alternative payment method.
Common causes
- The shopper manually closed or dismissed the Google Pay payment sheet without completing the authorization.
- The customer is attempting checkout using an unsupported browser or an unsupported logged-in Google account.
- The payment request originated from an insecure, non-HTTPS web context.
- The loadPaymentData method was invoked while a Google Pay payment sheet was already actively displayed to the user.
- The PaymentDataRequest configuration was rejected due to missing or invalid gateway tokenization specifications.
How to resolve it
Start by reviewing client-side logs to determine the exact trigger for the CANCELED response. If the issue stems from an insecure context, ensure your checkout environment enforces HTTPS. For configuration errors, validate your PaymentDataRequest payload, checking that the PaymentMethodTokenizationSpecification parameters perfectly match your payment gateway's requirements. To prevent double-firing, disable the Google Pay button immediately after it is clicked until the loadPaymentData promise resolves.
For merchants
Treat this as a checkout abandonment or integration error rather than an issuer decline. Log CANCELED outcomes separately from true card declines so they do not artificially inflate your fraud or decline rates. Implement intelligent fallback logic: if Google Pay fails due to browser support or user dismissal, seamlessly display alternative payment methods or a standard credit card entry form to save the sale.
For customers
If you accidentally closed the payment window, please click the Google Pay button to try again. If the issue persists, try checking out with a standard credit card or another available payment method.