Skip to main content
A gateway in OwnPay is a plugin that knows how to talk to a specific payment provider - it sends the customer’s payment details, receives the authorization result, and handles callbacks and refunds. OwnPay ships with 123+ gateway plugins covering international card processors, regional mobile wallets, and bank-level integrations.

​
Gateway types

Online gatewaysReal-time payment processing. The customer enters payment details on the checkout page, and the gateway authorizes the transaction instantly.Examples: Stripe, PayPal, bKash, Nagad, Razorpay, SSLCommerz, Square.
Manual gatewaysOffline payment methods that require manual confirmation. The customer is shown instructions (bank account number, QR code), and a staff member marks the payment as complete after verifying the transfer.Examples: bank transfer, cash on delivery, manual invoice.

​
How gateway routing works

When a customer reaches the checkout page, OwnPay looks at the brand’s active gateways and presents them as payment options. The routing logic is straightforward:
  1. Load all gateways marked active for the brand.
  2. Filter by the payment’s currency (each gateway declares its supported currencies via supportedCurrencies()).
  3. Present the matching gateways on the checkout page.
  4. The customer selects one and submits payment.
OwnPay does not currently perform automatic gateway failover or load balancing. The customer chooses the gateway. If you want redundancy, activate multiple gateways so the customer has alternatives.

​
Credential encryption

Gateway API keys, secrets, and merchant IDs are never stored in plaintext. When you save gateway credentials, OwnPay encrypts them using AES-256-GCM with a key derived from your application’s APP_KEY. The encrypted blob is stored in the database; only the running application can decrypt it.
If you lose your APP_KEY, all encrypted gateway credentials become unrecoverable. Back up your .env file and store APP_KEY in a secure secrets manager.

​
Per-brand gateway assignment

Each brand independently selects which gateways to activate. Brand A might use Stripe and PayPal, while Brand B uses bKash and SSLCommerz. Credentials, fees, and enabled/disabled state are all scoped to the brand’s merchant_id.

​
Gateway health checks

OwnPay periodically pings active gateways to verify they are reachable. If a gateway consistently fails health checks, it is flagged in the admin dashboard so you can investigate. Check gateway status under Gateways in the sidebar.
This table shows a subset. OwnPay supports 123+ gateways. See the full list in the admin panel under Gateways or visit GitHub.
Last modified on August 25, 2026

Related topics

Quickstart - Accept Your First Payment in 5 MinutesConfigure payment gatewaysHow OwnPay WorksLaravel SDK - Fluent Payment Integration for PHP AppsPlugin System - Extensible Architecture