Payment gateways

OFEngine supports several payment processors. You can enable more than one, and each is configured in the admin panel under Payment gateways. No code changes or .env edits are needed.

Choosing a processor

Pick a processor whose rules allow the kind of content on your platform. Your processor’s acceptable-use policy matters more than anything else here: a mainstream processor will close your account if your platform’s content breaks its rules.

Processor	Best for	Notes
Stripe	Mainstream platforms: coaching, fitness, music, education	Fast approval. Strict content rules.
PayPal	Mainstream platforms; fans who prefer PayPal	Has a sandbox mode for testing.
CCBill	Categories mainstream processors don’t accept	FlexForm (hosted payment page) on all plans; RESTful API (cards entered on your site) on Pro and above.
NetBilling	Categories mainstream processors don’t accept	Cards entered on your site and saved for one-click and recurring payments.
Crypto (NowPayments, Coinbase Commerce)	Regions where cards are hard to accept	Bitcoin, Ethereum, USDT, USDC and more.

On Pro and Business, different creators can use different processors on the same platform (per-creator gateway routing).

Setting up a gateway

1. Create a merchant account with the processor and get your API credentials.
2. In the admin panel, open Payment gateways and choose the processor.
3. Paste your credentials. Use test or sandbox mode first where the processor offers it.
4. Copy the webhook URL shown for that gateway into your processor’s dashboard. Webhooks are how the processor tells OFEngine a payment succeeded, renewed, failed or was refunded.
5. Enable the gateway, and set it as the default if you want it pre-selected at checkout.
6. Make a small test payment, then switch to live mode.

Only one card gateway at a time

If you enable two card processors (for example CCBill and NetBilling), fans see two “Add card” options at checkout. Keep one card processor enabled, plus PayPal or crypto alongside it if you like.

Recurring billing

Subscriptions renew automatically through the cron job. For processors with saved cards (CCBill RESTful, NetBilling), OFEngine charges the saved card when a subscription comes due. If a renewal is declined, the fan gets a short grace period; a second decline cancels the subscription.

Recurring billing depends on the cron job. If renewals aren’t happening, check the cron job first.