Scheduling single/multiple debit requests
To view error codes, click here
Scheduling single/multiple debit requests
To view error codes, click here
Getting started with Digio Rest Apis
|
HTTP Basic
Send
Authorization in header containing the word Basic followed by a space and a base64 encoded string of username:password.
|
This API is used to create schedule plan for a single UMRN
{
"umrn": "string",
"settlement_date": "1970-01-01T00:00:00.000Z",
"corporate_account_number": "AAAAAAAA",
"settlement_config_profile_id": "string",
"amount_in_paise": 0,
"amount": 0,
"narration": "A",
"unique_key": "",
"sub_user_identifier": "string",
"split_settlement_info": [
{
"settlement_account_number": "string",
"split_amount_in_paise": 0
}
],
"frequency": "ONETIME",
"payment_count": 1,
"optional_attr": {
"member_id": "string",
"client_id": "string",
"pg_bank_ref_number": "string",
"order_id": "",
"txn_type": "string"
},
"upi_mandate_extended_detail": {
"id": "string",
"umrn": "string",
"ownerId": "string",
"customerRefNumber": "string",
"customerVpa": "string",
"customerName": "string",
"schemeRefNumber": "string",
"partnerBank": "KOTAK",
"frequency": "ADHO",
"corporateConfigId": "string",
"status": "authenticated",
"mandateStartDate": "1970-01-01T00:00:00.000Z",
"mandateEndDate": "1970-01-01T00:00:00.000Z",
"amount": 0,
"amountType": "fixed",
"digioEnachId": "string",
"identifier": "string",
"sponsorBankCode": "KOTAK",
"authenticationTime": "1970-01-01T00:00:00.000Z",
"narration": "string",
"destinationBankIfsc": "string",
"mandateRequestId": "string",
"serviceProviderName": "string",
"statusUpdatedAt": "1970-01-01T00:00:00.000Z",
"customerAccountNumber": "string",
"customerAccountType": "savings",
"merchantCategoryCode": "string",
"subUserId": "string"
}
}
Mandate UMRN created upon successful registration of Mandate
Date for Settlement in yyyy-mm-dd hh:mm:ss
Default: (i) first_collection_date as provided in registered mandate OR (ii) current date Note : Settlement Date should be more than 26 hours from current time
âž” Any one of corporate_account_number or settlement_config_profile_id or split_settlement_info is required. All numeric
Config of settlement, if already predefined. Any one of corporate_account_number or settlement_config_profile_id or split_settlement_info is required.
Either of amount or amount_in_paise is mandatory
Either of amount or amount_in_paise is mandatory.
âž” Default: Enterprise name
➔ To be used for Corporate’s reference.
Default:
Set value to assign it to a sub-user
âž” Any one of corporate_account_number or settlement_config_profile_id or split_settlement_info is required.
Min Items: 2 Max Items: 10 ⮕ [ Any one of corporate_account_number or settlement_config_profile_id or split_settlement_info is required. ]
Bank Account Number
Amount to be settled in paise
âž”
âž” Should be non-negative and >= 1. payment_count has to be one if frequency is ONETIME
Please refer below for the additional attributes, that should only be passed by Mutual Fund use case customers
Member ID for whom the PA/ Bank is uploading the file
UCC for the said Client.
Unique reference number provided by the member for payment to be collected for a unique client.
âž” Pass the Order Number for this SIP order
Type of transaction
âž”
âž”
âž”
âž”
âž”
âž”
Unique identifier for the UPI scheduled plan
Unique Mandate Reference Number for the scheduled plan
âž” Current status of the scheduled payment
List of all transactions for the specific UPI schedule plan
Unique identifier for the transaction
UMRN associated with the transaction
âž” State of the transaction
Creation timestamp of the transaction
Update timestamp of the transaction
Timestamp when the transaction status was last updated
Name of the customer
Unique ID of the customer
Detailed information about the UPI transaction
âž” Status of the NACH payment transaction
Transaction amount in standard currency units
Transaction amount in the smallest currency units (e.g., paise)
Identifier for the sponsor bank
Timestamp indicating when the transaction is ready to be processed
Code indicating the reason for transaction failure, if applicable
Description of the reason for transaction failure, if applicable
Virtual Payment Address of the customer, if applicable
âž” Type of the transaction
Reference number for the transaction
Unique Transaction Reference number for the transaction
Description of the settlement
Name of the settlement bank account
Total amount to be settled
First tax amount deducted from the settlement
Second tax amount deducted from the settlement
Third tax amount deducted from the settlement
First fee amount deducted from the settlement
Second fee amount deducted from the settlement
Final amount after taxes and fees have been deducted
âž” Status of the external settlement
Consolidation identifier for the settlement
Bank transaction reference for the settlement
Account number associated with the settlement
Digio's unique transaction reference number
Date of settlement for the transaction
Identifier of the parent transaction, if any
List of details for each settlement transaction
Transaction ID of the debit transaction
Amount in paise of the debit transaction
Account number associated with the transaction
Unique Reference Number for the settlement
Date and time when the settlement was processed
List of all transactions for the specific UPI schedule plan
Unique identifier for the transaction
UMRN associated with the transaction
âž” State of the transaction
Creation timestamp of the transaction
Update timestamp of the transaction
Timestamp when the transaction status was last updated
Name of the customer
Unique ID of the customer
Detailed information about the UPI transaction
âž” Status of the NACH payment transaction
Transaction amount in standard currency units
Transaction amount in the smallest currency units (e.g., paise)
Identifier for the sponsor bank
Timestamp indicating when the transaction is ready to be processed
Code indicating the reason for transaction failure, if applicable
Description of the reason for transaction failure, if applicable
Virtual Payment Address of the customer, if applicable
âž” Type of the transaction
Reference number for the transaction
Unique Transaction Reference number for the transaction
Description of the settlement
Name of the settlement bank account
Total amount to be settled
First tax amount deducted from the settlement
Second tax amount deducted from the settlement
Third tax amount deducted from the settlement
First fee amount deducted from the settlement
Second fee amount deducted from the settlement
Final amount after taxes and fees have been deducted
âž” Status of the external settlement
Consolidation identifier for the settlement
Bank transaction reference for the settlement
Account number associated with the settlement
Digio's unique transaction reference number
Date of settlement for the transaction
Identifier of the parent transaction, if any
List of details for each settlement transaction
Transaction ID of the debit transaction
Amount in paise of the debit transaction
Account number associated with the transaction
Unique Reference Number for the settlement
Date and time when the settlement was processed
Mandate information associated with the scheduled plan
Unique identifier for the UPI mandate
Customer ID associated with the mandate
Name of the customer
Identifier for the customer, such as a phone number
Virtual Payment Address of the customer
Bank code of the partner bank
Reference number of the customer, not present in the provided JSON but assumed to be relevant
Reference number of the scheme, not present in the provided JSON but assumed to be relevant
âž” Indicates if the mandate is for recurring payments
âž” Frequency of the mandate collection
Date for the first collection attempt
Date for the final collection attempt
Amount to be collected per transaction
Maximum amount that can be collected
âž” Type of the mandate
âž” Authentication type for the mandate
âž” Current status of the mandate
Reference number provided by the organization's PSP
Unique Mandate Reference Number
Timestamp when the mandate was authenticated
IFSC code of the debit account
Message describing the reason for any failure
Debit account number
Narration for the mandate
Configuration ID for the corporate
Merchant code
Name of the service provider
Timestamp of the last update to the mandate
Details of customer
Name of the customer
âž” Type of account of the customer
IFSC code of the bank
Masked account number of the customer
Details of corporate
Name of the corporate
Utility code registered for the corporate
Reference number against the corporate
IFSC code of the sponsor bank
Bank code for sponsor bank
Masked account number of the corporate
Date for the first proposed settlement
Date for the next scheduled settlement
Total number of payments to be made
âž” Number of payments already made
Date when the next payment should be presented
Date when the last payment was presented
Date of the last presented settlement
âž” Frequency of subscription payments
Narration or description of the payment schedule
Amount to be paid in paise
Transaction reference
Date when the schedule ended
Mandate ID associated with the payment schedule
Client reference ID for identification
List of all transactions for the specific UPI schedule plan
⮕ [ List of all transactions for the specific UPI schedule plan ]
Unique identifier for the transaction
UMRN associated with the transaction
âž” State of the transaction
Creation timestamp of the transaction
Update timestamp of the transaction
Timestamp when the transaction status was last updated
Name of the customer
Unique ID of the customer
Detailed information about the UPI transaction
âž” Status of the NACH payment transaction
Transaction amount in standard currency units
Transaction amount in the smallest currency units (e.g., paise)
Identifier for the sponsor bank
Timestamp indicating when the transaction is ready to be processed
Code indicating the reason for transaction failure, if applicable
Description of the reason for transaction failure, if applicable
Virtual Payment Address of the customer, if applicable
âž” Type of the transaction
Reference number for the transaction
Unique Transaction Reference number for the transaction
Description of the settlement
Name of the settlement bank account
Total amount to be settled
First tax amount deducted from the settlement
Second tax amount deducted from the settlement
Third tax amount deducted from the settlement
First fee amount deducted from the settlement
Second fee amount deducted from the settlement
Final amount after taxes and fees have been deducted
âž” Status of the external settlement
Consolidation identifier for the settlement
Bank transaction reference for the settlement
Account number associated with the settlement
Digio's unique transaction reference number
Date of settlement for the transaction
Identifier of the parent transaction, if any
List of details for each settlement transaction
Transaction ID of the debit transaction
Amount in paise of the debit transaction
Account number associated with the transaction
Unique Reference Number for the settlement
Date and time when the settlement was processed
Only present if a sub-user has created the schedule.
Unique ID for sub-user
Identifier for sub-user, this is generally emailID or mobile number
âž” This denotes what type of identifier was used
Sub-user's email id, if registered
Subuser's mobile number
Timestamp when the scheduled plan was created
Timestamp when the scheduled plan was last updated
Details about the exception. Usually contains the exception id for reference.
Error code
Description of the error
Custom errors
Getting started with Digio Rest Apis
|
HTTP Basic
Send
Authorization in header containing the word Basic followed by a space and a base64 encoded string of username:password.
|
This API is used to create schedule plan for a multiple UMRN. Max number of presentations which can be created is 500 per api call.
{
"requests": [
{
"umrn": "10b3ab554e0e40bfbff7843d4743fe63@upi",
"amount": 9.0,
"settlement_date": "2019-04-10 14:30:00",
"corporate_account_number": "123456789",
"unique_key": "LAN_EMI_1",
"narration": "TW Loan EMI"
},
{
<entry-2>
},
{
<entry-3>
}
]
}
Mandate UMRN created upon successful registration of Mandate
Date for Settlement in yyyy-mm-dd hh:mm:ss
Default: (i) first_collection_date as provided in registered mandate OR (ii) current date Note : Settlement Date should be more than 26 hours from current time
âž” Any one of corporate_account_number or settlement_config_profile_id or split_settlement_info is required. All numeric
Config of settlement, if already predefined. Any one of corporate_account_number or settlement_config_profile_id or split_settlement_info is required.
Either of amount or amount_in_paise is mandatory
Either of amount or amount_in_paise is mandatory.
âž” Default: Enterprise name
➔ To be used for Corporate’s reference.
Default:
Set value to assign it to a sub-user
âž” Any one of corporate_account_number or settlement_config_profile_id or split_settlement_info is required.
Min Items: 2 Max Items: 10 ⮕ [ Any one of corporate_account_number or settlement_config_profile_id or split_settlement_info is required. ]
Bank Account Number
Amount to be settled in paise
âž”
âž” Should be non-negative and >= 1. payment_count has to be one if frequency is ONETIME
Please refer below for the additional attributes, that should only be passed by Mutual Fund use case customers
Member ID for whom the PA/ Bank is uploading the file
UCC for the said Client.
Unique reference number provided by the member for payment to be collected for a unique client.
âž” Pass the Order Number for this SIP order
Type of transaction
âž”
âž”
âž”
âž”
âž”
âž”
Details about the exception. Usually contains the exception id for reference.
Error code
Description of the error
Custom errors
Was this page helpful?