Why wallet-based payments?

If you're coming to Lumanu from Stripe Connect, Tipalti, Trolley, or another payout provider, the most important thing to understand before reading any migration guide is how Lumanu's model differs from a pure payout system. You work with a smaller API surface than you'd expect. Lumanu shifts many responsibilities from your platform to the vendor.

The mental model

In a payout system, your platform is the custodian. You hold funds, configure when and how to disburse them and are responsible for money reaching the vendor's account.

In a wallet system, the moment you process a payout and credit a vendor's wallet, the money is theirs. Your platform's responsibility ends at funds available — not funds in their bank account. The vendor decides when to withdraw, which rail to use, and how much to take at a time. Lumanu shifts the last mile from your platform to the wallet holder.

This is a small semantic shift with large downstream consequences. The last mile includes bank connections, KYC, rail selection, failure handling, and FX. That part of the flow carries most of the cost, complexity, and compliance burden in payout systems. Moving it to the wallet boundary is what makes Lumanu's integration smaller than the system you're migrating from.

What this means in practice

Vendors control how, when, and how much to withdraw

This is the single most visible change. Your platform no longer configures payout schedules, minimum thresholds, or preferred rails on behalf of vendors. Each vendor picks their own:

• How: ACH, wire, international rail, card, or leaving funds in the wallet for future use.
• When: on demand, at a time of their choosing.
• How much: full or partial withdrawal

For creator-economy and marketplace platforms, this typically removes a large chunk of product surface area that was only necessary because the platform was making the withdrawal decision. Vendors generally prefer managing this themselves; they know their own cash flow better than your system does.

Reduced platform liability

You never store, transmit, or hold vendor bank details. KYC and AML for withdrawals happen between Lumanu and the vendor, not through your platform. You stop being a compliance pass-through.

Faster settlement

Vendors see funds immediately on wallet credit, even if they later choose a withdrawal rail that takes days. When do I get paid? — the top support ticket for most payout-based platforms — largely goes away, because the answer is now, in your wallet.

Lower aggregate fees

When vendors batch and route their own withdrawals, they optimize for their own situation. Someone making rent on the 1st has different preferences than someone saving up for a quarterly tax payment. A payout system has to pick one rail and schedule for everyone; a wallet lets each recipient choose the cheapest option that meets their needs.

Better international coverage

A recipient in São Paulo knows Brazilian rails better than your ops team does. Wallets let vendors route through local options, including ones your platform would never have integrated directly.

Cleaner reversal semantics

You can reverse a wallet credit before withdrawal in milliseconds because it is a ledger operation. Reversing a completed ACH payout often means a phone call, and sometimes a lawsuit. If your business has any chargeback, dispute, or fraud exposure, this difference compounds quickly.

Self-service onboarding

Tax forms (W-9, W-8BEN, 1099, etc.), identity verification, and payment method setup happen inside the wallet. Your platform isn't the one collecting and storing this information.

What changes in your integration

Your integration gets simpler: you manage fewer concepts, fewer endpoints, and fewer responsibilities.

You stop managing: payout schedules, bank account storage, rail selection, payout retries, tax form collection, and KYC state for disbursements.

You keep managing: the moments when a brand approves and pays payment to a vendor in your product, an approved deliverable, a signed-off invoice, a closed milestone, and one API call to credit the wallet.