Skip to content
Try Sandbox

Move money globally through one API.

Send payments across supported banking, payout and stablecoin rails from one integration. Gravv routes each payment based on its destination.

Get StartedDocumentation

One request. Multiple payment rails.

Keep one payment flow while Gravv routes each supported destination over the right rail.

  1. ACH and wireach_wire
  2. Faster Payments
  3. SEPAsepa
  4. SWIFTswift
  5. Regional railsmobile_money
  6. Stablecoin railscrypto_wallet
Payment requestRoutingDestination types

You choose who gets paid. Gravv handles the route.

Save the destination once. Gravv validates the required details, selects the supported path and returns payment status.

  1. Save destinationStore the recipient or account details once.
  2. Verify and routeValidate the required information and determine the supported payment path.
  3. Send and trackCreate the payment and follow its status through completion.
A Gravv payments screen: a Send-to list of saved recipients across bank accounts, local payment networks and wallets.

One payment object across supported destinations.

Bank account or supported wallet, the core request stays the same. Change the destination, not the integration.

POST /v1/transfer
{
  "amount": "1200.00",
  "source_currency": "USD",
  "destination": {
    "type": "external_account",
    "external_account_id": "ext_…"
  },
  "reference": "INV-4471"
}

Pay whoever your product needs to pay.

Use the same payment flow for customer payouts, suppliers, contractors, partners and treasury movement.

  • Customers

    Pay out to the people who use your product.

  • Suppliers

    Settle invoices with the businesses you buy from.

  • Contractors

    Pay individuals working with you across markets.

  • Partners

    Move agreed amounts to the partners you operate with.

  • Treasury

    Move your own funds between the balances you hold.

Your productGravvCustomersSuppliersContractorsPartnersTreasuryYour productGravvCustomersSuppliersContractorsPartnersTreasury

Coverage and rails

Every payment is checked before it moves.

Recipient details, available funds and required controls are validated before execution.

  • Recipient validation

    Recipient details and duplicate protection are checked before the payment is accepted.

  • Funds and limits

    The payment names the balance it draws on, and available funds and limits are validated before execution.

  • Payment controls

    Supported destinations are read back from the API, and an Idempotency-Key means a retry returns the original payment.

Trust and security

Payments connect to the rest of Gravv.

Fund from accounts, collect first, convert with FX, or settle through supported stablecoin rails.

Start where you are