> 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 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://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=<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.