> For the complete documentation index, see [llms.txt](https://help.basiq-solutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.basiq-solutions.com/guide/guides/review-templates/paypal-review.md).

# PayPal review

What PayPal asks for during a review and how to prepare each document, plus the message templates.

{% hint style="danger" %}
Contact your manager immediately, **before** submitting anything. Do not submit documents without consulting us first.
{% endhint %}

{% hint style="info" %}
There is roughly a 70% chance the account gets reviewed or receives a hold in the first month. This is normal. Contact your rep immediately — they will push the risk team. Every new account also has a mandatory hold of about 21 days; ask your rep to push for removal.
{% endhint %}

## While waiting for the review

* Create a branded Facebook page → add 2–3 posts (2 hours apart)
* Make sure Shopify shows the reviewed product and only compliant products — hide anything that could be considered risky during the review period
* Connect PayPal to that store if not already done

## What PayPal typically asks for — and how to prepare it

**Bank statement** — the statement of the account connected to PayPal. It must show a balance of at least $100,000 USD.

**Tracking info** — the tracking number for each referenced transaction + the courier name (usually Yun Express — confirm first).

**Supplier invoice** — for each transaction, the invoice from your supplier. Do not use an invoice created after the referenced transaction; use the bulk purchase invoice from your supplier issued more than 1 week before the transaction, showing the order was fulfilled from existing stock.

Invoice message template:

> I am writing to confirm that transaction ID XXXXX has been successfully completed, accompanied by tracking number XXXXX. This transaction included X units of our XXXXX. These items were part of a recent bulk purchase from our company, and the invoice for this purchase is attached for your reference.

Business structure answer:

> Our business operates an e-commerce website specialising in the X niche, with a primary focus on our main product, X. Through the integration of PayPal on our website, we ensure an efficient payment experience for our customers during checkout.

**Warehouse location** — state that you have 2 warehouses: your Chinese supplier's address and your business address.

## Disputes during a review

Reply to every dispute within 24 hours with accurate product details, a shipping policy screenshot and the supplier's proof of delivery, and ask the customer to close the dispute — see the [PayPal Warm-Up Guide](/guide/guides/paypal-warm-up.md), sections 5–6.

{% content-ref url="/pages/xxfif2iYe5F8CnZ5dcMn" %}
[PayPal Warm-Up Guide](/guide/guides/paypal-warm-up.md)
{% endcontent-ref %}


---

# 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://help.basiq-solutions.com/guide/guides/review-templates/paypal-review.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.