> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-commerce/add-ons/payment-providers/paypal.md).

# PayPal

Getting Started with the PayPal payment provider for Umbraco Commerce.

The PayPal payment provider allows you to capture payments via the [PayPal](https://paypal.com) payment gateway. It is a fully featured payment provider allowing full control of the payment flow directly from the Umbraco Commerce backoffice.

Before you begin, ensure that you have an Umbraco website set up and Umbraco Commerce installed. If not, see the [Umbraco Commerce Documentation](/umbraco-commerce/readme.md) to get started.

## Install PayPal

To Install the PayPal payment provider, see the [Install Payment Providers](/umbraco-commerce/add-ons/payment-providers/install-payment-providers.md)

## Useful links

Here are a few useful links to help you learn more about the PayPal payment provider and the PayPal API:

* [Payment provider source code](https://github.com/umbraco/Umbraco.Commerce.PaymentProviders.Paypal)
* [Payment provider issue tracker](https://github.com/umbraco/Umbraco.Commerce.Issues/issues)
* [PayPal checkout documentation](https://developer.paypal.com/docs/checkout/)


---

# 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://docs.umbraco.com/umbraco-commerce/add-ons/payment-providers/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.