> 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/testing.md).

# Testing

## Testing

Bead supports several ways to validate your integration in Sandbox. This section helps you choose the right test method and links to a step by step guide for each one.

### Choosing a Test Method

For most integrators, **Klarna is the recommended default**. It exercises the full end to end payment flow, create payment, hosted checkout, completion, and webhook or status confirmation, without requiring any real assets. Klarna provides sandbox test credentials, so you can prove your integration works before touching a live wallet or crypto network.

Pick your test method based on your terminal type and what you need to prove.

| Test method                       | Terminal type        | Real assets required?                                              | Best for                                                                      |
| --------------------------------- | -------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
| **Klarna** (recommended)          | Virtual and physical | No. Uses Klarna sandbox test credentials                           | The default way to prove the full payment flow works, on either terminal type |
| **Venmo**                         | Virtual only         | No. Sandbox does not draw from a live wallet                       | Validating the wallet redirect and QR flow on a virtual terminal              |
| **PayPal**                        | Virtual only         | No. Uses a sandbox PayPal test account                             | Validating the wallet approval flow on a virtual terminal                     |
| **Crypto** (USDC, BTC, Lightning) | Virtual and physical | Yes. Live blockchain networks, real assets plus network fee tokens | Only when you specifically need to validate a crypto tender                   |

#### Start here

If you only need to confirm that your API keys, terminal configuration, hosted payment page, and webhooks all work together, run a **Klarna test** first. It is the fastest path to a completed payment and needs no funded wallet.

If you are integrating on a **virtual terminal** and want to validate wallet based tenders, you can also test **Venmo** and **PayPal**. Both complete in Sandbox without drawing from a live account.

Reach for **crypto testing** only when a crypto tender is in scope for your integration. Sandbox crypto payments run on **live blockchain networks and require real assets** plus a network fee token, so keep test amounts small.

#### Guides in this section

* **Test with Klarna (recommended)** — full sandbox walkthrough for virtual and physical terminals
* **Test with Venmo** — virtual terminal wallet flow
* **Test with PayPal** — virtual terminal wallet flow
* **Test Crypto Payments** — live network testing, wallet funding, and fee tokens
* **Run a Test Payment in the API Reference** — fire a test payment from your browser

#### Related

* [Test the Full Onboarding Workflow in Sandbox](/onboarding/test-the-full-onboarding-workflow-in-sandbox.md)
* [Testing Settlement in the Test Environment](/settlement/testing-settlement-in-the-test-environment.md)
* [Sandbox and production URLs](/faqs-and-troubleshooting/environment-and-testing/sandbox-and-production-urls.md)


---

# 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/testing.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.