Embedded finance for marketplaces and gig platforms
A payout is money leaving the platform for good, and everything it earns on the way out earns for somebody else. Give the people you pay a wallet instead, and the balance stays where they already are: spendable on a card in your brand, reachable early when they need it, and working for you the whole time it sits there.
Your brand, your screen. Alviere is the platform underneath.
Marketplaces find the buyers, close the sale and work out what everyone is owed. The balance sits with a processor in escrow, which sets the dates and earns on it until somebody takes it out. Holding it yourself is not a new product: it's taking control of what you already built.
The checkout flow does not change and the payment processor stays. The balance still lives inside the app they already use, under your name, on screens you control. A payout ends the relationship every cycle. Money that stays in your product is a reason for both sides to come back.
One integrationOwning the balance is what unlocks the ability to monetize it. The financial products you layer on it turn the same money into revenue: when they spend it, when they need it before the date, when they want it in seconds, and every day it sits there earning.
What it earnsNo sponsor bank to go and win, no account structure to build that keeps balances off your books, no ledger and no compliance function to staff. Balances sit at our partner bank, never on your balance sheet. One contract covers the bank, the rails, the card and the operations.
You do not build a bankEvery cycle you already work out who is owed what, and when they can have it. That calculation and the payment itself do not change. What changes is where the money goes: Alviere sits after the payment and enables everything that comes next.
One call carrying who is owed what, and the date it becomes available. Balances credit straight away, so they watch money arrive rather than waiting for a payment file to land.
The money itself moves as a single daily transfer on the settlement cycle you already keep, instead of thousands of individual payments.
Your app shows the balance and provides all the options for what they can do with it. Everything earns a fee, and the more they use it the more it earns.
Each marketplace has different needs depending on what they sell, how they sell it, and who they pay. Owning the balance means you can layer the financial products that make sense for your business, and time them out according to your roadmap and strategy.
Everything your people already have carries on: ACH, RTP, FedNow, or a push to a card they already hold. They have the same experience as today, but now from your balance instead of something held in escrow at your processor.
A virtual and physical debit card in your brand, issued against the balance. They spend anywhere the network runs, and every purchase away from your platform pays you.
Interchange on every purchase, ATM withdrawal and international purchase, earned on card spend. Every dollar spent on the card is also a dollar that never had to be sent anywhere.
Issuance and replacement, fraud monitoring, and every dispute and chargeback under network rules, deadlines included. The number on the back of the card is ours, so the 24/7 cardholder line is ours to staff and ours to answer.
Money that has already passed its date, pushed over the card networks to a debit card they carry today. Typically within minutes, at any hour, with nothing new to activate.
A fee on every push, which you set. Nothing is advanced: the money is already available, and what is being paid for is the speed of getting it out.
The network push, the tokenization, and what happens when a card declines or an issuer rejects it. Failures come back as a state you can act on rather than as a support ticket.
Every balance credit carries an availability date that you set. Early Pay moves that date forward, in full or in part, for a fee. The work is done and the transaction is recorded; what changes is the availability timing, not the amount.
A fee on each release, per transaction or for a group of transactions. You can decide to fund the early money yourself, or have Alviere fund it.
The release mechanics, the ledger entry and the fee shown at confirmation. Nobody owes anything afterwards, so there is nothing to collect and no arrears process for anyone to run.
When a balance is spent on your platform, it moves wallet to wallet without touching an external network. That covers buying from another person and paying you: a subscription, a listing fee, promoted placement, a shipping label. Nothing clears, so nothing costs.
No cost to move it, because it never leaves. You stop paying card acceptance on your own fees, and the balance becomes the next person's balance and keeps earning.
The ledger movement and the reconciliation behind it. Wallet to wallet is a single entry, so there is no clearing to chase and nothing to match against a settlement file.
If your audience includes expats who send money home, or companies that pay their suppliers internationally, they can do it inside your product. Transfers to more than 120 countries from the same balance, with no wire, no correspondent bank and no separate remittance app.
Transaction fees and foreign exchange on every transfer.
The corridors, the foreign exchange, sanctions screening on every transfer, and the payout partners at the other end. You hold none of those relationships.
The balance carries its own account and routing numbers, so it behaves like an account rather than a holding pen. Money can arrive from anywhere, not only from you, and it does not need a bank relationship that someone may not be able to open.
Yield, and more of it than any payout model would show you. Every other line here earns on money you paid out. This one brings in money you did not: another employer's deposit, a refund, a transfer from family. A seller who treats the balance as their account holds more than you sent them.
The account structure, the numbers themselves, and the screening on anything arriving from a third party. Inbound money from outside your platform is our obligation to check, not yours.
Holding money for other people and moving it around is a regulated activity, and it is one of the reasons most marketplaces stop at paying out. It is a sponsor bank, an account structure that keeps balances off your books, a compliance function and the people to staff it. That is the part we already own, and it is the part you do not have to take on.
Balances sit at one of our partner banks, in an account held for the benefit of the people you pay, titled so that each person's share is identifiable. Custody is the bank's and the balance is theirs, which is why none of it reaches your balance sheet or ours.
We hold the licenses and carry the regulatory obligations by default, including the examinations and the reporting behind them. If you already hold your own, or decide you want to in one market, the same platform runs underneath it.
Identity and business verification, sanctions and watchlist screening, and the monitoring and record keeping that follow. What lands in your product are the screens, and then you hand us the information you already collect. The decisions, the liability and the audit trail are ours.
Issuance and replacement, fraud monitoring, and every dispute and chargeback under network rules and deadlines. The number on the back of the card is ours, so the 24/7 cardholder line is ours to staff and ours to answer.
Balances are eligible for pass-through deposit insurance. The conditions that come with that are in the questions below.
What leads depends on how money reaches them, and on what they do with it once it is there.
Money is available the same day, so the demand is for speed rather than early release. Card spend runs highest in this use case.
Pros are paid per job rather than per shift, so income arrives in pieces with gaps in between. How quickly each payment lands is what they notice, and having an easy way to reach it is what they care about most.
Secondhand or handmade, the seller ships it themselves, so funds clear a few days after delivery once a return window closes. A short wait is still a wait, and both products sell against it.
Monthly settlement means sellers wait weeks. Working capital is what they actually ask for, and some are still paid by check.
Sellers are often running inventory rather than selling their own things, so the payout funds the next buy, and eight days is eight days too long when the next show is on Friday.
Payment runs on a monthly close rather than on the sale, so a creator waits weeks for money that was irregular to begin with.
Your product already has the payouts flow, and that flow already calls an API to tell a processor to move funds out. Point the same call at us so credits and debits act on your balance instead, with your own rules. The screen, the button and the journey stay yours.
Alviere is an API-first product giving you full flexibility to integrate it into your own flows, and pick only what you need. Idempotency and external references to your system's entities are built in by design.
Web components that work in any framework, plus native iOS and Android SDKs for accounts, payments, cards and remittances. Take them as they are, or take the headless core underneath and put your own design system on top.
Events grouped into subscriptions you point at your own URL, each one reporting something that happened, in real time. Nothing blocks on delivery, and you are never polling us to get information.
POST /accounts
{
"external_id": "seller_4471",
"account_type": "BUSINESS", // or CONSUMER
"information": { /* name, contact, identity */ }
} One per payee, a person or a company. Identity lives here and is never asked for again.
GET /accounts/{uuid}/wallets/{uuid}
Response
{
"wallet_uuid": "wal_71ab",
"currency": "USD",
"funds": {
"balance": 128400, // settled, in the bank
"pending": 34000, // unsettled
"available": 128400 // authorized to spend
}
} Settled, unsettled and spendable, separately. This is what a pending Early Pay credit looks like before its date.
POST /early-pay/transfers
{
"amount": 34000,
"available_at": "2026-10-03T00:00:00Z", // RFC 3339
"external_id": "job_88213",
"source": { "wallet_uuid": "wal_ops_4f1a" },
"destination": { "wallet_uuid": "wal_71ab" }
} What someone earned, and the date it becomes theirs. Instantly or on a schedule that you control.
POST /early-pay/release
{
"transaction_uuid": "txn_5c9d",
"external_id": "rel_10774",
"amount": 20000 // optional: omit to release all of it
} Early Pay. Moves the date forward on one credit. Pass an amount to release part of it and leave the rest on schedule.
POST /wallets/{uuid}/withdraw
{
"amount": 34000,
"payment_method_uuid": "pm_9f2c",
"external_id": "wd_44190"
} Out to a bank account they have registered.
POST /wallets/{uuid}/transfer
{
"amount": 34000,
"beneficiary_uuid": "ben_04de",
"external_id": "rem_2281"
} Out to a beneficiary, including across borders.
POST /wallets/{uuid}/push-to-card
{
"amount": 34000,
"payment_method_uuid": "pm_c318",
"external_id": "ip_77301"
} A tokenized card they already hold, typically arrives in minutes.
POST /wallets/{uuid}/issued-cards
{
"external_id": "card_9931",
"product_id": "prd_2a70"
} Virtual straight away, physical on request, spends against the same balance.
POST /wallets/{uuid}/service-fees
{
"service_fee": {
"description": "Instant payout",
"calc_type": "DEDUCT", // or UPCHARGE
"category": { "transaction_fee": { /* see reference */ } }
}
} Your own fee on any of the above, one-time or periodically.
POST /wallets/{uuid}/quote
{
"amount": 34000,
"amount_currency": "USD",
"beneficiary_uuid": "ben_04de"
} The rate and the fee before anyone commits to sending.
No to both. Buyers pay exactly as they do now, through the processor you use today. Alviere sits after the payment, on the payout side, and never touches the buyer flow.
You send us what each person is owed, which is the same calculation you already run every cycle. Balances are credited straight away, so people see money arriving. The cash itself moves separately. Your processor now routes settlements in bulk, as one transfer on the cycle, rather than as thousands of individual payments.
Alviere takes care of the movement of funds and all the sub-ledgers for the people you pay out.
No. Balances never sit on your balance sheet and are never mixed with ours. They are held at one of Alviere's partner banks, Member FDIC, in an account held for the benefit of the people you pay, so the money is theirs throughout and custody is the bank's.
The account is titled and recorded so that each person's share is identifiable, which makes balances eligible for FDIC pass-through deposit insurance of up to $250,000 per person, per insured bank, in the event the bank fails. Alviere is not a bank and is not itself FDIC insured. Pass-through coverage applies to the failure of the insured bank rather than to other losses, and it aggregates with any other deposits that person already holds at the same bank.
The full custody, reconciliation and wind-down detail belongs in diligence rather than on a web page. We will take your risk and finance teams through it line by line whenever you want it.
No. This is purely additive. ACH, RTP, FedNow, push to card and bank transfer all still work, and anyone who wants nothing to change can carry on withdrawing exactly as they do now. The difference is that you now control the money movement and earn on each transaction.
Yes, and most do. The wallet is the foundation and every product runs on the same balance, so the integration, the objects and the events are already there when you add the next one. What a new product does cost you is its own screens, its own terms and its own support path. It is a smaller build than the first, not no build at all.
Yes, and so does same-day availability, and everything in between. The availability date is a rule you configure, not a constraint we impose. Balances track credited and available separately, so someone can watch money arriving while your return or dispute window is still open.
Nobody borrows and nobody repays. The person being paid receives their own money earlier than the date you set. Nothing is extended to them, there is no application and no credit check, and no obligation is created on their side.
What changes is the date, not the amount and not the direction. Before the release the money already sits in their balance as a pending credit; the release makes it available. If you fund the acceleration yourself, you are simply releasing your own money earlier. If we fund it, that arrangement sits between you and Alviere, and still never with the person being paid.
Characterization varies by market, so it is confirmed with counsel before launch rather than asserted on a web page.
They are the ones this helps most. A balance and a card give someone a way to be paid, to spend and to take out cash without a bank relationship they may not be able to open. On gig platforms this is often a large part of the base.
That is the direction most of this goes. The balance can take money in from more than just you, and savings, secured cards, rewards and cross-border run on the same ledger without a second integration. What any given program supports is set in its configuration rather than fixed, so the specifics are a conversation. The account capability itself is covered in full by our embedded accounts product rather than by payouts.
The float you earn between the buyer paying and the payout running does not go away. What a wallet adds is balance that stays past the payout date, because someone who can spend from it has less reason to move it out. That is additive to the cycle you run today, not a replacement for it.
This depends on the products you decide to implement and your own development cycles. Typically, 60 to 90 days for the wallet and the first payout. Anything added afterwards is an addition to an integration that already exists.
Bring how many people you pay, how often, and what it costs to move the money. We will come back with what a wallet changes, what it earns and how long it takes.