Embed multi-merchant crypto checkout in your product.
If you onboard sellers, merchants, or sub-accounts, you need Gateway — not a single-merchant invoicing tool. Settlematic Gateway provides checkout sessions, signed webhooks, and merchant lifecycle APIs built for platforms.
Overview
Onboard merchants via API, issue checkout sessions, and receive signed webhooks when payments land — with sandbox merchants for integration testing.
Merchants
Multi
Onboard via API
Checkout
4 modes
Hosted, embed, redirect, API
Events
Webhooks
Signed HMAC deliveries
Definition
What is Platforms?
Settlematic Gateway is a crypto payment processing module for platforms — multi-merchant onboarding, hosted and embedded checkout, refunds, and webhook-driven automation.
Merchants
Onboard sellers without manual ops
Create merchants programmatically, configure fee splits, and issue checkout sessions from your backend. Sandbox merchants let engineering test end-to-end before production.
- REST API for merchant lifecycle
- Hosted and iframe checkout
- Customer records and refunds
- Org-level transaction views
Developers
Webhooks your backend can trust
Subscribe to payment events with HMAC signature verification. Delivery logs and retries mean finance and engineering debug from the same event stream.
- OpenAPI-documented endpoints
- Testnet and mainnet environments
- Scoped API keys
- Rate limit dashboards
Compliance
Merchant lifecycle your ops team controls
KYB workflows, per-merchant rate limits, refund tooling, and org-level transaction views give platforms visibility without becoming a custodian of merchant funds.
- Merchant KYB submission flows
- Refund and dispute tooling
- Subscription plans for SaaS marketplaces
- Org-wide analytics across merchants
Workflow
How platforms teams use Settlematic
- 1
Onboard
Create merchant via API or dashboard
- 2
Session
Issue checkout session from your backend
- 3
Pay
Customer completes hosted or embedded checkout
- 4
Webhook
Backend receives signed payment.confirmed event
- 5
Settle
Treasury sweeps to merchant-configured wallets
Problems we solve
Teams in platforms often hit the same operational walls before adopting unified crypto finance infrastructure.
Single-merchant invoicing tools
Collect-style products cannot onboard sellers or route settlements per merchant.
Unreliable webhooks
Payment processors without signed events and delivery logs make finance and engineering debug different realities.
Long integration cycles
Without sandbox merchants, platforms ship checkout integrations blind to production edge cases.
Recommended modules
Start with the modules most teams in platforms deploy first.
Collect is for one business billing its clients. Gateway is when you onboard multiple merchants or sellers on your platform.
Related industries
Start with Platforms
Create a free testnet account or open a sandbox demo with sample data.