PART 01 · OUR LUMO EXPERIENCE

One wallet.
A complete ecosystem.

Built by our team across app, backend, integrations and operations.

WALLET EXPERIENCELUMO ECOSYSTEMCONNECTED SERVICESwalletbusinessintegrateintegrateassistPersonal walletCreate · import · manage assetsBusiness userInvoices · payment linksLumo WalletApp + backend + operationsSwaps & fiatThird-party integrationsVirtual cardsProvider-backed spendingAI assistanceSupport + critical-action alerts
Practical delivery experience across the full wallet lifecycle.
LUMO · SYSTEM OVERVIEW

The complete picture.
Every layer has a role.

Logical architecture: the backend is a service inside the server, not a separate custody layer.

USER DEVICE / PUBLIC ACCESSAPPLICATION SERVER · EC2DATA & EXTERNAL SERVICESrequestsAPIadminwebrecordschain dataservicesLumo appLocal keys & signingCloudflareProtected traffic routingBackend APIAuthentication & servicesAdmin panelFeatures · chains · feesLanding pagePublic websiteMongoDBApplication recordsBlockchain APIsBalances & transactionsThird-party providersSwaps · ramps · cards
Private keys and recovery phrases stay on the device. Provider card and payment services have their own processing boundaries.
LUMO · APP ARCHITECTURE

The app owns
the signing experience.

The backend supports the journey. The user’s device controls wallet signing.

USER’S DEVICEAPP CONTROL & SIGNINGNETWORK / STATUSsetuplocal keysbroadcaststatusWallet setupCreate or importEncrypted key vaultCredentials stay on-deviceWallet interfaceSelected wallet & networkTransaction reviewRecipient · amount · feesUser approval + signingDevice authenticationBlockchain networkSigned transaction onlyTransaction statusPending / confirmed / failed
Device-backed storage support varies by platform; signing keys may be decrypted locally for signing. No backend custody.
LUMO · BACKEND ARCHITECTURE

One coordination layer.
Clear responsibilities.

The API connects wallet users to data, application services and external providers.

APP REQUESTSBACKEND SERVICES · EC2DATA / THIRD PARTIESrequestrecordsdataAPI callresponseLumo appWallet & operation contextResponse to appData, quote or service statusValidate & authorizeWallet proof · input checksService coordinationWallet · provider · businessMongoDBApplication & business dataBlockchain / indexerBalances · historyProvider APIsExternal service execution
The backend never needs the user’s private key. Wallet and admin sessions are separate.
LUMO · SEND & RECEIVE CRYPTO

From your wallet.
To theirs. With confidence.

Send crypto to any compatible wallet address—or receive with an address and QR code. Every transfer stays under the user’s control.

SENDER · LUMO APP

Your wallet

Choose asset & network
Enter address or scan QR

Review → approve → sign locally
BLOCKCHAIN NETWORK

Transfer & confirmation

Signed transaction is broadcast
Network confirms the transfer

Network fee shown before approval
RECIPIENT · COMPATIBLE WALLET

Their wallet

Crypto arrives on the
selected blockchain network

Recipient does not need Lumo
Signed transaction→
On-chain delivery→
RECEIVING IS SIMPLESelect network → share address or QR → track incoming fundsIllustrative QR only. Always use the address and network shown in the live app.
✓Clear transaction status
Built-in checks: valid destination · correct network · sufficient funds including fees · confirmation before signing. Some chains require a destination tag or memo.
LUMO · CHANGENOW SWAP FLOW

From one asset
to another.

ChangeNOW is the third-party swap provider. The app remains responsible for wallet approval and signing.

LUMO APP · USER DEVICEBACKEND · EC2CHANGENOW · THIRD PARTYrequestAPIquotedepositstatusupdateChoose swapAssets · networks · amountReview & approveQuote · receive amount · feesSign deposit locallyUser controls wallet keysQuote / order coordinationProvider request & responseTrack swap statusProcessing → completed / failedSwap quote / orderProvider route & conditionsProcess depositExecute provider swapDeliver output assetTo user’s destination wallet
Flow is a logical integration view. Swap execution uses the provider’s route and settlement conditions.
LUMO · ON / OFF-RAMP FLOW

Connect fiat payments
to a self-custodial wallet.

MoonPay and Stripe are third-party integrations; eligible purchase, sale and payout routes depend on the provider.

LUMO APP · USER DEVICEBACKEND · EC2THIRD-PARTY FIAT SERVICESrequestsessionsessionopen UIeventstatusChoose buy / sellAsset · amount · walletProvider payment UIUser completes required checksWallet / payout statusBuy to wallet · sell to fiatCoordinate sessionPrepare provider journeyPayment statusVerify & relay integration eventsMoonPayEligible buy / sell routesStripeEligible payment / buy routesSettlementWallet credit / eligible payout
Provider status returns to the app through the integration. Stripe is not presented as a universal off-ramp.
LUMO · INTERLACE CARD FLOW

A spending layer.
Connected to the wallet.

Interlace supplies the virtual-card service. Lumo presents the card experience.

LUMO APPBACKEND · EC2INTERLACE · THIRD PARTYrequestAPIresponseupdateCard request / actionCreate · top up · freezeCard dashboardDetails · activity · controlsAuthorize & coordinateValidate action · call providerReturn card statusPresent provider responseVirtual card serviceCreation & managementProvider card dataCard status & transactions
Lumo’s SRS separates wallet credentials on-device from card data handled by the third-party provider.
LUMO · MERCHANT EXPERIENCE

From payment request
to visible payment status.

A business workflow connected to the customer’s crypto payment journey.

BUSINESS / CUSTOMERLUMO BACKEND · EC2PAYMENT ROUTE / DATAcreatesavelinkpaystatusnotifyupdateBusiness userCreate invoice / linkCustomer payment pageAmount · address · QRBusiness dashboardPayment status & notificationInvoice servicesGenerate record & payment linkPayment trackingUpdate status & notifyApplication recordsInvoices & business dataPayment integrationSupported network / provider
Wallet support and merchant-plugin asset/network scope are distinct.
LUMO · AI SUPPORT & CRITICAL-ACTION ALERTS

Helpful AI.
A precise scope.

Lumo’s AI was for support chat and alerts when a critical action was detected.

USER JOURNEYSLUMO AI ASSISTANCEUSER FEEDBACKquestionguidancedetectalertSupport questionUser asks for helpSensitive actionUser initiates wallet operationAI support chatGuidance & explanationsCritical-action detectionDetect & prompt alertSupport responseInform the userCritical-action alertUser reviews operation
Lumo’s AI did not execute natural-language transfers or swaps. A transactional AI wallet is proposed separately for your product.
LUMO · DEVOPS ARCHITECTURE

A narrow public surface.
Restricted data access.

Reported Lumo hosting and access controls.

PUBLIC ACCESSEC2 · APPLICATION SERVERDATABASE ACCESSwebDB accessUsers & administratorsApp / browser accessCloudflareProtected routingNginx entry pointPublic web ports 443 / 80Backend APIApplication servicesWebsite & admin panelPublic page / protected adminMongoDBServer IP allowlisted
No other publicly open server ports reported. For the client release: validate encrypted transport, origin restrictions and operational access.
LUMO · ADMIN & AUTHENTICATION

Operational control.
Separate from wallet custody.

Administrators manage application services and commercial settings.

OPERATOR ACCESSADMIN DOMAINSERVICE CONFIGURATIONloginwallet proofmanagemanagemanageAdministratorLogin requestWallet userSeparate authentication domainAdmin authenticationJWT + authenticator verificationWallet authenticationSeparate secrets & guardsChains & featuresEnable / disablePlatform feesAdjust applicable feesBusiness onboardingReview / approve
Admin access does not expose user recovery phrases or grant wallet signing access.
PART 02 · OUR SOLUTION FOR YOU

Your vision.
An experienced delivery partner.

Bring your conversational wallet to market with practical experience across self-custody, multi-chain transactions and provider integrations.

OUR DELIVERY EXPERIENCEYOUR WALLET FOUNDATIONYOUR WALLET CAPABILITIESexperiencedeliveryextendextendvalidateLumo wallet experienceSelf-custody & multi-chainIntegrations & operationsProviders · backend · adminYour wallet experienceOne connected user experienceConversational actionsAI proposes · user approvesRecipient & dApp flowsClear context & permissionsRelease validationWallet + AI + security review
Informed decisionsClear delivery ownershipFocused MVP execution
For your project, we bring hands-on wallet experience, end-to-end delivery ownership and a clear approach to building AI-assisted transactions with user approval.
OUR SOLUTION FOR YOU · AI TRANSACTION FLOW

Natural conversation.
Confident user control.

Our solution makes everyday wallet tasks simpler while keeping you and your users in control of every transaction.

YOUR APP · USER CONTROLAI SERVICES · ACTION PROPOSALSDEVICE SIGNING / NETWORKrequestproposalapprovestatusupdateUser request“Send 50 USDC to John”App validationChain · asset · recipient · fundsExact transaction reviewFull address · amount · feeInterpret intentStructured action proposalShared wallet / chat stateReflect transaction statusUser approvalDevice authenticationLocal signingKeys remain on-deviceBlockchain networkBroadcast & track status
User trust is built into the flow: validate independently, show exact transaction details, require approval again if they change, and sign only on the device.
OUR SOLUTION FOR YOU · USER SAFEGUARDS

Earn trust.
Through predictable behavior.

We build clear safeguards into your wallet, so users know what happens next—even when a request is ambiguous, a quote changes or a provider is unavailable.

REQUEST / SERVICE RISKSOUR VALIDATION & SAFEGUARDSPREDICTABLE USER EXPERIENCEcheckconstrainhandleresolveapproveinformAmbiguous actionWrong recipient / networkUntrusted contentPrompt manipulationProvider disruptionExpired quote / downtimeResolve & validateContact · chain · token checksConstrained AI actionsAllowlist + independent validationStatus & reconciliationRefresh · controlled retryReview exact detailsUser understands the actionExplicit user approvalNo silent signingClear next stepPending / retry / recovery
Release checks: wallet/recovery tests · chain-specific tests · adversarial AI tests · independent security review.
OUR DELIVERY APPROACH

A focused MVP.
A disciplined path to launch.

Agree the product boundaries, prove the core journeys, then release against defined security and operational checks.

SCOPE & FOUNDATIONSBUILD & CONNECTVALIDATE & LAUNCHbuilddesignconnecttestreviewverifyDefine product scopeChains · devices · providersTrust boundariesKeys · AI policy · approvalsWallet coreCreate · send · swaps · historyAI-assisted wallet actionsRecipients · dApps · chat actionsRelease testingRecovery · load · adverse casesIndependent reviewResolve findings → launch
Start together: confirm the launch chains, target devices, AI action scope and provider coverage. Then agree milestones, acceptance criteria and the independent security review.
PART 03 · SEE THE PRODUCT

See what we built.
Let’s shape what comes next.

Explore Lumo across platforms, then align on the scope and delivery plan for your wallet.

Lumo illustrates our wallet development experience. Our solution for you will be tailored to your launch markets, supported chains and target devices. Architecture diagrams show the intended service responsibilities; the final integration design and provider coverage will be agreed during project scoping.
← → to navigate