> For the complete documentation index, see [llms.txt](https://hollow-peak.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hollow-peak.gitbook.io/docs/payments/paypal.md).

# PayPal

Accepting PayPal balance and cards through PayPal.

PayPal lets customers pay from a PayPal balance or with a card through PayPal, without a PayPal account in many countries.

## Before you start

You need a **PayPal Business** account. A personal account cannot take payments this way.

## Getting your credentials

1. Sign in at [developer.paypal.com](https://developer.paypal.com)
2. **Apps & Credentials**
3. Choose **Sandbox** while setting up
4. **Create App**, give it a name
5. Copy the **Client ID** and **Secret**

Sandbox and Live have separate tabs with different credentials.

## Configuring

**Payments → Settings → PayPal**

| Field         | Notes                        |
| ------------- | ---------------------------- |
| Enable PayPal | Tick                         |
| Mode          | **Sandbox** while setting up |
| Client ID     | From your PayPal app         |
| Secret        | **Stored encrypted**         |
| Webhook ID    | From the webhook step        |

## Webhooks

1. In your PayPal app, scroll to **Webhooks** → **Add Webhook**
2. Webhook URL:

   ```
   https://your-domain.com/webhooks/paypal
   ```
3. Subscribe to:

   ```
   CHECKOUT.ORDER.APPROVED
   PAYMENT.CAPTURE.COMPLETED
   PAYMENT.CAPTURE.DENIED
   PAYMENT.CAPTURE.REFUNDED
   ```
4. Copy the **Webhook ID** into Hollow Peak

{% hint style="info" %}
PayPal verifies webhooks differently from Stripe: it uses a **Webhook ID** that Hollow Peak sends back to PayPal for verification, rather than a shared signing secret. That is why the field is named differently.
{% endhint %}

## Sandbox testing

PayPal creates sandbox buyer and seller accounts under **Testing Tools → Sandbox Accounts**. Use the sandbox buyer's email and password at checkout — not your real PayPal login.

## Going live

1. Switch to the **Live** tab in the PayPal developer dashboard
2. Create a live app and copy its Client ID and Secret
3. Create a live webhook and copy its Webhook ID
4. In Hollow Peak, set Mode to **Live** and paste all three
5. Place one small real payment and refund it

## Common problems

| Symptom                                    | Cause                                                     |
| ------------------------------------------ | --------------------------------------------------------- |
| “PayPal credentials have not been entered” | Client ID or Secret missing                               |
| Authentication failure                     | Sandbox credentials with Mode set to Live, or the reverse |
| Order stays pending after payment          | Webhook missing or wrong Webhook ID                       |
| Currency rejected                          | PayPal does not support that currency in your account     |


---

# 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://hollow-peak.gitbook.io/docs/payments/paypal.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.
