One account per client, in their name.
USD account details at the bank you choose, in your client’s legal name, for ACH, wire and SWIFT. EUR, GBP and BRL alongside.
Why named accounts matter
A named account is registered to the holder’s legal name, not pooled and not behind a reference code. That matters for three reasons.

Compliance
Funds trace directly to the verified entity that owns the account.
Trust
Counterparties see the company name on the receiving account and wire with confidence.
Clarity
Every inbound wire links to the right entity. No matching against reference codes.
Capabilities

Named & multicurrency
Your client’s name, several currencies, local details to pay and get paid.
Choose the bank
Open each client’s USD account at the partner bank you choose: JPMorgan Chase, Citi, CFSB, Lead Bank, Portage Bank or Zenus Bank.
Worldwide SWIFT
Receive and send international USD wires to and from 100+ countries.
Automatic matching
Incoming deposits are linked to the right customer and wallet.
Pooled details
For one-off transfers, shared details with a reference still work.
Real-time notifications
A webhook for every deposit and state change.
Your client’s name, several currencies, local details to pay and get paid.
Open each client’s USD account at the partner bank you choose: JPMorgan Chase, Citi, CFSB, Lead Bank, Portage Bank or Zenus Bank.
Receive and send international USD wires to and from 100+ countries.
Incoming deposits are linked to the right customer and wallet.
For one-off transfers, shared details with a reference still work.
A webhook for every deposit and state change.
Who it’s for

Payroll platforms
Collect employer deposits into an account in the employer’s name, then pay out to the team.

Fintechs
Offer USD account details to customers without building banking infrastructure.

Import / export businesses
Receive buyer payments from abroad into an account in your name.

Marketplaces
Hold seller funds in dedicated details before payout, with clean separation per seller.

Remittance companies
Receive sender funds, quote the conversion and deliver onward.
How it works
- 01
Request
Onboard the customer and request the account capability through the API.
- 02
Create
Swipelux issues dedicated bank details once provisioning is complete.
- 03
Receive
The customer, or their sender, pays in through local rails or SWIFT.
- 04
Manage
Follow the balance, quote conversions and send payouts from your platform.
Compliance and trust
- Business onboardingKYB review of the entity, owners and control persons before accounts are enabled.
- Sanctions screeningSanctions and PEP checks on customers and on inbound and outbound transfers.
- Transaction monitoringContinuous AML and CTF monitoring with case escalation.
- Jurisdiction reviewAvailability depends on the customer and the corridor.
Questions about Accounts
More answers on eligibility, verification and timing in the Knowledge Base.
Which bank will my client’s account be at?
You choose the bank per client: JPMorgan Chase, Citi, CFSB, Lead Bank, Portage Bank or Zenus Bank in the US, Stark Bank in Brazil and NVIO Pagos in Mexico.
Whose name will the payer see?
Your client’s. Named accounts carry the client’s legal name, so payers see who they are paying, not a processor.
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.
Can I start without an API integration?
Yes. Start in the dashboard, add the API when ready. Onboard clients with a shareable link in the meantime.
