Global Payouts & Pay-ins

Pay out and collect through every rail that matters

One integration — dashboard or API — for SWIFT, SEPA, ACH, Fedwire, RTP, PIX, SPEI and the stablecoin networks. Choose the rail per payment: fastest, cheapest or most familiar.

Rails & Timing

Every corridor, with the clock made explicit

Timing shown is typical for compliant payments; each payout displays its expected window before you confirm.

RailTypeTypical timingBest for
USDC / USDTStablecoinminutesOn-chain settlement, 24/7
RTP / FedNowUS instantinstantUS vendors & payroll
ACHUS batchsame – 2 daysLow-cost US payouts
FedwireUS wiresame dayHigh-value USD
SEPA / InstantEUinstant – 1 dayEUR across EEA
Faster PaymentsUKinstantGBP payouts
PIXBrazilinstantBRL payouts & collections
SPEIMexicoinstantMXN payouts
SWIFTGlobal wire0 – 3 daysLong-tail corridors
FX & Settlement

Convert at quoted rates, settle on your calendar

Lock a rate for immediate (T+0) or forward (T+1/T+2) settlement between fiat and stablecoin. Enterprise flows get quoted pricing per volume band — shown before confirmation, never averaged after the fact.

  • Stablecoin ↔ fiat conversion, T+0 credit
  • Fiat ↔ fiat FX across core corridor list
  • Rate lock at confirmation
  • Per-corridor enterprise pricing

Example: USDC collected in Brazil

1Client pays 100,000 USDT to your wallet
2Auto-rule converts to USD @ quoted rate
3USD credited to your Astro Breeze account, T+0
4Pay out via PIX to local suppliers, instant
What It Costs

One $10,000 payment, three ways

Same supplier, same country, three different plumbing choices. This is why rail selection is a per-payment decision.

Correspondent wire

Local rail via Astro Breeze

On-chain (USDC)

Illustrative market-typical values for comparison, not a quote. Actual pricing is quoted per corridor and volume band before you confirm — and locked at execution.

Daily cut-offs (typical, ET)

Payments missing a cut-off roll to the next window with the new ETA shown — visible, not vanished.

Reliability

When a payout fails, you'll know why

The uncomfortable truth of cross-border payments: things occasionally fail — an account closes, a name mismatch trips a compliance check, a network congests. The difference between infrastructure and a portal is what happens next.

  • Bad account details caught at verification — before money moves
  • Rail-side failures retry automatically, then escalate with a reason code
  • On-chain sends to wrong networks return to your balance
  • Every state change logged: who, what, when — exportable
  • SWIFT GPI corridors report per-bank status where available
Use Cases

Built for real payment operations

Marketplace & platform settlement

Collect from buyers on local rails or stablecoin, settle to sellers in their currency — with reconciliation fields carried end-to-end.

Global contractor & supplier pay

Pay 5 or 5,000 counterparties through the cheapest compliant rail per destination, with approvals on every batch.

Cross-border treasury sweeps

Sweep balances between entities and currencies on schedule, keeping operating floats where they are spent.