Offer configuration stays visible
Use Offers to decide what PayPal receives: product, price, buyer, checkout mode, invoice, and automation context.

Product surfaces
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.
Use Offers to decide what PayPal receives: product, price, buyer, checkout mode, invoice, and automation context.
Before PayPal enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
PayPal should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
PayPal handles the charge while Plandalf keeps checkout, payment state, invoice, tax, and follow-up context together.
Builder paths
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
Find full stack guides that pair PayPal with checkout, payment, automation, fulfilment, records, and downstream integrations.
Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.
Use hosted checkout when PayPal should hand the buyer to a branded Plandalf checkout page.
Use SDK checkout when PayPal belongs inside an app, custom site, or API-first stack.
Route checkout events, purchase events, payment state, invoices, and customer context into another tool.
Turn a completed checkout into access, receipts, CRM updates, support context, and records.
Compare how PayPal fits beside Plandalf Offers, checkout, payment state, invoices, automation, and integrations.
Compare how PayPal fits beside Plandalf Offers, checkout, payment state, invoices, automation, and integrations.
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
How PayPal participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
paypal.payment_succeededpaypal.payment_failedpaypal.subscription_canceledThings Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
trigger: paypal.payment_succeeded
actions:
- plandalf.grant_entitlement: ${product_slug}
- email.send_receipt:
to: ${customer.email}
- notify_team:
channel: "#sales"Pair it with
Platforms whose roles complement PayPal inside a Plandalf sequence.
PayPal + HubSpot
Sync paying customers into HubSpot the second checkout completes.
PayPal + Kajabi
Sell a course through Plandalf, drop the student into Kajabi.
PayPal + ActiveCampaign
Sync paying customers into ActiveCampaign the second checkout completes.
PayPal + beehiiv
Sync paying customers into beehiiv the second checkout completes.
PayPal + Kit (ConvertKit)
Sync paying customers into Kit (ConvertKit) the second checkout completes.
PayPal + Customer.io
Sync paying customers into Customer.io the second checkout completes.
Integration methods
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.
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 liveFAQ
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.
Under 10 minutes — paste a webhook URL into PayPal, point it at the Plandalf endpoint, and trigger a test event to confirm.
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.
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.
Drop into the Plandalf REST API and call PayPal directly from your sequence's HTTP action. Anything PayPal's public surface exposes is reachable.
Plandalf doesn't rate-limit PayPal calls beyond what PayPal itself enforces. Your PayPal plan's API rate limit is the practical ceiling.
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.