End-to-end transaction flow
This deterministic sequence applies across every channel — hosted checkout, payment links, mobile companion verification, or direct Merchant REST API calls.Core architectural pillars
Brands
Isolated merchant workspaces — each brand has its own settlement rails, custom domain, staff roles, API keys, and ledger accounts.
Payment Flow
Deterministic transaction state machine from intent creation through authorization, escrow settlement, or reversal.
Direct Financial Rails
Native Pycer rails for mobile money prompts, C2B/B2C/B2B transfers, card acquiring, and real-time bank settlement.
Double-Entry Ledger
Statutory-grade bookkeeping that records every payment, fee split, and payout as balanced debit-credit pairs per brand.
Extension Engine
Modular runtime supporting custom payment adapters, checkout themes, operational addons, and enterprise ERP connectors.
White-Label Domains
Custom checkout domains per brand (
pay.yourbrand.com) with automated DNS TXT verification and TLS provisioning.Why enterprises run on Pycer
- Primary Direct Switch — Pycer operates its own switching core, eliminating intermediary hops and delivering sub-second authorization latencies.
- Cryptographic Data Protection — Customer PII and rail credentials are encrypted at rest using AES-256-GCM. Passwords use Argon2id, and every webhook is signed with HMAC-SHA256.
- Strict Tenant Isolation — Every transaction, customer record, API credential, and ledger journal is strictly scoped by
merchant_id. - Precision Monetary Math — All currency calculations, fee rules, and foreign-exchange conversions execute via arbitrary-precision
bcmatharithmetic with zero floating-point drift. - Unified Developer Portal — Single sign-on with your Pycer account gives instant access to API key rotation, live request logs, DLQ webhook replay, and sandbox simulators.