Providers
Bring the provider you already settle with.
Sobtra is not a processor. The billing layer records what should be charged and coordinates the request; your provider collects and settles. That separation means changing gateway does not mean rebuilding subscriptions.
Modelled gateways
Thirteen gateways in the billing layer.
A gateway being modelled means Sobtra can be configured to call it. It does not mean a partnership, and it does not override the provider's own country coverage or your account's approval.
Read this before integrating. Several of these gateways have overlapping but non-identical country coverage and settlement behaviour. Sobtra does not guarantee that a provider will approve your account, support your business category, or settle in the currency you price in. Confirm those with the provider.
How a connection works
Four steps, no fund custody.
Connecting a gateway is configuration in the dashboard, not a code change in your product.
1. Add the gateway to your merchant account
Choose the provider and the environment. Test and live credentials are stored separately, so a test connection cannot charge a live customer.
2. Store credentials server-side
Provider secrets are used only by Sobtra to call the provider. They are never returned to a browser or included in API responses.
3. Let the billing layer charge
When an invoice is due, the configured gateway is called with the amount, currency and customer reference. The result is recorded against the payment.
4. Reconcile from webhooks
Provider callbacks update payment status. A callback that arrives twice is handled once; a payment can also be verified directly against the provider.
By market
Coverage starts with the country.
Each market page lists the currencies and methods the platform models, plus what your provider account needs to support.
Not sure whether your provider covers a market?
Tell us the provider, the country and the method you want to collect with. We will confirm before you build against it.