About

What Kobbopay is

Kobbopay is API-first crypto payment infrastructure for B2B merchants. The product centers on server-created payables, explicit lifecycle semantics, signed webhooks, and reconciliation-oriented operations—not consumer checkout gimmicks.

Access is reviewed. Rails and environments are configured per merchant. Production enablement follows operational procedures, not marketing timelines.

Operational reliability

Reliability means predictable lifecycle behavior, verifiable event delivery, and language finance can audit. It does not mean pretending blockchains remove policy, exceptions, or treasury controls.

Settlement clarity

We document the difference between observing funds on a rail and recognizing economic outcome in merchant books. Settlement clarity is shared vocabulary across engineering, support, and finance—not a single green status in a UI.

Controlled merchant onboarding

Merchants proceed through approval gating, rail enablement, and bounded integration review before production traffic. Onboarding expectations are described in guides and intake flows—not implied by public feature lists alone.

Webhook verification

Signed webhooks and server-side secrets are part of the trust boundary. Integrations are expected to verify raw payloads, implement idempotency, and map events to explicit lifecycle states.

Reconciliation discipline

Infrastructure supplies stable identifiers and machine-readable statuses; merchants supply mapping to orders, entitlements, and ledger rules. Kobbopay editorial and documentation reinforce that separation consistently.

Treasury visibility

Treasury teams need attribution, rail context, and exception paths—not explorer screenshots in chat. Journal and product language emphasize ledger-oriented views and audit-friendly transitions where configuration allows.