Typed rail registry
The public list ships from a typed code registry. Procurement sees exactly what Gruv names as a rail category and its current status.
Rail disclosure
Payment rails and currency coverage
Gruv publishes rail coverage by method, currency, region, and rollout status. Use this table for RFP responses, procurement evaluation, and launch planning across ACH, SEPA, SWIFT, local bank transfer, wallet, card, and crypto corridors.
Registry snapshot
v19
Rail categories
1
Code-routed
3
Coverage review
1
Feature gated
Status legend
- Code-routed — Routing logic is pinned in code for the named corridors.
- Coverage review — Rail exists; corridor-level approval gates activation.
- Feature gated — Requires tenant policy and explicit eligibility.
- Partner onboarding — Capability in alpha, not generally available.
Corridor-scoped coverage
Each rail requires customer, payee, country, currency, and partner approval before activation for a given corridor.
No sensitive details exposed
This page discloses rail categories and currency bands. Partner identities, live bank details, card data, and wallet addresses are never shown here.
Current registry
Rail-by-rail disclosure
Status labels distinguish code-routed corridors from rails still pending partner onboarding, tenant policy, or launch review. Treat a rail as customer-available only after review completes.
ACH and U.S. bank transfer
Coverage reviewU.S. domestic bank-transfer instructions and payout routing for approved customer programs.
- Direction
- Collections and payouts
- Currencies
- USD
- Region
- United States
Account details, cutoff times, return handling, and debit/credit behavior vary by partner and program approval.
SEPA and Euro IBAN
Coverage reviewEUR bank-transfer instructions routed to approved licensed partners for payout execution.
- Direction
- Collections and payouts
- Currencies
- EUR
- Region
- SEPA area
IBAN issuance, reach, name requirements, and refund/return rules are confirmed per rollout.
UK local bank transfer
Coverage reviewGBP local receiving and payout routes, including sort-code bank details for approved partner programs.
- Direction
- Collections and payouts
- Currencies
- GBP
- Region
- United Kingdom
Settlement timing, account-name requirements, and same-day availability are partner and program specific.
SWIFT and international wire
Partner onboardingInternational bank-transfer fallback for corridors where local methods are unavailable or pending approval.
- Direction
- Collections and payouts
- Currencies
- Partner-enabled ISO-3 currencies
- Region
- Cross-border corridors
Intermediary fees, receiving-bank requirements, FX quote availability, and repair handling require review before launch.
LATAM local bank transfer
Code-routedLocal-bank payout corridors in BRL, MXN, COP, ARS, CLP, and PEN with country-specific bank metadata.
- Direction
- Payouts
- Currencies
- BRL, MXN, COP, ARS, CLP, PEN
- Region
- Brazil, Mexico, Colombia, Argentina, Chile, Peru
USD-to-local-currency payout corridors are pinned to a dedicated partner. No alternate failover by default.
Real-time U.S. consumer disbursement
Alpha partnerU.S. B2C payout using recipient email or phone alias with recipient-name metadata.
- Direction
- Payouts
- Currencies
- USD
- Region
- United States
Payouts run on a dedicated path enforcing USD. No automatic bank-transfer failover.
Push-to-card
Alpha partnerCard payout execution through approved push-to-card programs for networks with completed onboarding.
- Direction
- Payouts
- Currencies
- Network and partner-enabled currencies
- Region
- Program-approved card networks
Card data must remain in approved partner or tokenized flows. Network membership, mTLS, and program credentials are prerequisites.
Digital wallet payouts
Alpha partnerWallet payouts routed when the beneficiary record and tenant policy select that method.
- Direction
- Payouts
- Currencies
- Partner and wallet-enabled currencies
- Region
- Partner-approved wallet markets
Wallet payouts use explicit partner priority. No failover to bank payouts unless the rollout configures it.
USDT crypto rail
Feature gatedUSDT checkout and payout routing through an approved partner. Gruv retains fiat accounting with no custodial USDT balance.
- Direction
- Collections and payouts
- Currencies
- Fiat invoices and ledger; USDT delivered by the partner
- Region
- Policy-allowed crypto corridors
USDT requires tenant policy, feature flags, eligibility checks, and partner approval. It is not a default payout method.
Review inputs
What we need from you to confirm a corridor.
- Launch countries and payer or payee entity types
- Required collection and payout directions
- Invoice, payout, and settlement currencies
- Preferred bank, card, wallet, or crypto rail
- Expected transaction size, frequency, cutoff, and return handling
- Compliance, tax, procurement, and support evidence requirements
Disclosure limits
What this page does — and does not — promise.
- A listed method is not a promise that every customer, payee, or country can use it immediately.
- Partner 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.
Next step
Have a corridor to validate?
Share your launch countries, directions, currencies, and expected flow. We'll confirm rail availability, surface status, and outline what's left before activation.