> For the complete documentation index, see [llms.txt](https://docs.blockchain.com/pay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockchain.com/pay/getting-started/testing-your-integration.md).

# Testing your integration

When your account is opened, your widget will support users using your company email address only ie. members of your team. Those users be will using live production systems so that you see exactly what your customers see. This means you can use real identity documents when onboarding and use real credit and debit cards in the app to buy crypto.&#x20;

{% hint style="info" %}
All information, including identify documents, will be held securely according to our production standards.
{% endhint %}

## Custom fees and balances&#x20;

Speak to us about how to manage fees and crypto balances for testing. Reach out to your account manager or drop us an email on <pay@blockchain.com>.


---

# 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.blockchain.com/pay/getting-started/testing-your-integration.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.
