> For the complete documentation index, see [llms.txt](https://docs.bird.com/applications/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/applications/payments/bird-pay-beta/faqs/why-was-my-onboarding-unsuccessful.md).

# Why was my onboarding unsuccessful?

Unfortunately, there are some instances where Bird cannot proceed with an application for a payment account.

We may not be able to proceed with an application due to the business's location, restrictions and regulations imposed upon us by our various partners worldwide or if the business's use case falls outside the permissions and requirements of our [contract terms](https://bird.com/legal/product-specific-terms).

Due to regulations, we cannot share specific details about our onboarding decisions, including why an application was unsuccessful or rejected.

However, to better understand what businesses we can support, please see our [Terms & Policies](https://bird.com/legal/product-specific-terms). Our list of supported countries is also available [here](/applications/payments/bird-pay-beta/concepts/bird-pay-coverage.md).

<br>


---

# 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.bird.com/applications/payments/bird-pay-beta/faqs/why-was-my-onboarding-unsuccessful.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.