Blueprint · 01 Consumer neobank

A consumer neobank, composed in eight weeks.

Reference architecture for launching a consumer bank on the Klyqo Banking OS. Onboarding, account, debit card and notify on day one. KYC + AML + ledger + cards orchestrated as one journey, swap any provider on a binding. The canonical “challenger bank” pattern, on the marketplace model — no bundled lock-in, no 18-month integration project.

Talk to us about your launch See other blueprints
The use case

Building a bank from scratch and need every customer-facing moment running on day one.

A consumer neobank lives or dies on three things: onboarding that doesn’t lose customers in the funnel, a card that lands in the wallet before they forget you exist, and notifications that earn engagement instead of unsubscribes. Everything else is downstream.

8 weeks
Time to first paying customer
< 4 min
Median onboarding completion
D+1
Physical card delivery target
12 caps
Marketplace primitives wired
The architecture

Five layers + two rails. Klyqo composes them.

A consumer neobank is the canonical Klyqo deployment shape: the marketplace primitives the platform was built for, orchestrated through one TypeScript journey definition per customer-facing flow.

Compliance railGDPR consent, PSD2 SCA, marketing communication preferences
Layer 5 · Channels
Customer-facing surfaces
Mobile appWeb bankingCustomer supportEmail / SMS
Risk railReal-time fraud signals from device + behavior into every channel
ComplianceEvery binding call signed and logged; per-tenant audit trail
Layer 4 · Klyqo · the Banking OS
Runtime + marketplace dispatch
ComposeDispatchRunObserveOnboardVerifyOpen accountIssue cardNotify
RiskFraud + behavior scoring inline with every dispatch
ComplianceKYC vendor + AML vendor selection per tenant; export bundler regulator-ready
Layer 3 · Marketplace primitives & providers
The capabilities a consumer neobank needs
KYC · Onfido / PersonaAML · ComplyAdvantageCards · MarqetaNotify · Twilio + ResendLLM-as-binding · for triage
RiskFraud + biometric liveness checked in line during onboarding
CompliancePSD2 reconciliation; AML transaction monitoring connected to the ledger
Layer 2 · Core banking
Mambu · consumer-fit
CustomerCurrent accountSavingsDebit cardLedger / GL
RiskLedger + card controls enforce daily / monthly / channel limits
ComplianceBank licence in your jurisdiction or sponsor-bank arrangement
Layer 1 · Foundation (yours)
Licence · capital · sponsor-bank
Banking licenceEquity (seed + Series A)Sponsor or own BIN
RiskEquity + deposit insurance posture defines acquisition pace
The canonical journey

Sign-up to first card spend, in under five minutes.

Customer enters a phone number on the marketing site. Klyqo orchestrates KYC → AML → account opening → card issuance → welcome push, all as a single typed journey. Every step is signed, every step is replayable, every step lands in your audit log.

klyqo / journeys / consumer-onboarding · LIVE
01
Sign-upphone + email captured · consent recorded
< 5 s
02
KYC dispatchOnfido or Persona · document + selfie + liveness
~90 s
03
AML screeningComplyAdvantage · sanctions + PEP + adverse media
~5 s
04
Account opened in Mambucurrent account provisioned · IBAN issued
~3 s
05
Virtual card issuedMarqeta · tokenized for Apple/Google Pay
~4 s
06
Welcome push + emailTwilio + Resend · activation moment captured
< 2 s
07
Physical card dispatchembossed + posted · D+1 in EU
1–2 days
The providers used

What you pick from the marketplace.

A consumer neobank in this configuration uses five marketplace providers plus the core. Onfido is production; the others are scoped or in flight. The build sequence promotes them in the order the journey needs.

KYC · identity
Onfido
Document + biometric + liveness in 90 seconds median. Frictionless return-customer experience via cached identity hashes.
In flight
AML · screening
ComplyAdvantage
Sanctions, PEP, adverse media. Sub-second response with structured findings; integrated with the AML alert triage blueprint.
Roadmap
Cards · issuance
Marqeta
Virtual-first issuance with same-day Apple/Google Pay provisioning. Physical card pipeline as second journey, same adapter.
In flight
Notify · messaging
Twilio + Resend
SMS for transactional + push trigger, email for receipts + activation. Branded sender, deliverability monitoring.
Roadmap
Core banking
Mambu
Customer record, current + savings account, debit card account, ledger. Consumer-fit configuration with debit-only at launch.
In flight
LLM-as-binding
Anthropic / OpenAI
Bound per tenant. Used by the Operator Copilot to triage KYC exceptions and draft customer outreach. Human approves every action.
Roadmap
What this blueprint is and isn’t

Honest about the build.

The work this blueprint represents

A neobank in eight weeks is achievable on Klyqo if (1) you have a licence or sponsor-bank arrangement, (2) you accept Mambu as the core with a debit-first product, and (3) your acquisition strategy doesn’t depend on physical branches. Eight weeks gets you a working v1 with mobile onboarding, account, debit card, payments and notifications. It does not get you complex lending, treasury operations, or a multi-currency book.

What you bring: the licence (or BIN sponsorship), the brand, the acquisition motion, the compliance officer. What Klyqo brings: the runtime, the journey templates, the provider adapters, the audit log, the operator console. What we agree on together: which KYC vendor for your geography, which card issuer for your regulatory regime, which notify provider for your channels.

If you’re launching a consumer challenger and want to ship something real in eight weeks instead of eighteen months: talk to us before you scope the build against horizontal vendors who will quote you a year.

Launching a consumer neobank?

If you’re a founder with a sponsor-bank arrangement or a licence application in motion, the first conversation is short. Tell us about the market, the licence, the acquisition motion, the timeline. We’ll tell you honestly whether Klyqo is the right runtime for you today.

Email diogo@klyqo.com Response within two business days