Use Cases
Lightspark
Use Cases
Marketing
2 lightspark — About us View docs Log in Contact
I Replace fragmented vendors with one
ightspark for a par nen
stablecoins, local rails, and Bitcoin.
financial apps
Global Accounts
Nu México (++++ 3872) $500.00
withdrawn to bank
Just now
Tota balance
$5,000.00
‘Transactions
‘Weekly activity Biteoin
1 0.0000 BTC
Groen Bottle Coffee
om 4 7
Financial apps own the relationship.
The stack underneath is still fragmented.
The problem
The global account Wallets, neobanks, remittance apps, savings products, and consumer finance apps
already have something every financial provider wants: user trust, financial intent,
and repeated money behavior. Users open the app to store, move, convert, send,
‘spend, or manage money.
Security & compliance
Integration
Account controls Underneath that unified experience, the stack is often split across vendors. One
Closing partner issues cards. Another handles crypto. Another handles off-ramps. Another
supports cross-border movement. Another owns wallet controls or custody. Each
vendor solves a piece, but each boundary becomes a product constraint, an
Book a demo
operational queue, and a place where economics leave the app.
Explore sandbox
View docs
The global account
Acomplete dollar account.
Embedded in your app.
Global Accounts gives financial apps a branded dollar account inside the existing
product experience. It is the durable account layer users can hold, spend, cash out
from, convert through, and move across supported rails.
The account becomes the center, not another rail in the stack. Stablecoins,
local cash-out, cards, Bitcoin, and controls become behaviors around
‘one account relationship.
© Account of record Your brand
®© Stablecoin rails Major assets and chains
1 Local cash-out 65+ countries
& _ Visa debit cards 175M+ merchants
© Native Bitcoin instant swaps v
© Account controls Scoped access
‘The economics
Users can hold, spend, and cash out.
You own the economics.
Fragmented infrastructure fragments the business model. Cards monetize spend
somewhere else. FX spreads accrue to a corridor provider. Crypto conversion
happens in another product. Balances leave before they can deepen the relationship.
Accounts let the economics compound inside the app. Balances can generate
reserve rewards. Cards generate interchange. Foreign exchange carries margin.
Bitcoin trading carries spread. Cross-border movement, local cash-out, and
‘stablecoin interoperability become account features instead of vendor handoffs.
For financial apps, the strategic shift is simple: the account is no longer a thin
balance in front of someone else's rails. It is the operating layer where more of the
user's financial life can happen.
Reserve rewards 2.6-3.0% annualized $1B in balances = $26M-30M/yr
Cardinterchange revenue share on account spend
FX margin 100-200 bps on local currency conversions
Bitcoin trading Spread ‘on supported dollar/BTC swaps
Transaction fees Pertxn account movement and payments.
Security & compliance
Ship the account layer.
Not a new vendor maze.
Replacing a vendor stack only works if the control model gets clearer. Financial apps
need account infrastructure that can be evaluated by product, compliance, risk,
security, and operations teams without turning every new rail into a new build.
Global Accounts packages the hard parts behind the account: wallet authorization,
regulated movement, supported rails, compliance operations, webhooks, and
traceable account activity. The accounts themselves are self-custodial and built on
‘Spark. Neither Lightspark nor the financial app can unilaterally move user funds.
User authorization Customer signed
& Self-custody on Spark No unilateral movement v
@_ User authorization Customer signed
Self-custody on Spark No ur
TE Regulated rails Licen:
& Compliance operations KYC, KYB, sanctions
@ Security program SOC 2 Type Il and NIST CSF
© App-level controls Your product surface
Audit trail Traceable movement
One integration.
Test the account before replacing the stack.
This does not need to start as a rip-and-replace program. 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 Al-readable pages.
export GRID_BASE_URL="https: //api. light spark. com/grid/2025-10-13"
1. Creat
curl -X POST
-u
-H "Content-Type:
customerType": "INDIVIDUAL",
"platformCustomerId": “user_7c19e4a1",
region": "US"
email": "[email protected]",
"fullName": "Maya Chen"
"birthDate": "1990-01-15",
nationality": "US"
2. Fetch auto-provisioned G Ac
curl -X GET "$GRID_BASE_URL/internal-accounts?customerId=Customer : abi
-u "$GRID_CLIENT_ID:
curl -X POST "$GRID_BASE_URL/sandbox/internal-accounts/InternalAccout
-H "Content-Type:
-d '{ "amount":
As money work becomes agentic,
the account needs policy.
Financial apps are moving from passive balances to active money management:
bill pay, savings movement, remittance planning, card controls, FX decisions,
crypto conversion, and account monitoring. Agents will make more of that work
preparatory and automated.
The risk is not automation itself. The risk is automation without account boundaries. If
an agent can suggest, prepare, or queue money movement, the account needs
scoped access, approval thresholds, rail permissions, and an audit trail.
The agent gets a pocket, not the keys. Policy decides what is allowed, the account
enforces it, and the user stays in control.
oat
‘Agent
Working
Financial apps already have trust.
Now they can own more of the account.
Users come to financial apps with intent. They want to hold money, move it, convert it,
spend it, cash out, and keep control. The better that account becomes, the more
reasons they have to keep the relationship inside your product.
That only works if the account layer is unified. Not one vendor for every behavior.
One branded account that can support the behaviors users already expect
from modern money.
Financial apps already own the relationship. Give them an account layer worthy of it.
Your brand. Your economics. One integration.
Talk with sales >
Global accounts Financial apps Company Terms & conditions SOC 2 Type Il Book a demo.
Payments platforms News Privacy policy NIST CSF Get API key
Payouts Neobanks Careers Licenses ISO 27001
Pay-ins Marketplaces FAQ Cookie preferences Miewidocs)
Ramps On-demand platforms Support Sandbox.
Cross-border P2P Creator platforms Playground
Stablecoin payments Flow builder
Payouts
Pay-ins
Ramps
Cross-border P2P
‘Stablecoin payments
Agentic payments
Virtual accounts:
Wallets
Cards
Stablecoin issuance
Rewards
Deposits
Withdrawals
Swaps
Payments platforms News
Neobanks Careers
Marketplaces FAQ
On-demand platforms Support
Creator platforms
Sports & gaming x
LinkedIn
Global payouts
B2B payments
Payroll & EOR
Remittances
Embedded finance
Stablecoin payments
Treasury
Privacy policy
Licenses
Cookie preferences
NIST CSF
ISO 27001
Get API key
View docs
Sandbox
Playground
Flow builder
GitHub