API keys are scoped and revocable
Merchant API keys are issued per merchant and environment, shown once at creation, and can be rotated or revoked. Keys are not shared across merchants and are not returned by list endpoints after creation.
Security
Sobtra coordinates payments rather than holding funds, which defines where the security boundary sits: we protect billing state, credentials and access control, and the provider protects the payment instrument.
Merchant API keys are issued per merchant and environment, shown once at creation, and can be rotated or revoked. Keys are not shared across merchants and are not returned by list endpoints after creation.
Roles resolve to a permission set that the API checks on every request. Dashboard controls hide what a role cannot do, but the enforcement point is the server, not the interface.
Merchant records carry an environment, and queries are scoped by it. A test key cannot read or write live subscriptions, customers, invoices or payments.
Webhook endpoints hold a signing secret that can be rotated. Deliveries are recorded with their attempt history so a missed event can be traced rather than guessed at.
Sobtra does not store full card numbers or security codes. Collection happens at the provider, and Sobtra records the provider reference, status and amount against the payment.
Sobtra is not a payment processor and does not hold or settle money. Funds move between the payer and the merchant through the merchant's own provider account.
Data handling
Stored
Customer names and email addresses, subscription and invoice records, usage events with external identifiers, tax rates, provider references and webhook delivery history.
Not stored
Full card numbers, card security codes, bank credentials and provider API secrets beyond what is required to call the provider on your behalf.
Retention
Billing records are retained while the merchant account is active, and exported on request during beta. Usage events are retained per the configuration agreed with each merchant.
Current posture
To report a vulnerability, use the contact page and include reproduction steps. Please do not test against other merchants' data.
For reviewers
On the API for every merchant-scoped request, and in the dashboard session layer. Client-side checks are presentation only.
No. Every query is scoped to the authenticated merchant, and the environment is part of that scope.
Provider secrets are stored server-side and used only to call the provider's API. They are never returned to a browser.
The delivery attempt and its result are recorded, and the endpoint remains available for retry. A failed webhook does not silently change billing state.
We can walk your team through the permission model, key handling and data boundaries directly.