Ready nowWorking inside pre-production
Pre-production command center
Launch Control
A single, honest view of what works now, what only needs a provider adapter, and what cannot be activated before Meridian has a legal entity.
Adapter readyWaiting for external credentials
Company blockedRequires contracts or legal approval
Activation rule
The product can be complete before the company exists.
Meridian keeps provider boundaries explicit. Customer billing through Paddle is separate from Paddle's Payoneer settlement and from participant rewards. Identity, connectors, KYC, and participant payouts can be exercised in test mode now and activated later without redesigning consent, audit, finance, or privacy.
01
Operational
Identity boundary
Verified sign-in, pseudonymous actor keys, server-side RBAC and same-origin writes are active.
READY02
Operational
Durable product state
D1 persistence, versioned migrations, idempotency and audit evidence are connected.
READY03
Operational
User and organization onboarding
Profiles, adult attestation and organization applications are available in pre-production.
READY04
Operational
Consent and data exchange
Offers, granular consent, revocation, aggregate delivery and usage evidence run end to end.
READY05
Operational
In-app notifications
Account and workflow notifications persist with user-controlled preferences.
READY06
Operational
Email delivery
Verified Resend delivery, encrypted contacts, idempotent sends, multilingual templates and signed delivery webhooks are active.
READY07
Operational
Legal and privacy center
Terms, Privacy Policy, production DPA and a role-aware provider register are publicly available with an explicit pre-incorporation boundary.
READY08
External adapter
Paddle customer billing
Sandbox-first Paddle.js checkout, signed idempotent webhooks and minimal billing state are implemented; credentials, catalog price and seller settings activate it.
ADAPTER09
Operational
Paddle seller settlement
Paddle-to-Payoneer settlement is correctly isolated as an account-level revenue payout and requires no access to participant data or application code.
READY10
Operational
Public identity and account recovery
Public provider-managed sign-in, registration, verified email, recovery and server-side identity attribution are active.
READY11
External adapter
Mandatory organization MFA
Users can enable provider MFA; organization-wide enforcement requires an authentication-strength claim or enterprise identity provider.
ADAPTER12
Legal entity gate
Real data connectors
The certified adapter boundary is ready; a provider contract, credentials, data map and approved pilot partner are still required.
BLOCKED13
Legal entity gate
Production KYB/KYC
Synthetic four-eyes verification is ready; no real identity provider can be selected or contracted before the operator and production jurisdiction are confirmed.
BLOCKED14
Legal entity gate
Real participant EUR/USD payouts
The double-entry ledger is ready; Paddle/Payoneer seller settlement is not a participant payout service. A licensed payout provider and compliance onboarding are required.
BLOCKED15
Legal entity gate
Production jurisdiction
No country can be activated before legal review, DPIA and signed operating ownership.
BLOCKEDWhat remains at commercial activation
Four external switches — no product rebuild
01Legal operator identity and signed contracts02Paddle credentials, price, webhook and approved domain03Participant payout and KYB/KYC providers04One approved connector and production jurisdiction