Billing and payments on Sentin8 — merchants, checkout, recurring billing, a double-entry money engine, webhooks, fraud screening, and reporting as one commerce vertical.
Every service this vertical ships, each owning its own data and API surface.
The charge lifecycle: from a payment intent through authorization, capture, and settlement to refund and dispute — routed through selectable payment rails.
Recurring revenue: product/price catalog, subscriptions with proration, invoices generated per billing cycle, metered usage records, coupons and credits.
The money engine: every money position and movement in the bill8 vertical — the single authority that mutates balances; others post through it.
The outbound integration surface: consumes domain events from Bus, materializes typed events, and delivers signed payloads to merchant-configured endpoints with retries.
Fraud prevention: declarative rules and velocity checks screening charges before money moves, sanctions screening, and a review queue for adjudication.
The reporting surface: report types defining a query shape, report runs that execute them, and scheduled reports delivering output files via Storage.
User- and staff-facing applications, thin by design — tokens never reach the client.
The operator-facing dashboard: payments, billing, connected accounts, and reporting in one merchant surface.
Explore →The payer-facing checkout app: payment method capture and charge confirmation for a single merchant transaction.
Explore →The payer self-service portal: invoices, subscription management, payment methods, and history.
Explore →The staff administration surface (RFW-rendered in Dash): merchant onboarding, risk review queues, webhook monitoring.
Explore →Typed facades over every service API — the only supported integration surface.
Bill8 inherits the Sentin8 security model and adds commerce guarantees — one money authority, screened charges, and signed webhook delivery.
Bill8:Ledger is the single authority that mutates balances; every other service moves money by asking it to post — nothing shadow-writes.
Risk screens every charge through declarative rules and velocity checks before the payment path — fraud prevention is a gate, not a report.
Every outbound webhook is signed, persisted, and delivered with retries — merchants never miss an event silently.
Billing owns the product/price catalog, subscriptions with proration, per-cycle invoices, and metered usage — upgrades never lose a cent.
The charge lifecycle (intent → authorize → capture → settle → refund → dispute) rides Bank8:Payment rails — bill8 never re-implements a rail.
Bill8 contains no platform infrastructure of its own — identity, events, storage, scheduling, and money movement are delegated.