Get paid and pay out, one API.
Collect by ACH, wire, RTP, SWIFT and local methods like Pix and SPEI, then pay your client, their suppliers or anyone they pay. Every payout starts from a quote.
Get paid: collect from anywhere
Local transfers, wires, cards and stablecoins, settled into the customer’s wallet.

Multi-currency collection
Local payment methods
Cards and checkout
Stablecoin pay-ins
Screened USDC deposits straight into the customer’s wallet.
Real-time notifications
transfer.state_changed webhooks the moment funds move.
Automatic matching
Every pay-in is tied to its customer, wallet and transfer.
Screened USDC deposits straight into the customer’s wallet.
transfer.state_changed webhooks the moment funds move.
Every pay-in is tied to its customer, wallet and transfer.
Pay out: send to anyone, anywhere
To your client’s own account or anyone they pay, from a ready wallet.

Direct-to-bank payouts
To the customer’s own account on local rails.
Recipient destinations
Save third-party bank accounts and wallets, reuse them every cycle.
Quote-first pricing
The exact amount in and out, before execution.
Stablecoin-to-fiat off-ramp
Settle in USDC on the backend, deliver local currency on the front.
Crypto payouts
Send stablecoins to verified self-custody wallets.
Delivery tracking
Follow each transfer to its final state.
To the customer’s own account on local rails.
Save third-party bank accounts and wallets, reuse them every cycle.
The exact amount in and out, before execution.
Settle in USDC on the backend, deliver local currency on the front.
Send stablecoins to verified self-custody wallets.
Follow each transfer to its final state.
How it works
Four calls from quote to final state.
- 01
Send
Your platform requests a quote for the exact amount through the API.
- 02
Route
The quote fixes the destination, the rail and every fee.
- 03
Move
Execute the quote once with an idempotency key; funds move from the wallet.
- 04
Confirm
The recipient is paid and your platform gets the final state by webhook.
Built for your clients

Get paid in your client’s name.
Named account details per client, at the bank you choose.
Local and international, one flow.
Pix, SPEI, PSE, Transfers 3.0, RTP, ACH, wire and SWIFT land in the same balance.
See every payment.
From quote to completion, in the dashboard or by webhook.
Your setup today vs. with Swipelux
Swipelux runs on these rails too, so the comparison is with your setup today. See pricing.
Today
- BanksOne provider, one bank
- Whose nameThe provider’s name
- Ways to get paidWire and ACH
- StablecoinsA separate vendor
- Your revenueThe provider’s price
- VisibilityEmails and statements
With Swipelux
- BanksSix US banks to choose from, plus Stark Bank and NVIO Pagos
- Whose nameYour client’s name
- Ways to get paidPlus Pix, SPEI, PSE, Transfers 3.0 and RTP
- StablecoinsUSDC and USDT in the same flow, in and out
- Your revenueYour fee on top, per client
- VisibilityEvery payment tracked from quote to completion
Questions about Payments
More answers on eligibility, verification and timing in the Knowledge Base.
Which currencies and local methods are available?
USD over ACH, Wire, RTP and SWIFT, EUR over SEPA, local payments by Pix, SPEI, PSE and Transfers 3.0, and USDT or USDC on-chain.
How fast does money arrive?
RTP, Pix, SPEI and stablecoins land in minutes; ACH, Wire and SWIFT follow banking times. See the typical time per method.
What does it cost, and can I add my fee?
A transaction fee of 0.01–0.5% by corridor and volume, bank charges at cost and FX in the quote. You add your own fee per client.
Can clients both receive and send payments?
Yes. The same account and balance collect money and pay it out, to the client’s own account or to other recipients.
