Rail registry in code
The public list is driven from a typed registry so procurement review can see what Gruv actually names as a rail category.
Rail disclosure
Payment rails and currency coverage
Gruv publishes rail coverage as method, currency, provider, and rollout-status information. The table is meant for RFP, procurement, and launch planning before a customer asks teams to rely on a specific ACH, SEPA, SWIFT, local, wallet, card, or crypto route.
Coverage is corridor scoped
Each rail still needs customer, payee, country, currency, and provider approval before it can be enabled for a rollout.
Sensitive details stay out
This page discloses rail categories and currency bands, not live bank details, card data, or wallet addresses.
Current registry
Rail-by-rail currency disclosure
Status labels separate code-routed corridors from rails that still need provider onboarding, tenant policy, or launch review. A rail should be treated as available for a customer only after that review is complete.
| Rail | Direction | Currencies | Region | Providers | Status |
|---|---|---|---|---|---|
ACH and U.S. bank transferU.S. domestic bank-transfer instructions and payout routing where the customer program has provider coverage. | Collections and payouts | USD | United States | Nium, Tazapay, Currencycloud, Airwallex | Coverage review Final account details, cutoff times, return handling, and debit or credit behavior depend on the provider and program approval. |
SEPA and Euro IBANEuro bank-transfer instructions and payout execution through enabled bank-transfer providers. | Collections and payouts | EUR | SEPA area | Airwallex, Currencycloud, Tazapay | Coverage review IBAN issuance, SEPA reach, name requirements, and refund or return rules are confirmed per rollout. |
UK local bank transferGBP local receiving and payout routes, including sort-code style bank details where provider coverage is approved. | Collections and payouts | GBP | United Kingdom | Airwallex, Currencycloud, Tazapay | Coverage review Faster Payments, CHAPS, account-name requirements, and payout settlement timing are provider and program specific. |
SWIFT and international wireInternational bank-transfer fallback for corridors where local rails are unavailable or not yet approved. | Collections and payouts | Provider-enabled ISO-3 currencies | Cross-border corridors | Tazapay, Airwallex, Currencycloud, Nium, Payoneer | Provider onboarding Intermediary fees, receiving-bank requirements, FX quote availability, and repair handling must be reviewed before launch. |
LATAM local bank transferLocal-bank payout corridors routed to dLocal, including country-specific bank metadata and document requirements. | Payouts | BRL, MXN, COP, ARS, CLP, PEN | Brazil, Mexico, Colombia, Argentina, Chile, Peru | dLocal | Code-routed The routing layer pins these USD to local-currency payout corridors to dLocal instead of defaulting to a bank-provider fallback. |
Zelle disbursementU.S. B2C payout rail using recipient email or phone alias plus recipient-name metadata. | Payouts | USD | United States | Zelle bank API adapter | Alpha provider The payout controller enforces USD and keeps Zelle requests on the Zelle rail without bank-provider failover. |
Push-to-cardCard payout execution through Visa Direct, Mastercard Send, or Amex where network onboarding is complete. | Payouts | Network and provider-enabled currencies | Program-approved card networks | Card payouts adapter | Alpha provider Card data must remain in approved provider or tokenized flows. Network membership, mTLS, and program credentials are prerequisites. |
PayPal, Venmo, Skrill, and NetellerWallet payout options routed to dedicated providers when the beneficiary record and tenant policy select that rail. | Payouts | Provider and wallet-enabled currencies; Venmo uses USD | Provider-approved wallet markets | PayPal, Paysafe | Alpha provider Dedicated wallet rails use explicit provider priority so they do not fail over to bank payouts unless a rollout intentionally configures that behavior. |
USDT crypto railUSDT checkout and payout routing through Triple-A, with Gruv retaining fiat accounting and no custodial USDT balance. | Collections and payouts | Fiat invoices and ledger; USDT delivered by the provider | Policy-allowed crypto corridors | Triple-A | Feature gated USDT usage requires tenant policy, feature flags, explicit eligibility checks, and provider approval. It is not a default payout rail. |
Review inputs
- Launch countries and payer or payee entity types
- Required collection and payout directions
- Invoice, payout, and settlement currencies
- Preferred provider, bank, card, wallet, or crypto rail
- Expected transaction size, frequency, cutoff, and return handling
- Compliance, tax, procurement, and support evidence requirements
Disclosure limits
- A listed rail is not a promise that every customer, payee, or country can use it immediately.
- Provider onboarding, tenant policy, sanctions screening, KYC or KYB, tax holds, and local law can limit availability.
- Currency support means operational routing can evaluate that currency. Fees, delivery timing, and settlement finality still require corridor review.
- Gruv does not publish raw bank details, card data, or wallet addresses on this page.
Code references
Evidence used for this registry
Each rail entry carries code or repo-doc references so the list can be checked during engineering review without relying on a sales-only coverage table.
ACH and U.S. bank transfer
- payments-service/apps/virtual-accounts/README.md
- payments-service/apps/provider-nium/README.md
- payments-service/apps/provider-tazapay/README.md
- payments-service/apps/provider-currencycloud/README.md
SEPA and Euro IBAN
- payments-service/apps/virtual-accounts/README.md
- payments-service/apps/provider-airwallex/README.md
- payments-service/apps/provider-currencycloud/README.md
- payments-service/apps/provider-tazapay/README.md
UK local bank transfer
- gruv-home/apps/web/src/components/virtual-accounts/GlobalReach.tsx
- payments-service/apps/virtual-accounts/README.md
- payments-service/apps/provider-airwallex/README.md
- payments-service/apps/provider-currencycloud/README.md
SWIFT and international wire
- payments-service/apps/payments-gateway/src/routing/routing.service.ts
- payments-service/apps/provider-tazapay/README.md
- payments-service/apps/provider-airwallex/README.md
- payments-service/apps/provider-currencycloud/README.md
- payments-service/apps/provider-payoneer/README.md
LATAM local bank transfer
- payments-service/apps/payments-gateway/src/routing/routing.service.ts
- payments-service/apps/provider-dlocal/README.md
Zelle disbursement
- payments-service/apps/payments-gateway/src/orbit/controllers/payouts.controller.ts
- payments-service/apps/provider-zelle/README.md
Push-to-card
- payments-service/apps/provider-card-payouts/README.md
- payments-service/apps/payments-gateway/src/orbit/controllers/payouts.controller.ts
PayPal, Venmo, Skrill, and Neteller
- payments-service/apps/provider-paypal/README.md
- payments-service/apps/provider-paysafe/README.md
- payments-service/apps/payments-gateway/src/orbit/controllers/payouts.controller.ts
USDT crypto rail
- payments-service/apps/provider-triplea/README.md
- payments-service/docs/provider-triplea-plan.md
- platform-backend/docs/usdt-invoices-triplea-plan.md