Pay people abroad, each by the route that reaches them.

Cross-border payments

Pay contractors and teams in their own currency from one USDC balance: USD by ACH, EUR by SEPA and GBP by Faster Payments. Each payout reports its status and the amount that arrived.

Talk to us

Read the documentation

The September run

How one run reaches Carlos in Lisbon, Amina in London and Oliver in USDC.

A contractor platform pays its people abroad from one USDC balance. Carlos, a freelance illustrator in Lisbon, is paid in EUR; Amina in GBP; Oliver takes USDC.

Fund

One balance funds the run

The September run draws on one USDC balance on your customer’s account. USD or EUR can arrive by bank transfer and convert into USDC as it lands, and your team reads the balance before anything is paid.

The accounts and balances that fund each payout

Recipients

Each recipient is set up once

Carlos and Amina accept our partners’ terms, clear KYC and are added to the paying account as payout recipients. Oliver already holds his own USDC account on the platform. Remove a recipient’s role and their next payout stops.

Routes

The platform picks each recipient’s route

Carlos is paid by SEPA to his EUR account, Amina by Faster Payments to her GBP account, Oliver by USDC transfer. A bank route pairs the recipient’s bank account with the stablecoin that funds it, and only a route that reports ACTIVE can be paid.

Run

The run goes out as route, amount and key

Each payout names its route, the USDC amount and an idempotency key, so a retry never pays anyone twice. The request comes back REQUESTED; each payout then reports SENDING and PROVIDER_PROCESSING on its own.

Paid

Carlos’s payment lands

His bank receives EUR, and the payout reports COMPLETED with the fiat amount the provider actually paid. Amina’s GBP payout completes the same way, and Oliver’s transfer reports COMPLETED.

Booked

The ledger books what arrived

Your ledger books each settled amount, in the currency the recipient received. If a bank later sends a payment back, for a closed account or a name mismatch, the payout reports RETURNED and the booking is reversed.

The payout objects, fields and statuses in this story are documented in the pay-outs guide.

Read the pay-outs guide

Route sheet

Every route, and what is confirmed on it today

Every bank payout is funded from the USDC balance: the stablecoin leaves the account wallet and the recipient’s bank receives fiat. Supported routes carry the full status path; routes being added say so, and are not available until Venly confirms them for your customer and destination.

Recipients are verified and screened before money moves: KYC or KYB, sanctions screening, AML and transaction monitoring run on licensed partner rails. Every bank route also needs the recipient’s acceptance of our partners’ terms and a PAYOUT_RECIPIENT role, and only a route that reports ACTIVE can be paid.

Supported bank account types

Payout routes and statuses in the API guide

How a quote for your payouts is built

Run report

A September run of 20 recipients, totalled by route

Carlos, Amina and Oliver are three of the 20 people in the platform’s full September run. One balance funds it all, and each route reports on its own, so the report answers where every payment stands: completed, still with the provider, or returned by a bank.

Paying abroad, answered

Which routes can we pay on today?

Bank payouts in USD by ACH, EUR by SEPA and GBP by Faster Payments, and USDC transfers between accounts on your platform. USD by wire including international SWIFT, more payout currencies, and local-currency payouts in supported African markets to bank accounts or mobile money are being added; ask for availability in your corridors.

How long does a payout take?

Timing depends on the rail and the checks each payment needs. Each payout reports its own status, so your team can see where every payment stands.

What happens when a bank sends a payment back?

The payout moves from COMPLETED to RETURNED. If you release work or credit a ledger on COMPLETED, reverse it on RETURNED.

What does one cross-border payment cost?

Pricing is quoted per contract against your product, use case, volume and rails: a setup fee, a monthly minimum that counts as usage credit, and usage fees. The cost calculator compares one payment on your current provider.

We pay our own suppliers from a company balance. Is this the right page?

This page is about a platform paying recipients on behalf of its customers. If your company moves its own balances, with approvals before money leaves, start with treasury management.

How pricing is quoted

Related

The accounts and balances that fund each payout

Seller payouts inside a marketplace

Paying suppliers from a company treasury with approvals

Where stablecoin settlement replaces SWIFT

Multi-rail settlement

Bring your recipient list

We go through it route by route: what is confirmed for your setup today and what needs confirming first.

Talk to us

Read the documentation

What your ledger records for each recipient

Reconcile on what arrived. A completed bank payout records the fiat amount the provider actually paid, and a payment a bank sends back later reports RETURNED, so your ledger follows the money that reached each recipient.

SOC 2 Type 2 certified. Our own licences are in flight and flows run on licensed partner rails today.