Payment providers
Payment is configured in two data fields plus encrypted credentials — no code, no rebuild. You choose which methods appear at checkout and which gateway backs them; the gateway itself is a shared, versioned package.
What’s available
Section titled “What’s available”| Method / gateway | What it is |
|---|---|
cod |
Cash on delivery — a built-in method, no gateway credentials needed. Pair it with COD & fraud review. |
sslcommerz |
SSLCommerz online gateway (the shipped adapter). |
More gateways are added by version bump, for everyone. The checkout call site is provider-agnostic — switching the gateway changes only which adapter runs.
The settings
Section titled “The settings”Set in the deep-ops console under Core → Tenant configs.
| Setting | Purpose | Default | Where |
|---|---|---|---|
payment_methods |
The methods offered at checkout, e.g. ["cod","sslcommerz"] |
["cod"] (serializer fallback) |
Tenant config → Commerce |
payment_provider |
The gateway package to use for online payments | blank → the first gateway with credentials | Tenant config → Providers |
| gateway credentials | API keys / secrets for the gateway | — | Integrations (encrypted) |
Wiring an online gateway
Section titled “Wiring an online gateway”- Add the gateway to
payment_methods(e.g. include"sslcommerz"). - Add the gateway’s credentials as an App integration — encrypted at rest automatically.
- Set
payment_providerto the gateway’s name (or leave blank to use the first gateway that has credentials).
Related: Courier providers · SMS provider · Upgrading a provider package.