Modify Settlement Hold for Transfers
PATCH/v1/transfers/:idClick to copy
Use this endpoint to modify the settlement configuration for a particular transfer_id. On a successful request, the API responds with the modified transfer entity.
Is this page helpful?
Curl
change language
change language
1curl -X PATCH https://api.razorpay.com/v1/transfers/trf_JJD536GI6wuz3m \2-u [YOUR_KEY_ID]:[YOUR_KEY_SECRET] \3-H 'content-type: application/json' \4-d '{5"on_hold": true,6"on_hold_until": 16796915057}'
Success
Failure
1{2"id": "trf_JJD536GI6wuz3m",3"entity": "transfer",4"status": "processed",5"source": "pay_JGmCgTEa9OTQcX",6"recipient": "acc_IRQWUleX4BqvYn",7"amount": 300,8"currency": "MYR",9"amount_reversed": 0,10"fees": 1,11"tax": 0,12"notes": {13"name": "Nur Aisyah",14"roll_no": "IEC2011026"15},16"linked_account_notes": [17"roll_no"18],19"on_hold": true,20"on_hold_until": 1649971331,21"settlement_status": "on_hold",22"recipient_settlement_id": null,23"created_at": 1649933574,24"processed_at": 1649933579,25"error": {26"code": null,27"description": null,28"reason": null,29"field": null,30"step": null,31"id": "trf_JJD536GI6wuz3m",32"source": null,33"metadata": null34}35}
Path Parameters
id *
stringUnique identifier of the transfer for which settlement configurations should be modified.
Request Parameters
on_hold *
booleanIndicates whether the account settlement for transfer is on hold. Possible values:
true: Put the transfer settlement on hold.false: Releases the settlement.
For example, if the settlement schedule is T+10 days, a transfer made withon_holdset to true will not be settled even after 10 days, as it is on hold. If the hold is disabled onT+15day, the amount will be settled to the Linked Account by the next working day.
on_hold_until integer Timestamp, in Unix, that indicates until when the settlement of the transfer must be put on hold. If no value is passed, the settlement is put on hold indefinitely. For example, if a transfer is created with on_hold_until timestamp defined as 1583991784, the settlement will be held off until the specified time period. The amount will be settled to the Linked Account only on the next day.
Response Parameters
idstringUnique identifier of the transfer.
entitystring The name of the entity. Here, it is transfer.
transfer_statusstringThe status of the transfer. Possible values are:
createdpendingprocessedfailedreversedpartially_reversed
settlement_statusstringThe status of the settlement. Possible values are:
pendingon_holdsettled
sourcestring Unique identifier of the transfer source. The source can be a payment or an order.
recipientstringUnique identifier of the transfer destination, that is, the Linked Account.
amountintegerThe amount to be transferred to the Linked Account, in sen. For example, for an amount of RM200.35, the value of this field should be 20035.
currencystring ISO currency code. We support route transfers only in MYR.
amount_reversedintegerAmount reversed from this transfer for refunds.
notesjson objectSet of key-value pairs that can be associated with an entity. These pairs can be useful for storing additional information about the entity. A maximum of 15 key-value pairs, each of 256 characters (maximum), are supported.
errorstringProvides error details that may occur during transfers.
Show child parameters (7)
linked_account_notesarray List of keys from the notes object which needs to be shown to Linked Accounts on their Dashboard. For example, "region", "city". Only the keys will be shown, not values.
on_holdbooleanIndicates whether the account settlement for transfer is on hold. Possible values:
true: Puts the settlement on hold.false: Releases the settlement.
on_hold_untilintegerTimestamp, in Unix format, indicates until when the settlement of the transfer must be put on hold. If no value is passed, the settlement is put on hold indefinitely.
recipient_settlement_idstringUnique identifier of the settlement.
created_atintegerTimestamp, in Unix, at which the record was created.
Errors
The api key/secret provided is invalid
Error Status: 4xx
This error occurs when there is a mismatch between the API credentials passed in the API call and the API credentials generated on the Dashboard.
Solution
The amount must be atleast MYR 1.00
Error Status: 400
This error occurs when the amount is less than the minimum amount. The transaction amount expressed in the currency subunit, such as sen (in MYR) should always be greater than or equal to RM1.
Solution
transfer_id is not a valid id
Error Status: 400
This error occurs when you pass an invalid transfer_id in the API endpoint.
Solution
Modify Settlement Hold for Transfers
PATCH/v1/transfers/:idClick to copy
Use this endpoint to modify the settlement configuration for a particular transfer_id. On a successful request, the API responds with the modified transfer entity.
Is this page helpful?
Path Parameters
id *
stringUnique identifier of the transfer for which settlement configurations should be modified.
Request Parameters
on_hold *
booleanIndicates whether the account settlement for transfer is on hold. Possible values:
true: Put the transfer settlement on hold.false: Releases the settlement.
For example, if the settlement schedule is T+10 days, a transfer made withon_holdset to true will not be settled even after 10 days, as it is on hold. If the hold is disabled onT+15day, the amount will be settled to the Linked Account by the next working day.
on_hold_until integer Timestamp, in Unix, that indicates until when the settlement of the transfer must be put on hold. If no value is passed, the settlement is put on hold indefinitely. For example, if a transfer is created with on_hold_until timestamp defined as 1583991784, the settlement will be held off until the specified time period. The amount will be settled to the Linked Account only on the next day.
Response Parameters
idstringUnique identifier of the transfer.
entitystring The name of the entity. Here, it is transfer.
transfer_statusstringThe status of the transfer. Possible values are:
createdpendingprocessedfailedreversedpartially_reversed
settlement_statusstringThe status of the settlement. Possible values are:
pendingon_holdsettled
sourcestring Unique identifier of the transfer source. The source can be a payment or an order.
recipientstringUnique identifier of the transfer destination, that is, the Linked Account.
amountintegerThe amount to be transferred to the Linked Account, in sen. For example, for an amount of RM200.35, the value of this field should be 20035.
currencystring ISO currency code. We support route transfers only in MYR.
amount_reversedintegerAmount reversed from this transfer for refunds.
notesjson objectSet of key-value pairs that can be associated with an entity. These pairs can be useful for storing additional information about the entity. A maximum of 15 key-value pairs, each of 256 characters (maximum), are supported.
errorstringProvides error details that may occur during transfers.
Show child parameters (7)
linked_account_notesarray List of keys from the notes object which needs to be shown to Linked Accounts on their Dashboard. For example, "region", "city". Only the keys will be shown, not values.
on_holdbooleanIndicates whether the account settlement for transfer is on hold. Possible values:
true: Puts the settlement on hold.false: Releases the settlement.
on_hold_untilintegerTimestamp, in Unix format, indicates until when the settlement of the transfer must be put on hold. If no value is passed, the settlement is put on hold indefinitely.
recipient_settlement_idstringUnique identifier of the settlement.
created_atintegerTimestamp, in Unix, at which the record was created.
Errors
The api key/secret provided is invalid
Error Status: 4xx
This error occurs when there is a mismatch between the API credentials passed in the API call and the API credentials generated on the Dashboard.
Solution
The amount must be atleast MYR 1.00
Error Status: 400
This error occurs when the amount is less than the minimum amount. The transaction amount expressed in the currency subunit, such as sen (in MYR) should always be greater than or equal to RM1.
Solution
transfer_id is not a valid id
Error Status: 400
This error occurs when you pass an invalid transfer_id in the API endpoint.
Solution
Curl
change language
change language
1curl -X PATCH https://api.razorpay.com/v1/transfers/trf_JJD536GI6wuz3m \2-u [YOUR_KEY_ID]:[YOUR_KEY_SECRET] \3-H 'content-type: application/json' \4-d '{5"on_hold": true,6"on_hold_until": 16796915057}'
Success
Failure
1{2"id": "trf_JJD536GI6wuz3m",3"entity": "transfer",4"status": "processed",5"source": "pay_JGmCgTEa9OTQcX",6"recipient": "acc_IRQWUleX4BqvYn",7"amount": 300,8"currency": "MYR",9"amount_reversed": 0,10"fees": 1,11"tax": 0,12"notes": {13"name": "Nur Aisyah",14"roll_no": "IEC2011026"15},16"linked_account_notes": [17"roll_no"18],19"on_hold": true,20"on_hold_until": 1649971331,21"settlement_status": "on_hold",22"recipient_settlement_id": null,23"created_at": 1649933574,24"processed_at": 1649933579,25"error": {26"code": null,27"description": null,28"reason": null,29"field": null,30"step": null,31"id": "trf_JJD536GI6wuz3m",32"source": null,33"metadata": null34}35}