> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/faqs-and-troubleshooting/environment-and-testing/why-do-sandbox-payments-over-usd100-return-payment-amount-exceeds-the-terminals-maximum-limit.md).

# Why do Sandbox payments over $100 return “payment amount exceeds the terminal’s maximum limit”?

In the Sandbox environment, some test terminals are configured with a low maximum transaction amount. For example, Bead’s test server may enforce a $100 maximum transaction limit. If a payment request exceeds the configured terminal limit, the API returns a `400 Bad Request` response with a message similar to:

`The requested payment amount exceeds the terminal's maximum limit.`

This is expected behavior when the requested amount is above the terminal’s configured maximum. Reduce the `requestedAmount` and retry, or contact Bead if the terminal limit needs to be raised for testing.

In Production, maximum transaction limits can vary by merchant and terminal. These limits are typically higher than Sandbox test limits, but they depend on the merchant’s approval and configuration. Integrators should handle this error gracefully and display a clear point-of-sale message such as:

`This transaction exceeds the terminal's maximum allowed amount. Use a lower amount or contact support to request a higher limit.`

When contacting Bead Support, include the environment, `merchantId`, `terminalId`, requested amount, timestamp, and full sanitized error response.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bead.xyz/faqs-and-troubleshooting/environment-and-testing/why-do-sandbox-payments-over-usd100-return-payment-amount-exceeds-the-terminals-maximum-limit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.