> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/chord-oms-overview/checkout/stripe-paypal-checkout.md).

# Stripe Paypal Checkout

Stripe PayPal Checkout lets your customers pay with their PayPal account during checkout. PayPal appears as a payment option alongside credit cards on the Stripe-hosted checkout page. When a customer pays with PayPal, the order flows into Chord OMS just like any other order.

## How It Works

```mermaid
flowchart LR
    A[Customer<br>at checkout] -->|Selects PayPal| B[Stripe<br>shows PayPal option]
    B -->|Redirected to PayPal| C[PayPal<br>authorizes payment]
    C -->|Payment confirmed| B
    B -->|Order confirmed| D[Chord<br>fulfills the order]
```

1. **Customer goes to checkout** — The Stripe checkout page shows PayPal as a payment option alongside credit cards.
2. **Customer selects PayPal** — They are redirected to PayPal to log in and authorize the payment.
3. **Payment is processed** — PayPal confirms the payment through Stripe.
4. **Order is created** — The order appears in Chord, tagged and ready for fulfillment.

## Getting Started

Navigate to **Store** **->** **Integrations → Stripe PayPal** on Chord.

The setup page walks you through a 5-step checklist:

1. **Stripe API Key** — Your store must have a Stripe API key configured (auto-detected).
2. **Request Orchestration access** — Your Stripe account needs Orchestration preview access enabled by your Stripe account representative.
3. **Deploy PayPal adapter** — A bridge service that connects Stripe and PayPal must be running. **Note: This step must be handled by Chord, so please reach out at** **once you are ready!**
4. **Create Custom Payment Method** — A PayPal Custom Payment Method must be created in the Stripe Dashboard.
5. **Enter your token** — Paste the Custom Payment Method token (starts with `cpmt_`) into the settings.

Once all steps are complete, click **Enable** to turn on PayPal checkout.

{% hint style="info" %}
**Note:** If your store uses Chord's managed PayPal account, steps 2–4 may already be handled for you. In that case, you just need to enable the feature.
{% endhint %}

## Settings

All settings are accessible from the **PayPal settings page** once the feature is enabled.

### Token Configuration

* **Custom Payment Method Token** — The token that connects your checkout to PayPal (starts with cpmt\_). If your store doesn't have its own token, Chord's default token is used automatically.

### Order Processing

* **Order Channel** — The channel name assigned to PayPal orders (default: "PayPal"). Useful for filtering and reporting.
* **Order Tag** — An optional tag applied to all PayPal orders. Useful for identifying PayPal transactions at a glance.

## How PayPal Orders Appear

PayPal orders look and behave like regular orders in your admin panel, with a few differences:

* **Channel** — PayPal orders are assigned to their own channel (default: "PayPal") so you can filter them separately in reports.
* **Tag** — If configured, a custom tag is applied to every PayPal order.
* **Payment type** — The payment is recorded as "PayPal" rather than a credit card.
* **Customer info** — Billing and shipping details are synced from the customer's PayPal account.

## Refunds

**PayPal refunds must be processed through the Stripe Dashboard**, not through Chord OMS. The refund button is disabled for PayPal payments on Chord OMS to prevent any issues.

To refund a PayPal order:

1. Go to the Stripe Dashboard.
2. Find the payment.
3. Process the refund from there.

## Limitations

* **PayPal checkout is available for one-time payments only** — PayPal is not available for subscription orders. If a customer's cart contains a subscription, PayPal will not appear as a payment option.
* **Automatic capture** — Payments are captured immediately at checkout (no manual capture option).
* **Currency availability** — PayPal may not appear for certain localized currencies that PayPal doesn't support.
* **Refunds** — Must be processed through the Stripe Dashboard, not the OMS admin.

## FAQ

**Q: Will PayPal appear automatically at checkout?**

Yes. Once enabled, PayPal appears as a payment option on the Stripe checkout page alongside credit cards. No changes to your storefront are needed.

**Q: What if my customer's cart has a subscription?**

PayPal will not appear as a payment option. The customer can still pay with a credit card.

**Q: Do I need my own PayPal account?**

Not necessarily. You can use Chord's managed PayPal account, where payments go through Chord and are settled to you. Alternatively, you can set up your own PayPal account and Custom Payment Method token for direct payments.

**Q: How do I know if an order was paid with PayPal?**

PayPal orders are tagged with the channel name (default: "PayPal") and any custom tag you've configured. The payment record also shows "PayPal" as the payment type.

**Q: Can I use PayPal with multiple stores?**

Yes. Each store can independently enable PayPal with its own token and settings.

**Q: What happens if PayPal is down?**

Customers can still pay with credit cards. PayPal simply won't appear as an option if the service is unavailable.


---

# 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.chord.co/chord-oms/chord-oms-overview/checkout/stripe-paypal-checkout.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.