GuidesRecipesAPI ReferenceChangelog
Guides

Payouts to India

What are the specific requirements for INR payouts to India?

Review these India-specific requirements before initiating 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.

⚠️

Use a customer-level trading account

For INR remittance plans, only individual customer accounts are supported as the source. Attempting to use a bank-level trading account will result in an error (e.g., invalid_asset or No platform payout symbol configuration found). Use a customer-level trading account when creating remittance plans to India.

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

When you create a plan, the API validates that all required KYC fields are present.

Originator (Customer)

Required fields for the customer (individual):

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

Receiver (Counterparty)

Create an individual counterparty with the standard required fields. This corridor requires no additional counterparty fields beyond the platform defaults.

ℹ️

Counterparty address reflects destination country

For cross-border remittance, the address.city and address.country_code fields for the counterparty should reflect the destination country (e.g., India for INR payouts), not the source country.

⚠️

Self-to-Self remittance (NRE accounts)

When the receiver is the same person as the originator and the destination is a Non-Resident External (NRE) account, create the counterparty using the originator/customer’s non-Indian residential address (the same address on the customer record) — not an India-based address.

The counterparty must be in verified state 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.

Plan expiration

When a plan is created, the response includes an expires_at field (ISO8601 datetime format) indicating when the plan will expire. Once a plan expires, it cannot be executed and attempting to execute it will result in a plan_expired error. The default expiration is 30 seconds.

Common validation errors

Error CodeDescription
invalid_destination_account_exceptionExternal bank account not completed or missing IFSC details
invalid_purpose_of_transactionMissing or invalid purpose value for India
invalid_parameterKYC requirements not met (originator or receiver PII incomplete)
invalid_asset_exceptionBank does not support INR payouts for C2C

Retryable error codes

Only certain remittance errors should be retried automatically. Only external_server_error and market_volatility are valid for automated retries. Other errors, such as invalid_destination or invalid_destination_account_exception, should not be retried automatically and typically indicate an issue with the counterparty or bank account details that must be resolved before attempting again.

Related resources

Updated 11 days ago