PayPal

Integration

PayPal

Trusted by millions of merchants worldwide.

What it does

Product surfaces

Where PayPal fits in the buying workflow

Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before PayPal receives checkout, payment, tax, or workflow context.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.
The Numi checkout elements palette showing content, interactive, and selling blocks.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

PayPal should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

The Numi Stripe payment methods settings page showing card, wallet, bank transfer, and buy now pay later options.

Builder paths

Stack guides that use PayPal

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

Overview

Add PayPal alongside Stripe (or as your sole processor). Setup is a short form — paste your PayPal Client ID + Secret from your PayPal developer dashboard, and we’ll wire up checkout buttons across every offer.

Automation graph

Connecting PayPal

How PayPal participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from PayPal

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

paypal.payment_succeeded
Fires when PayPal confirms a successful charge.
paypal.payment_failed
Fires when a charge is declined or fails.
paypal.subscription_canceled
Fires when a customer cancels a recurring subscription.

Actions on PayPal

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

paypal.refund
Refund a PayPal charge in full or in part.
paypal.cancel_subscription
Cancel a recurring subscription on PayPal.
Example sequence
trigger: paypal.payment_succeeded
actions:
  - plandalf.grant_entitlement: ${product_slug}
  - email.send_receipt:
      to: ${customer.email}
  - notify_team:
      channel: "#sales"

Integration methods

How PayPal connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use PayPal with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.

  1. Method 1

    Connect your account

    Plandalf links to PayPal via OAuth — pick the PayPal account to use, accept the scopes, and you'll be bounced back. Plandalf never sees your secret key, and every offer in your org can charge through that account without per-offer wiring.

    Plandalf → Settings → Integrations → PayPal → Connect
      ↳ Redirects to https://www.paypal.com
      ↳ Authorize Plandalf
      ↳ Redirected back, account live
Official PayPal docs and sign-up: www.paypal.com

FAQ

Common questions about the PayPal integration

Do I need a paid plan to use PayPal with Plandalf?

PayPal has its own account requirements — Plandalf doesn't add any. Any PayPal plan that supports OAuth + the Charges/Subscriptions API will work, which is every paid plan.

How long does setup take?

Under 10 minutes — paste a webhook URL into PayPal, point it at the Plandalf endpoint, and trigger a test event to confirm.

Can I disconnect PayPal later without losing data?

Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and PayPal's own records are untouched. You can reconnect any time and resume from the last seen event.

Does Plandalf store PayPal data?

Plandalf stores the PayPal customer ID, the charge IDs, and the metadata needed to reconcile orders. Card numbers never touch Plandalf — they go straight from the customer to PayPal.

What if my payment need isn't covered by the actions or triggers listed here?

Drop into the Plandalf REST API and call PayPal directly from your sequence's HTTP action. Anything PayPal's public surface exposes is reachable.

Is there a usage limit?

Plandalf doesn't rate-limit PayPal calls beyond what PayPal itself enforces. Your PayPal plan's API rate limit is the practical ceiling.

Where do I find PayPal's own documentation?

PayPal's homepage at https://www.paypal.com links to their developer docs. For Plandalf-side questions about the PayPal integration, see the Plandalf docs.

Feature detail