Accept payments through PayPal — the world’s most-recognised checkout brand, 200+ countries, 25+ currencies — directly from your Acelle Mail install. Ships as TWO payment gateways: one-off and recurring. Customers without a PayPal account can still pay with debit/credit card on the one-off flow. No webhook setup, no IPN configuration, no merchant gateway approval. Drop-in plugin for Acelle Mail. Paste Client ID + Secret, save, sell.
PayPal is the single payment method customers know without explanation:
Pair PayPal with Acelle Mail and you get a globally-credible checkout option alongside your existing Stripe / Offline / regional gateways.
Adds two payment gateways to Acelle’s admin under one plugin:
Both share the same form (Client ID + Secret + Environment) and use the same PayPal REST app. Enable one or both depending on what your customers need — they show up as two entries in the gateway picker, register independently, and are managed independently. Registers without modifying Acelle core code. Requires Acelle 4.0.24+ and PHP 8.1+.

Acelle’s billing layer distinguishes between Direct Payment (Acelle owns the subscription record) and Remote Subscription (vendor owns the subscription record). PayPal does both, but through different APIs. This plugin gives you BOTH as separate, independently-configurable gateway entries:
POST /v2/checkout/orders. Customer approves, return handler calls /orders/{id}/capture inline. One transaction per customer click. Best for: one-time plan purchases, top-ups, pay-as-you-go credits.POST /v1/billing/subscriptions against a pre-mapped PayPal Billing Plan. Customer approves once; PayPal handles every renewal forever after. Best for: SaaS plans with monthly / annual auto-renewal.The admin chooses which to enable. Some operators ship both (one-off for ad-hoc credits, subscription for the actual plans); some ship only one. Both use the same PayPal REST app credentials — there is no separate “subscription credential” at PayPal.
On the one-off PayPal gateway, PayPal’s hosted checkout exposes a “Pay with Debit or Credit Card” option below the standard “Log in to PayPal” option. The customer can pay with a card directly without signing up for PayPal — meaning you don’t lose customers who associate PayPal with mandatory account creation.
This is automatic on PayPal’s side; no extra integration work. Acelle just sees a successful capture.
Unlike most payment integrations that require you to expose /webhooks/paypal and verify IPN / signatures, this plugin does not need any inbound URL:
?token=… back, Acelle captures, done.RemoteSubscriptionSyncService polling GET /v1/billing/subscriptions/{id} hourly through Acelle’s existing scheduler.Net result for the admin: no webhook_id to copy into PayPal’s developer dashboard, no IPN URL to configure, no event subscriptions to maintain, no HMAC secret rotation. Drop the plugin in, save Client ID + Secret, done.
PayPal has multiple integration generations. This plugin only uses the latest REST APIs:
POST /v1/oauth2/token against Client ID + Secret) — no legacy API username / password / signature triple.If you’ve used older PayPal integrations and dread “IPN handler” or “Express Checkout signature”: those are not part of this plugin. Modern PayPal REST is straightforward; this plugin just wraps it cleanly for Acelle.
PayPal handles the country / currency / local-payment-method matrix for you. Configure your Acelle gateway in USD and your German customer can still pay in EUR through PayPal — currency conversion happens at PayPal’s side at their published rate. Brazilian customer can pay with their local Boleto if their PayPal account supports it. Japanese customer sees JCB / domestic options. No extra integration work required.
Supported currencies include USD, EUR, GBP, JPY, AUD, CAD, CHF, NZD, SGD, HKD, SEK, DKK, PLN, CZK, HUF, BRL, MXN, TWD, THB, PHP, MYR, ILS, NOK and more.
PayPal’s Sandbox is bundled with every developer account at developer.paypal.com — completely isolated from Live (separate API hosts, separate balances, separate accounts). Test buyer accounts come pre-funded with play money. You can develop, demo, and QA against Sandbox without ever touching real funds — the plugin’s Environment dropdown switches API hosts cleanly. Flip to Live only when you’re ready.
GET /v1/billing/plansresumeRemoteSubscription exposed for admin un-cancel flow before the period ends.php files, no ionCube, no encoder. Audit and customise freely under the Envato licenseacelle-paypal-v1.0.x.zip — ready to installServiceProvider (registers BOTH gateways), PayPalGateway (one-off, Orders v2), PayPalSubscriptionGateway (recurring, Subscriptions v1), PayPalApi HTTP client, 2 controller pairs (Checkout + Return)PayPalGateway and PayPalApi (PHPUnit / Pest compatible)api-m.paypal.com (live) and api-m.sandbox.paypal.com (sandbox) on port 443. No inbound public endpoint needed for sync.payment_gateways table — no new migrations in v1Do I need to set up a webhook URL in PayPal’s developer dashboard? No. This plugin uses pull-based sync. There is nothing to register in PayPal’s webhook settings page. You can still register webhooks for your own analytics if you want — they won’t conflict with this plugin.
Does it support one-off charges or only subscriptions? Both, as TWO separate gateways. The plugin registers paypal (one-off, Direct Payment) and paypal-subscription (recurring, Remote Subscription). You can enable just one or both — pick from the gateway picker and configure each independently.
Do my customers need a PayPal account? For one-off (PayPal gateway): NO — PayPal’s hosted checkout exposes a guest card-payment option right next to the “Log in to PayPal” button. Buyers can pay with debit/credit card without signing up. For recurring (PayPal Subscription gateway): YES — recurring billing requires a stored billing agreement at PayPal, which means the customer must have (or create) a PayPal account at approve time.
My PayPal account uses the older API (Username / Password / Signature). Does this work? That’s PayPal’s legacy Classic API (Payflow / Express Checkout). This plugin only uses the modern REST API (Client ID / Secret / OAuth 2.0), which is what new PayPal Business accounts get by default. If you only have Classic creds, create a REST app at developer.paypal.com → Apps & Credentials → Create App (free) and use those Client ID / Secret. The two coexist on the same PayPal account.
Can the same PayPal REST app feed both gateways? Yes. The same Client ID + Secret works for both Orders v2 (one-off) and Subscriptions v1 (recurring). You typically paste the same credentials into both gateway rows in Acelle — there is no separate “subscription credential” at PayPal.
Will it work alongside Stripe / Offline / Paddle in the same Acelle install? Yes. Acelle supports multiple active gateways concurrently — customers see all enabled options at checkout and pick one. This plugin only registers paypal and paypal-subscription as new options; existing gateways are unaffected.
Can I run a sandbox gateway and a live gateway side by side? Yes. Each payment_gateways row stores its own Client ID / Secret / environment. Add as many rows as you need — Sandbox + Live for one-off, Sandbox + Live for subscription = up to 4 distinct PayPal rows, all independent.
Does it support PayPal Credit / Pay Later? Yes — these are PayPal-side features automatically exposed at checkout in supported markets when buyer eligibility allows. No extra configuration needed; the plugin just hands off to PayPal’s hosted approve flow which renders these options when applicable.
Is the source open / unobfuscated? Yes. All PHP source is delivered as plain .php files — no ionCube, no obfuscator. You can audit, fork, and customize it under the Envato license terms.
v1.0.0 — Current
(Future releases will be appended here. CodeCanyon emails buyers when a new version is uploaded.)
Reasonable scope: install help, configuration help, plan-mapping help, bug reports against an unmodified install. Out of scope: PayPal account / payout / merchant-account / Business verification issues (those go to PayPal merchant support), Classic API migration, custom development against the plugin source, Acelle core modifications.
Envato Regular License — use in a single end-product (one Acelle install / one Acelle SaaS instance). For SaaS providers reselling Acelle to multiple end customers under their own brand, the Extended License applies. Full terms: https://codecanyon.net/licenses/standard
0 average based on 0 ratings.
| Last Update | 2026-05-17 |
| Created | 2026-05-17 |
| Sales | 1 |
| Discussion | Comments |
| Compatible Browsers | |
| Software Version | PHP 8.x |
| High Resolution | |
| Software Framework | |
| Files Included | JavaScript JS HTML PHP |
| Video Preview Resolution |