What the PayPal API gives you
PayPal's API covers three quite different jobs, which often get mixed up:
- Payouts Sending money to sellers, affiliates or contractors with PayPal accounts. See PayPal Payouts integration.
- Subscriptions Recurring billing for customers who'd rather pay through PayPal.
- Custom checkout PayPal and Pay Later in a bespoke platform through the Orders API. See PayPal checkout in WooCommerce.
For more detail, read the PayPal API integration guide.
Who it's for
- Marketplaces Seller payments sent to each seller's PayPal account at the end of each settlement period, with no manual payments or CSV uploads.
- Affiliate and commission schemes Commission worked out from your tracking and paid on your schedule, weekly, monthly or on demand.
- Subscription businesses Plans, billing agreements and cancellations handled, with access to your platform granted or removed by PayPal billing status.
- Custom platforms Booking systems, marketplaces and membership sites with no PayPal plugin, often with PayPal and Stripe side by side. See PayPal vs Stripe and the best payment APIs for UK shops.
- Shops that want Pay Later PayPal's Pay in 3 offered as its own option, with instalment messages on product pages.
What's included
- Webhooks for every payment event, with signatures checked
- Failed payouts caught, logged and flagged
- Real-world testing with small amounts before full use
- A handover document, and the code is yours
Not included: your PayPal business account, the Payouts approval itself (I'll guide you through it), PayPal's fees, a standard WooCommerce PayPal checkout (use the plugin), and full marketplace onboarding through PayPal Commerce Platform, which is quoted separately.
Payment is 50% to start and the balance on completion. For what drives the price, read what a PayPal integration costs.
How it's built
- Server-to-server, never in the browser Your PayPal credentials stay on the server. The integration signs in to PayPal itself and makes every call from there.
- Orders created and captured properly For checkout, an order is created on the server with the amount from your own system, the customer approves it in PayPal, and the payment is only captured and marked as paid once PayPal confirms it.
- Payouts tracked item by item A payout batch can succeed while individual payments inside it don't. Some will be unclaimed, because the recipient's email has no PayPal account yet, and PayPal returns unclaimed money if it isn't claimed within 30 days. Others are held or fail. Each payment is tracked on its own status, and only a payment PayPal confirms as succeeded is ever marked as paid in your system.
- Webhooks verified with PayPal Every incoming event is verified with PayPal before it's trusted, and repeat deliveries are recognised and ignored.
- Tested in the sandbox, then with small real amounts Sandbox testing catches the logic. A handful of small live payments confirms the account settings before full use.
Built from experience
I built the PayPal Payouts pipeline for ReGraded, my trade-in platform, which pays customers for the devices they send in. Getting the statuses right mattered: an early version treated an unclaimed payout as paid, which would have told customers they'd been paid when the money hadn't reached them. It was caught in testing and fixed so that only a confirmed, succeeded payment can mark a trade as paid. That's the level of care money movement needs.
How to get a price
Send a short written spec by WhatsApp, text, email or the form: whether you need payouts, subscriptions or a checkout, and what platform it connects to. I'll reply within 24 hours with a quote.