A full customer, organization, merchant, developer, and operations experience.
The customer platform brings account management, organization management, onboarding workflows, dashboards, notifications, support, and governed provider visibility into one repository-backed demo-safe experience.
Customer platform pages use repository-backed demo-safe metadata, provider status visibility, and execution-gated messaging only. They do not expose credentials, production secrets, customer PII, merchant PII, or live financial execution controls.
A repository-backed operating view without production execution.
Verification progress
62%
Profile, contact, compliance, and account verification progress are loaded from customer repository metadata.
Provider status
6 providers
Provider readiness is represented from stored customer provider-status metadata with execution disabled.
Open tasks
7
Business verification, compliance review, provider selection, and support contact setup remain pending.
Notifications
4
Notification preferences and dashboard counts are persisted through the customer repository abstraction.
Organization summary
verification_pending
Customer lifecycle, profile, preferences, support, activity, and verification state now come from repository-backed records.
Merchant summary
onboarding_started
Merchant onboarding, KYB intake, provider selection, settlement preferences, verification, and approval state are repository-backed.
Business summary
verification_pending
Business profile, registration information, contacts, operational settings, compliance, provider enrollment, and dashboard state are repository-backed.
Developer summary
sandbox_requested
Developer profile, organization, applications, sandbox requests, API key request metadata, webhook metadata, SDK preferences, and usage summary are repository-backed.
Workflow state
in_progress
User registration, onboarding, KYB, verification, approval, provider, support, operations, task, and review workflow metadata is repository-backed.
Review queue
3
Review queue tasks are persisted as metadata and cannot trigger provider execution or financial movement.
Notification inbox
3
User, organization, merchant, business, developer, and operations notification inbox items are repository-backed and delivery execution remains disabled.
Announcements
2
Announcement center history is persisted as approved metadata without email, push, SMS, provider, or financial execution.
Operations queues
7
Merchant, business, developer, organization, KYB, provider onboarding, and approval queues are persisted behind the operations repository.
Operations tasks
5
Operational tasks, assignments, escalations, SLA metadata, review history, and activity timeline are metadata-only and cannot execute providers.
Support tickets
2
Support tickets, lifecycle state, priority, category, conversations, notes, attachment metadata, and resolution history are repository-backed.
Support conversations
2
Customer communications and internal notes are persisted as demo-safe metadata without sending messages or exposing PII.
Executive dashboard
88%
Executive dashboard intelligence aggregates identity, provider, workflow, notification, operations, support, and activity metrics from repository-backed services.
Dashboard KPIs
15
Dashboard KPIs cover active users, organizations, merchants, businesses, developers, workflows, notifications, support, reviews, provider readiness, platform health, and activity summaries.
Customer, merchant, business, developer, workflow, notification, operations, support, audit, and dashboard intelligence state is repository-backed.
Customer state is repository-backed.
Profile, contact, preferences, notification preferences, dashboard state, activity, provider status, verification progress, support posture, and lifecycle state now flow through the customer repository abstraction.
Customers
1
Profiles
1
Preferences
1
Notifications
1
Activities
4
Provider statuses
6
Verification
pending
Lifecycle
verification_pending
Merchant onboarding state is persisted as metadata.
Merchant profile, configuration, KYB progress, document metadata, provider selections, settlement preferences, verification, risk, approval, and lifecycle state use the merchant repository boundary.
Merchants
1
Configurations
1
KYB progress
pending
Documents
2
Provider selections
6
Settlement
manual_review
Risk
under_review
Approval
pending
Repository backed: true
Provider execution enabled: false
Financial execution enabled: false
Settlement execution enabled: false
Ledger posting enabled: false
Secrets stored: false
Business platform state is repository-backed.
Business profile, registration information, contacts, verification, operational settings, dashboard state, compliance, provider enrollment, preferences, and activity now flow through a business repository boundary.
Businesses
1
Contacts
2
Dashboard
1
Provider enrollments
2
Compliance
pending
Verification
pending
Lifecycle
verification_pending
Activity
2
Developer platform state is persisted as metadata.
Developer profile, organization, applications, sandbox requests, API application requests, API key request metadata, webhook metadata, SDK preferences, usage summary, verification, and lifecycle now use a developer repository boundary.
Developers
1
Applications
1
Sandbox requests
1
API key requests
1
Webhooks
1
SDK
typescript
Lifecycle
sandbox_requested
Activity
2
Repository backed: true
Provider execution enabled: false
Financial execution enabled: false
Settlement execution enabled: false
Ledger posting enabled: false
Production secrets stored: false
Workflow state is repository-backed.
Registration, onboarding, KYB, verification, approval, provider, support, operations, task, and review workflows now flow through a workflow repository boundary with timeline and history metadata.
Workflows
3
Current status
in_progress
Current step
KYB and provider readiness review
Timeline
3
History
1
Tasks
3
Approvals
2
Review queue
3
Inbox and announcements are persisted as metadata.
Notification inbox, announcements, preferences, email queue readiness, push readiness, SMS readiness, and notification history now use a notification repository boundary without delivery execution.
Inbox items
3
Announcements
2
Preferences
2
History
2
Email ready
2
Push ready
1
SMS ready
0
Unread
2
Repository backed: true
Provider execution enabled: false
Financial execution enabled: false
Notification delivery execution enabled: false
Settlement execution enabled: false
Ledger posting enabled: false
Production secrets stored: false
Operations queues are repository-backed.
Operations dashboard, merchant, business, developer, organization, KYB, provider onboarding, approval queues, tasks, assignments, escalations, SLA metadata, review history, and activity are persisted as metadata only.
Queues
7
Readiness
86%
Tasks
3
Assignments
3
Escalations
1
SLA records
2
Reviews
1
Timeline
2
Support tickets and conversations are repository-backed.
Support ticket lifecycle, status, priority, category, conversations, internal notes, attachment metadata, resolution history, communications, preferences, knowledge links, and timeline now use a support repository boundary.
Tickets
2
Open tickets
2
Conversations
2
Internal notes
1
Attachments
1
Resolution
1
Preferences
1
Knowledge
1
Repository backed: true
Provider execution enabled: false
Financial execution enabled: false
Support communication execution enabled: false
Settlement execution enabled: false
Ledger posting enabled: false
Production secrets stored: false
Audit events and timelines are repository-backed.
User, organization, merchant, business, developer, workflow, notification, operations, support, review, approval, security, and login activity now aggregate into one metadata-only audit timeline.
Audit events
13
Timeline items
16
User activity
1
Merchant activity
1
Workflow events
1
Operations events
1
Support events
1
Security events
1
Executive and operating dashboards share one metrics layer.
Executive, operations, merchant, business, developer, support, compliance, identity, provider, and workflow dashboards consume repository-backed metrics derived from existing platform persistence.
Dashboards
10
Metrics
15
Summaries
10
Executive score
88%
Operations
1
Provider
1
Workflow
1
Support
1
Repository backed: true
Provider execution enabled: false
Financial execution enabled: false
Settlement execution enabled: false
Ledger posting enabled: false
Production secrets stored: false
Role-aware entry points.
Each role keeps its own onboarding and portal path while sharing the same governance, support, privacy, and execution-gate posture.
Consumer
Personal access for future wallet, payment, transaction, support, and compliance experiences.
Merchant
Merchant access for payments, providers, KYB, transactions, settlements readiness, and support.
Business
Business access for organization profile, provider visibility, treasury readiness, transactions, and team coordination.
Developer
Developer access for API documentation, sandbox readiness, webhook planning, and key governance placeholders.
Financial Institution
Financial institution access for partnership readiness, provider governance, settlement controls, and compliance review.
Credit Union
Credit union access for partnership readiness, member-program planning, compliance status, and governed integration review.
Partner
Partner access for ecosystem readiness, integration planning, provider status, and governed collaboration.
Internal Operations
Internal operations access for support, readiness, incident, evidence, and governed operational visibility placeholders.
Administrator
Administrator access for governed console visibility, RBAC messaging, audit readiness, and execution gate status.
Inbox and announcement examples.
Your business verification remains pending while approval workflows complete.
Stripe and Paystack readiness remain visible, but execution stays approval-gated.
Your sandbox request metadata is stored for review without issuing API keys.
AnnuVera capabilities remain governed while workflow, notification, and persistence layers mature.
Support messages are visible in demo mode and remain non-delivering until notification execution is approved.
Recent activity.
Reviewer demo mode opened
The dashboard loaded repository-backed metadata only and did not access production secrets or provider credentials.
Provider status reviewed
Provider readiness was displayed from stored visibility metadata without provider execution or network calls.
Merchant onboarding draft viewed
Business information and KYB intake were displayed from merchant repository metadata.
Support link opened
The user can reach support, privacy, terms, and account deletion information.
Merchant onboarding workflow loaded
Merchant onboarding, KYB, provider readiness, and approval workflow state loaded from repository metadata.
notification-business-verification
Notification channel in_app is rendered; deliveryExecuted=false.
notification-merchant-provider
Notification channel email_ready is suppressed; deliveryExecuted=false.
Merchant review queue loaded
Merchant review, assignment, SLA, and approval metadata loaded from the operations repository.
Provider onboarding escalation recorded
Provider onboarding escalation metadata was persisted without provider calls or credential access.
Support ticket loaded
Support ticket lifecycle, conversation, internal note, attachment metadata, and preferences loaded from repository state.
Operations audit event loaded
Operations, review, approval, and support events are aggregated into a repository-backed audit timeline.
Dashboard intelligence refreshed
Dashboard metrics were aggregated from existing platform persistence without financial or provider execution.
Reviewer demo mode opened
The dashboard loaded repository-backed metadata only and did not access production secrets or provider credentials.
Provider status reviewed
Provider readiness was displayed from stored visibility metadata without provider execution or network calls.
Merchant onboarding draft viewed
Business information and KYB intake were displayed from merchant repository metadata.
Support link opened
The user can reach support, privacy, terms, and account deletion information.
Business profile loaded
Business profile, contacts, and operational settings loaded from repository metadata.
Provider enrollment reviewed
Provider enrollment metadata was displayed without provider execution or credential exposure.
Developer registration opened
Developer profile, organization, and sandbox request metadata loaded from repository state.
Webhook registration reviewed
Webhook registration metadata was stored without signing secrets or provider calls.
Merchant onboarding workflow loaded
Merchant onboarding, KYB, provider readiness, and approval workflow state loaded from repository metadata.
notification-business-verification
Notification channel in_app is rendered; deliveryExecuted=false.
notification-merchant-provider
Notification channel email_ready is suppressed; deliveryExecuted=false.
Merchant review queue loaded
Merchant review, assignment, SLA, and approval metadata loaded from the operations repository.
Provider onboarding escalation recorded
Provider onboarding escalation metadata was persisted without provider calls or credential access.
Support ticket loaded
Support ticket lifecycle, conversation, internal note, attachment metadata, and preferences loaded from repository state.
Readiness visibility stays non-executing.
Stripe
gatedpilot_ready
Provider code stripe is visible from repository metadata only. Execution enabled: false.
Paystack
gatedsandbox_ready
Provider code paystack is visible from repository metadata only. Execution enabled: false.
MTN Mobile Money
gatedsandbox_ready
Provider code mtn_momo is visible from repository metadata only. Execution enabled: false.
M-PESA
gatedsandbox_ready
Provider code mpesa is visible from repository metadata only. Execution enabled: false.
Orange Money
gatedsandbox_ready
Provider code orange_money is visible from repository metadata only. Execution enabled: false.
Flutterwave
gatedsandbox_ready
Provider code flutterwave is visible from repository metadata only. Execution enabled: false.
Dashboard, portal, organization, merchant, developer, and operations views share one identity model.
Provider-agnostic identity with WorkOS readiness.
The website now reads a shared identity abstraction and repository layer for provider readiness, sessions, organizations, members, invitations, roles, permissions, workflow state, and lookup surfaces. WorkOS stays configuration-only without returning credentials or making provider network calls.
Session
demo_active
Demo mode
true
Organization
under_review
Verification
pending
Members
1
Invites
1
Roles
6
Network calls
0
Users stored
1
Sessions stored
1
Registrations
1
Security events
1
Role assignments
1
Team hierarchy
1
Registration: in_progress
Organization creation: in_progress
Invitation lifecycle: draft
Verification lifecycle: pending
Role assignment: completed
Repository backed: true
Provider execution enabled: false
Financial execution enabled: false
Settlement execution enabled: false
Ledger posting enabled: false
Treasury execution enabled: false
Secret values returned: false
WorkOS production activation stays configuration-only.
Production callbacks, logout redirects, session cookies, signed claim validation, organization provisioning, and role enforcement are modeled without enabling live authentication or returning secret values.
Decision: BLOCKED
Readiness score: 36
Health endpoint: /api/identity/health
Production authentication enabled: false
Callbacks
blocked
Logout
blocked
Session cookies
blocked
Signed claims
blocked
Organization provisioning
ready
Role enforcement
ready
Production safety
ready
Secrets returned
blocked
The financial core remains untouched.
Provider execution
false
Money movement
false
Ledger posting
false
Settlement execution
false
Balance mutation
false
Credentials exposed
false
Secrets exposed
false
Real PII used
false