Payouts to India

This guide covers India-specific requirements for INR payouts. For the general cross-border payment flow, see Sending Cross-Border Payments.

C2C restriction

India payouts support consumer-to-consumer (C2C) only. Business customers and business counterparties are not supported. Both the customer (originator) and counterparty (receiver) must be individuals.

Trading account requirement

India payouts require a USDC_SOL trading account as the source. Other trading account types (such as USDC or USDC_NPL) are not supported for INR payouts.

Verify INR payout availability

Confirm your bank supports INR payouts for C2C and the bank_account route.

ℹ️

Bank configuration required

Contact Cybrid support to enable INR payouts and configure India as a supported corridor for your bank.

GET /api/banks/{bank_guid}
Authorization: Bearer YOUR_TOKEN

Look for an entry in supported_payout_symbols where:

• symbol: INR-USD or INR-USDC_SOL
• country_code: IN
• participants_type: C2C
• route: bank_account

You can also query prices for India:

GET /api/prices?payout_country_code=IN
Authorization: Bearer YOUR_TOKEN

Identity verification requirements

India payouts validate that all required KYC fields are present when you create a plan.

Originator (Customer)

Required fields for the customer (individual):

• name.first, name.last
• date_of_birth
• address.street, address.city, address.country_code

Receiver (Counterparty)

Required fields for the counterparty (individual):

• name.first, name.last

The counterparty must be in verified state (watchlist screening passed) before you can create the external bank account and plan.

Purpose of transaction

For India C2C payouts, purpose_of_transaction is required and restricted to:

• family_support — Personal remittances to family members
• personal_transfer — Personal transfers between individuals

Other purpose values are rejected for India C2C payouts.

External bank account setup

India payouts use IFSC (Indian Financial System Code) routing through India's National Electronic Funds Transfer (NEFT) and Real Time Gross Settlement (RTGS) systems.

Requirements:

• IFSC Code: 11-character bank branch identifier
• Account Number: Beneficiary account number

Send a POST request to /api/external_bank_accounts with the following body:

{
  "account_kind": "raw_routing_details",
  "name": "Indian beneficiary account",
  "counterparty_bank_account_details": [{
    "bank_code_type": "IFSC",
    "bank_code": "HDFC0000123",
    "account_identifier": "012345678901",
    "payment_rail": "IFSC"
  }],
  "counterparty_guid": "counterparty_guid",
  "customer_guid": "customer_guid",
  "asset": "INR"
}

ℹ️

API versioning

Creating external bank accounts with foreign raw routing details requires Accept-Version: 2025-10-01 or later.

For the full account model and field reference, see Create Foreign Fiat External Bank Accounts.

Common validation errors

Related resources

• Sending Cross-Border Payments
• Create Foreign Fiat External Bank Accounts
• Creating a Counterparty
• Verifying a Counterparty
• Create Plan API Reference