API Test Keys

Create a Fund Account for Externally Tokenised Card

POST
/v1/fund_accounts

Click to copy

Use this endpoint to create a fund account type card by saving the card as an external token.

Is this page helpful?

Curl

1
curl -u <YOUR_KEY>:<YOUR_SECRET> \
2
-X POST https://api.razorpay.com/v1/fund_accounts \
3
-H "Content-Type: application/json" \
4
-d '{
5
"contact_id": "cont_00000000000001",
6
"account_type": "card",
7
"card": {
8
"number": "4854980604708430",
9
"expiry_month": "12",
10
"expiry_year": "21",
11
"token_provider": "payu",
12
"input_type": "service_provider_token"
13
}
14
}'

Success

1
{
2
"id": "fa_00000000000001",
3
"entity": "fund_account",
4
"contact_id": "cont_00000000000001",
5
"account_type": "card",
6
"card": {
7
"last4": "8430",
8
"network": "Visa",
9
"type": "credit",
10
"issuer": "HDFC",
11
"input_type": "service_provider_token",
12
},
13
"active": true,
14
"batch_id": null,
15
"created_at": 1543650891
16
}
Request Parameters
contact_id

*

string

The unique identifier of the contact for which you want to fetch payouts. For example, cont_00000000000001.

account_type

*

string

The type of account linked to the contact id. Here, it will be card.

card

*

object

The details of the card used.

Show child parameters (5)

Response Parameters
id
string

The unique identifier linked to the payout. For example, pout_00000000000001.

entity
string

The entity being created. For example, payout.

fund_account_id
string

The unique identifier linked to the fund account. For example, fa_00000000000001.

fund_account
object

The account to which you want to make the payout.

Show child parameters (5)

amount
integer

The payout amount, in paise. For example, if you want to transfer ₹10,000, pass 1000000. Minimum value 100.

The value passed here does not include fees and tax. Fees and tax, if any, are deducted from your account balance.

currency
string

The payout currency. Here, it is INR.

notes
array of objects

Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.

fees
integer

The fees for the payout. This value is returned only when the payout moves to the processing state. For example, 5.

tax
integer

The tax that is applicable for the fee being charged. This value is returned only when the payout moves to the processing state. For example, 1.

status
string

The status of the payout. Possible payout states:

purpose
string

The purpose of the payout that is being created. The following classifications are available in the system by default:

  • refund
  • cashback
  • payout
  • salary
  • utility bill
  • vendor bill

utr
string

The unique transaction number linked to a payout. For example, HDFCN00000000001.

mode
string

The mode used to make the payout. Available modes:

  • NEFT
  • RTGS
  • IMPS
  • UPI
  • card

The payout modes are case-sensitive.

reference_id
string

Maximum length is 40 characters. A user-generated reference given to the payout. For example, Acme Transaction ID 12345. You can use this field to store your own transaction ID, if any.

narration
string

Maximum length 30 characters. Allowed characters: a-z, A-Z, 0-9 and space. This is a custom note that also appears on the bank statement. If no value is passed for this parameter, it defaults to the Merchant Billing Label.

Enter the important text in the first 9 characters as banks truncate the rest as per their standards.

batch_id
string

This value is returned if the contact was created as part of a bulk upload. For example, batch_00000000000001.

status_details
object

This parameter returns the current status of the payout. For example, IMPS is not enabled on beneficiary account, Retry with different mode.

Show child parameters (3)

created_at
integer

Timestamp, in Unix, when the contact was created. For example, 1545320320.

fee_type
string

Indicates the fee type charged for the payout. Possible value is free_payout.

Create a Fund Account for Externally Tokenised Card

POST
/v1/fund_accounts

Click to copy

Use this endpoint to create a fund account type card by saving the card as an external token.

Is this page helpful?

Request Parameters
contact_id

*

string

The unique identifier of the contact for which you want to fetch payouts. For example, cont_00000000000001.

account_type

*

string

The type of account linked to the contact id. Here, it will be card.

card

*

object

The details of the card used.

Show child parameters (5)

Response Parameters
id
string

The unique identifier linked to the payout. For example, pout_00000000000001.

entity
string

The entity being created. For example, payout.

fund_account_id
string

The unique identifier linked to the fund account. For example, fa_00000000000001.

fund_account
object

The account to which you want to make the payout.

Show child parameters (5)

amount
integer

The payout amount, in paise. For example, if you want to transfer ₹10,000, pass 1000000. Minimum value 100.

The value passed here does not include fees and tax. Fees and tax, if any, are deducted from your account balance.

currency
string

The payout currency. Here, it is INR.

notes
array of objects

Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.

fees
integer

The fees for the payout. This value is returned only when the payout moves to the processing state. For example, 5.

tax
integer

The tax that is applicable for the fee being charged. This value is returned only when the payout moves to the processing state. For example, 1.

status
string

The status of the payout. Possible payout states:

purpose
string

The purpose of the payout that is being created. The following classifications are available in the system by default:

  • refund
  • cashback
  • payout
  • salary
  • utility bill
  • vendor bill

utr
string

The unique transaction number linked to a payout. For example, HDFCN00000000001.

mode
string

The mode used to make the payout. Available modes:

  • NEFT
  • RTGS
  • IMPS
  • UPI
  • card

The payout modes are case-sensitive.

reference_id
string

Maximum length is 40 characters. A user-generated reference given to the payout. For example, Acme Transaction ID 12345. You can use this field to store your own transaction ID, if any.

narration
string

Maximum length 30 characters. Allowed characters: a-z, A-Z, 0-9 and space. This is a custom note that also appears on the bank statement. If no value is passed for this parameter, it defaults to the Merchant Billing Label.

Enter the important text in the first 9 characters as banks truncate the rest as per their standards.

batch_id
string

This value is returned if the contact was created as part of a bulk upload. For example, batch_00000000000001.

status_details
object

This parameter returns the current status of the payout. For example, IMPS is not enabled on beneficiary account, Retry with different mode.

Show child parameters (3)

created_at
integer

Timestamp, in Unix, when the contact was created. For example, 1545320320.

fee_type
string

Indicates the fee type charged for the payout. Possible value is free_payout.

Curl

1
curl -u <YOUR_KEY>:<YOUR_SECRET> \
2
-X POST https://api.razorpay.com/v1/fund_accounts \
3
-H "Content-Type: application/json" \
4
-d '{
5
"contact_id": "cont_00000000000001",
6
"account_type": "card",
7
"card": {
8
"number": "4854980604708430",
9
"expiry_month": "12",
10
"expiry_year": "21",
11
"token_provider": "payu",
12
"input_type": "service_provider_token"
13
}
14
}'

Success

1
{
2
"id": "fa_00000000000001",
3
"entity": "fund_account",
4
"contact_id": "cont_00000000000001",
5
"account_type": "card",
6
"card": {
7
"last4": "8430",
8
"network": "Visa",
9
"type": "credit",
10
"issuer": "HDFC",
11
"input_type": "service_provider_token",
12
},
13
"active": true,
14
"batch_id": null,
15
"created_at": 1543650891
16
}