Integrations · Payment Gateways
Gateways move the money.
A payment gateway connects Blesta to your payment processor. 36 ship first-party — cards, ACH, and crypto — and the merchant ones charge cards on file without anyone clicking Pay.
Two kinds
Merchant, non-merchant — run both.
01 · Merchant
Your processor, cards on file
Stripe, Authorize.net, Braintree and friends. Cards and bank accounts are tokenized and stored, and Blesta charges them automatically when invoices come due. This is where hands-off billing lives.
02 · Non-merchant
A hosted checkout
PayPal, crypto processors, and regional favorites. The customer clicks Pay and approves on the processor's site; the callback marks the invoice paid. The customer initiates — so there's no automatic charging.
03 · In practice
Most hosts run both
One merchant gateway for auto debit, plus PayPal or crypto as checkout options. Blesta runs any number side by side — per company, per currency, your rules.
Worked example — Stripe Preferred
Cards on file, charged on time.
Stripe is preferred for a reason: tokenized cards and ACH that renew services without anyone touching anything. Card data lives at Stripe — your server never sees a number.
Selling where card rails are thin? Regional gateways ship first-party — iDEAL in the Netherlands, Razorpay in India, Paystack in Africa, PagSeguro in Brazil — and BTCPay Server gives you self-hosted crypto with no middleman at all. Browse all 36
30-day free trial · No credit card · Your server
Get paid while you sleep.
The installer starts your 30-day free trial automatically — connect a gateway and let the next renewal charge itself.
Installing manually instead? Choose "Start a 30-day free trial" when prompted for a license key.