Initiate Batch Transfer

📌

Use this API to initiate a batch transfer request from your EnKash Payments account. This allows you to transfer funds to multiple beneficiaries simultaneously, streamlining bulk payouts and reducing manual effort.

Batch transfers are ideal for scenarios like vendor payments, employee disbursements, or large-scale customer refunds.

Batch Payout Create Request

batchTransactionId

string

required

This signifies the unique identifier you create to distinguish the batch transfer request.

transfers

array[object (PayoutTransactionCreateRequest) {10}]

required

beneficiaryId

string

optional

It is the unique ID you created to identify the beneficiary.

transactionId

string

required

It is the unique ID you create to identify the transfer.

transferAmount

number

required

This represents the transfer amount, where decimal values are permitted. The minimum value must be equal to or greater than 1.00

transferMode

enum<string>

required

This denotes the transfer method. Permitted values include IMPS, NEFT, RTGS & UPI. The default transfer mode is NEFT.

Allowed values:

IMPSNEFTRTGSUPI

transferRemark

string

optional

This field allows for any additional remarks regarding the transfer. Alphanumeric characters and whitespaces are permitted.

reference

string

optional

This is unique reference that you can pass in request.

fundSourceId

string

required

This represents the ID of the fund source from which the transfer amount will be debited.

beneficiaryDetail

object (BeneficiaryDetailCreateRequest)

optional

checksum

string

optional

This is checksum generated by you as per steps given in document.

debitAccountNumber

string

optional

This is mandatory for connected banking payouts

Batch Payout Create Response

batchTransactionId

string

optional

This signifies the unique identifier you created to distinguish the batch transfer request.

successfulPayoutTransactionCreateResponses

array[object (PayoutTransactionCreateResponse) {6}]

optional

List of successful transactions

transactionId

string

optional

It is the unique ID you created to identify the transfer.

enkashTransactionId

string

optional

This is unique id generated by EnKash to identify payout

payoutStatus

enum<string>

optional

This field displays the status of the transfer.

Allowed values:

SUCCESSFAILEDPENDINGIN_PROGRESSPAIDON_HOLDNEFT_CALL_MADEIMPS_CALL_MADEREINITIATEAGENCY_PENDINGAX_BBPS_SUCCESSPG_SETTLEMENT_PENDINGUPI_CALL_MADE

createdOn

string <date-time>

optional

This field displays the time when the transfer request was added to the system.

modifiedOn

string <date-time>

optional

This field displays the updated time for the transfer.

failureReason

string

optional

This field displays the failure reason if any

failedPayoutTransactionCreateResponses

array[object (PayoutTransactionCreateResponse) {6}]

optional

List of failed transactions

transactionId

string

optional

It is the unique ID you created to identify the transfer.

enkashTransactionId

string

optional

This is unique id generated by EnKash to identify payout

payoutStatus

enum<string>

optional

This field displays the status of the transfer.

Allowed values:

SUCCESSFAILEDPENDINGIN_PROGRESSPAIDON_HOLDNEFT_CALL_MADEIMPS_CALL_MADEREINITIATEAGENCY_PENDINGAX_BBPS_SUCCESSPG_SETTLEMENT_PENDINGUPI_CALL_MADE

createdOn

string <date-time>

optional

This field displays the time when the transfer request was added to the system.

modifiedOn

string <date-time>

optional

This field displays the updated time for the transfer.

failureReason

string

optional

This field displays the failure reason if any

status

string

optional

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

application/json

Body

response_code

integer <int32>

optional

response_message

string

optional

payload

string

optional

Example

{
    "response_code": 0,
    "response_message": "string",
    "payload": "string"
}

Request

Request samples

Responses