01
API-created payments
Create payments from your backend with a server-to-server API. API keys belong on your servers — not in browsers or mobile clients.
Capabilities
Operational infrastructure surface
Kobbopay is API-first B2B crypto payment infrastructure with signed webhooks, explicit payment lifecycles, and a merchant portal for operations — after merchant approval, on selected rails where enabled.
02
Explicit lifecycles
Payments move through defined lifecycle states so engineering, finance, and support can agree on what each status means for your workflows.
03
Signed webhooks
Subscribe to lifecycle events with signed deliveries so your systems can verify authenticity before updating internal state.
04
Merchant portal
Operate day-to-day: review payments, manage keys and webhook configuration, and follow operational signals appropriate to your deployment.
05
Balances and reconciliation
Balances are understood through ledger-oriented accounting tied to confirmation semantics — not vague “wallet vibes.”
06
Withdrawal requests
Merchants initiate withdrawal requests. Execution is subject to operational controls and configuration — not a promise of universal instant on-chain payout.