> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/test-your-integration/test-your-integration/test-payment-methods/google-pay-test-orders.md).

# Google Pay test orders

## Overview

You can simulate both successful and failed Google Pay payments by controlling the outcome through the order amount. Simulation is automatically activated when the `DOTEST=1` parameter is present on the order — no additional configuration is required.

{% hint style="danger" %}
**Important!** Test orders never reach the live gateway.
{% endhint %}

***

## Availability

Supported for: Default Templates

***

## Trigger amounts for error simulation

Enter one of the amounts below to trigger the desired scenario. Any other amount returns a success.

| Amount (USD)     | Simulated scenario      | Message shown to the buyer                                           |
| ---------------- | ----------------------- | -------------------------------------------------------------------- |
| $0.01            | Card declined           | Generic "payment failed" message + retry CTA                         |
| $0.02            | Insufficient funds      | Friendly insufficient funds message                                  |
| $0.05            | Do not honor            | "Your card was declined"                                             |
| $0.07            | Stolen card             | Generic "payment failed" message *(actual reason is never revealed)* |
| $999.00          | Amount too large        | Amount-specific error message                                        |
| $9,999.99        | Transaction not allowed | Message with support contact hint                                    |
| Any other amount | Success                 | "Thank you" page                                                     |

Trigger amounts also work in NOK and SEK — USD is the recommended currency for testing.

***

## Cart setup

Fill in the cart fields with the following data:

* **Billing currency**: USD
* **Payment option**: Google Pay

***

## Payment flow

### Successful payment

1. Fill in the cart with an amount not listed in the error table above (e.g. $10.00).
2. Click the **Buy with Google Pay** button.
3. You are redirected to the Google page — sign in with your Google credentials.
4. Click **Next**, select a card, and click **Pay**.
5. You are redirected to the *Thank you* page — the test order has been recorded.

### Simulated error payment

1. Fill in the cart with one of the trigger amounts from the table above (e.g. $0.01 for card declined).
2. Click **Buy with Google Pay** and complete the Google authentication.
3. After processing, you are redirected back to the checkout page with the corresponding error message.
4. The cart and session are preserved — you can retry immediately with a different amount.

{% hint style="info" %}
**Notes:**

* The $0.07 scenario (stolen card) always displays a generic message regardless of template — the actual decline reason is never exposed to the buyer.
* Zero-value orders placed with Google Pay TEST always return success (FK\_AUTH\_SUCCEEDED), regardless of the amount entered.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.2checkout.com/test-your-integration/test-your-integration/test-payment-methods/google-pay-test-orders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.