Lightspark forneobanks
Go global without a new banking stack. Dollar accounts, local rails, cards, and Bitcoin for every customer, in one integration.
Global Accounts
(0, 0, 0)
The problem
You out-built the banks at home. The borders are still theirs.
Neobanks won by rebuilding the banking experience: better onboarding, better cards, better product. But the stack underneath is usually a domestic one. One country’s rails. One currency. A sponsor arrangement that stops at the border.
So the roadmap fills up with geography. Every new market means new licenses, new banking partners, new integrations, and a launch measured in years. Meanwhile your customers already live globally: they get paid across borders, send money home, travel, and want dollars when their local currency wobbles.
The global account
One account layer. Every market at once.
Global Accounts adds a global dollar account beside the banking core you already run. Customers hold dollar balances backed by stablecoins, move money in and out on local rails in 65+ countries, spend on Visa cards, and hold Bitcoin natively.
Your brand on the surface. One integration underneath.
Customers hold dollar balances backed by stablecoins, under your brand, wherever they live. No sponsor bank per market.
Money moves in and out through PIX, UPI, SEPA, FPS, and more. One integration instead of a banking partner per corridor.
Customers spend their dollar balance with virtual or physical cards, locally and globally, anywhere Visa is accepted.
Send in one currency, deliver in another. Real-time FX rates lock when the quote is created, with fees visible before execution.
Because Global Accounts run on Spark, customers can hold Bitcoin alongside dollars and swap instantly without leaving the account.
Give agents narrow budgets, approved rails, and approval thresholds so they can help operate the account without holding the keys.
The economics
New revenue per customer. Not new fees from your stack.
A domestic sponsor stack charges you for every layer: the account, the card program, the processor, the FX provider. Expanding it internationally multiplies the fee stack before the first customer signs up.
The global account pays you instead. Balances generate reserve rewards. Cards generate interchange. Foreign exchange carries margin. Bitcoin trading carries spread. When the account layer belongs to you, those flows accrue back to you, in every market it reaches.
Security & compliance
Ship the global account. Not the bank behind it.
Going international used to mean rebuilding the regulated machinery per market: money transmission, KYC, sanctions screening, custody, dispute handling, and partner operations. Global Accounts carries that side of the equation so your team doesn’t have to.
The accounts themselves are self-custodial and built on Spark. Neither Lightspark nor the neobank can unilaterally move customer funds. That makes the policy and approval model real, with boundaries enforced by architecture instead of trust.
Outbound movement requires the customer to authorize from their device. You design the flow, limits, and approvals, but the account owner stays in the loop when funds leave.
Global Accounts are built on Spark wallets, so account control is enforced at the wallet layer. Neither Lightspark nor the neobank can unilaterally move customer funds.
Lightspark Payments is registered with FinCEN as a money services business and holds money transmission licenses or registrations where required for Grid Transaction Services, with banking and payment partners behind the regulated rails.
Lightspark handles the operational work your team does not want to duplicate for new markets: identity checks, business verification, sanctions screening, risk review, and the compliance requirements attached to supported corridors.
The infrastructure is backed by Lightspark’s security program, audited under SOC 2 Type II with NIST CSF–aligned controls, so teams can evaluate the account layer like enterprise financial infrastructure.
You own the brand, UX, account rules, approval flows, and user experience. Lightspark powers the account and regulated movement underneath.
Standard API objects and webhooks keep funding, withdrawals, card activity, quotes, and settlement status visible to your team instead of hiding money movement in a black box.
Integration
One integration. Live in days, not months.
This is not a multi-year banking build. Your team starts with one API, a sandbox, and the normal objects you would expect: customers, accounts, quotes, transactions, and webhooks. Create the customer, fetch the Global Account, fund it in sandbox, and test the full request shape before production money moves.
The hard parts are already packaged: account provisioning, supported rails, wallet authorization, simulated funding, webhook events, and signed withdrawals. The docs give your team the implementation path: OpenAPI, copyable examples, sandbox test credentials, Postman collections, and AI-readable pages.
Agentic money
Banking is becoming agentic. The account needs to keep up.
Customers are already using agents to plan, buy, book, and reconcile. The next obvious step is moving money on a customer’s behalf. The interesting question isn’t whether agents will spend from customer accounts. They will. The question is what enforces the boundaries when they do.
The agent gets a pocket, not the keys. Policy decides what is allowed, the account enforces it, and the customer stays in control.
Closing
You changed how people bank. Now change where banking ends.
Your customers already trust you with their money at home. The next step is being their account everywhere: dollars when they want stability, local rails when they need cash, cards wherever they are, Bitcoin when they ask for it.
That only works if the global account lives inside your product. Not as a partner handoff. As the account layer.
Your brand. Your economics. One integration.