Overview
Grid provides two payment methods depending on your use case:Prerequisites
Before sending payments, ensure you have:- An active internal account with sufficient balance
- A verified external account for the destination
- Valid API credentials with appropriate permissions
- A webhook endpoint configured to receive payment status updates (recommended)
Same-Currency Transfers
Use the/transfer-out endpoint when sending funds in the same currency (no exchange rate needed). This is the simplest and fastest option for domestic transfers.
When to use same-currency transfers
- Transferring USD from a USD internal account to a USD external account
- Sending funds within the same country using the same payment rail
- No currency conversion is required
Create a transfer
Get account IDs
Retrieve the internal account (source) and external account (destination) IDs:Note the
id fields from both the internal and external accounts you want to use.Initiate the transfer
Create the transfer by specifying the source and destination accounts:
cURL
Success (201 Created)
The
amount is specified in the smallest unit of the currency (cents for USD, pence for GBP, etc.). For example, 12550 represents $125.50 USD.Track transfer status
The transaction is created with a If a transaction fails, Grid initiates a refund automatically. You’ll receive
PENDING status and progresses through PROCESSING to COMPLETED or FAILED. Monitor the status by:You’ll receive OUTGOING_PAYMENT.<STATUS> webhooks as the transaction progresses. The webhook body contains the full transaction resource:OUTGOING_PAYMENT.REFUND_PENDING followed by OUTGOING_PAYMENT.REFUND_COMPLETED or OUTGOING_PAYMENT.REFUND_FAILED. The transaction’s refund object tracks the refund status and reference.For the full state diagram, refund object details, and all webhook scenarios (including bank returns and manual cancellations), see the Transaction Lifecycle guide.
Transaction statuses
| Status | Description |
|---|---|
PENDING | Transfer initiated and awaiting processing |
EXPIRED | Quote wasn’t executed before the expiry window |
PROCESSING | Transfer in progress through the payment rail |
COMPLETED | Transfer successfully completed |
FAILED | Transfer failed — accompanied by a failureReason |
For the full state diagram including refund tracking and edge cases like bank returns, see the Transaction Lifecycle guide.
Cross-Currency Transfers
Use the quotes flow when sending funds with currency conversion. This locks in an exchange rate and provides all details needed to execute the transfer.When to use cross-currency transfers
- Converting USD to EUR, MXN, BRL, or other supported currencies
- Sending international payments with automatic currency conversion
- Need to lock in a specific exchange rate for the transfer
Create and execute a quote
Create a quote
Request a quote to lock in the exchange rate and get transfer details:
cURL
Success (201 Created)
Locked currency side determines which amount is fixed:
SENDING: Lock the sending amount (receiving amount calculated based on exchange rate)RECEIVING: Lock the receiving amount (sending amount calculated based on exchange rate)
Review quote details
Before executing, review the quote to ensure:
- Exchange rate is acceptable
- Fees are as expected
- Receiving amount meets requirements
- Quote hasn’t expired (check
expiresAt)
Execute the quote
Confirm and execute the quote to initiate the transfer:
cURL
Success (200 OK)
Once executed, the quote creates a transaction and the transfer begins processing. The
transactionId can be used to track the payment.Real-time funding sources: If your quote uses a real-time funding source (USDC, BTC, RTP, or FedNow), you don’t call the execute endpoint. Instead, send a payment to the account specified in the quote’s
paymentInstructions. Grid detects the deposit and processes the transfer automatically.Monitor completion
After execution, a transaction is created and progresses through If a transaction fails, Grid initiates a refund automatically. You’ll receive
PENDING → PROCESSING → COMPLETED or FAILED. You’ll receive OUTGOING_PAYMENT.<STATUS> webhooks as the transaction progresses:OUTGOING_PAYMENT.REFUND_PENDING followed by OUTGOING_PAYMENT.REFUND_COMPLETED or OUTGOING_PAYMENT.REFUND_FAILED. The transaction’s refund object tracks the refund status and reference.For the full state diagram, refund object details, and all webhook scenarios (including bank returns and manual cancellations), see the Transaction Lifecycle guide.
Transaction statuses
| Status | Description |
|---|---|
PENDING | Quote created, awaiting execution |
PROCESSING | Quote executed, transfer in progress |
COMPLETED | Transfer successfully completed |
FAILED | Transfer failed — refund initiated automatically (track via refund object) |
EXPIRED | Quote expired without execution |
Checking Payment Status
Configure a webhook endpoint to receive real-time notifications when payment status changes:Best Practices
Handle quote expiration gracefully
Handle quote expiration gracefully
Quote expiration depends on the corridor (typically ~5 minutes or greater). Always check expiration before executing:
Include descriptive payment references
Include descriptive payment references
Always include meaningful descriptions to help with reconciliation:This makes it easier to match payments in your accounting system and provides context when reviewing transactions.
Store transaction IDs in your system
Store transaction IDs in your system
Always save transaction and quote IDs for audit trails and support: