The API can perform the following operations:
The workflow request
Workflow object for payment
id of the payment on which to take action .
the action to be taken on the payment
tenantId of the payment
reason for taking the action.
Any additional fields can be captured here as a map
Payment status updated sucessfully.
Unique id of tenant.
Unique id of tenant.
Total amount due.
Unique id of tenant.
Transaction number of the payment
The date of payment in epoch
Mode of payment used.
The instrument date
The number of the instrument like dd number,cheque number etc.
The status of the instrument
IFSC code of the bank to which payment is made
Any additional fields can be captured here as a map
Payment details of each bill
id of the payment detail
tenantId of the payment detail
The total amount to be paid for the bill corresponding to the payment detail
The amount that is being paid
Receipt number entered manually for legacy data.
The receipt number generated for the payment against the bill
The receipt type generated for the payment against the bill
The epoch receipt date generated for the payment against the bill
The code of the businessService to which the bill belongs
The id of the bill for which the payment is made
Name of the Person who is making payment.
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
status of the bill.
The reason for cancellation of bill
Boolean indicating if the bill is cancelled
Additional fields can be captured here
The list of collection modes that are not allowed
Boolean flag indicating if partial payment is allowed to be collected
Flag indicating if advance can be collected
The minumun amount that can be paid against the bill
The businessService of the entity for which the bill is generated
The total amount to be paid for the bill
The consumer code for which bill is generated
The bill number generated by system
The date on which bill is generated
uuid of the billDetail.
tenantId of the billDetail.
The id of the corresponding demand .
The id of the parent bill.
Amount to be paid for the bill detail.
Amount paid by the citizen.
start date of the taxperiod
end date of the taxperiod
Receipt Date.
Type of Receipt.
To be used by third party applications, to send the channel name.
Voucher header need to refer from Finanicals.
Boundary need to refer from Core services.
Manual Receipt Number for legacy reciepts.
Manual Receipt date for legacy reciepts.
collectionType of the payment.
Description of the bill.
Expiry date in epoch
Remarks related to cancellation of payment
uuid of the billAccountDetail.
tenantId of the billAccountDetail.
uuid of the parent billDetail.
uuid of the demand for which the parent billDetail is created.
Priority of the account detail.
Amount to be paid for the bill account detail
The amount paid against the bill account detail
The taxHeadCode of the bill account detail
Additional fields can be captured in this object as map
purpose of the bill account detail.
Any additional fields can be captured here as a map
The person who is paying the bill
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
Unique id of tenant.
This API generates a transaction number and persists the payment details. The payment information is then pushed to queue for further processing.
Creates payment for list of bill
Unique id of tenant.
Unique id of tenant.
Total amount due.
Unique id of tenant.
Transaction number of the payment
The date of payment in epoch
Mode of payment used.
The instrument date
The number of the instrument like dd number,cheque number etc.
The status of the instrument
IFSC code of the bank to which payment is made
Any additional fields can be captured here as a map
Payment details of each bill
id of the payment detail
tenantId of the payment detail
The total amount to be paid for the bill corresponding to the payment detail
The amount that is being paid
Receipt number entered manually for legacy data.
The receipt number generated for the payment against the bill
The receipt type generated for the payment against the bill
The epoch receipt date generated for the payment against the bill
The code of the businessService to which the bill belongs
The id of the bill for which the payment is made
Name of the Person who is making payment.
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
status of the bill.
The reason for cancellation of bill
Boolean indicating if the bill is cancelled
Additional fields can be captured here
The list of collection modes that are not allowed
Boolean flag indicating if partial payment is allowed to be collected
Flag indicating if advance can be collected
The minumun amount that can be paid against the bill
The businessService of the entity for which the bill is generated
The total amount to be paid for the bill
The consumer code for which bill is generated
The bill number generated by system
The date on which bill is generated
uuid of the billDetail.
tenantId of the billDetail.
The id of the corresponding demand .
The id of the parent bill.
Amount to be paid for the bill detail.
Amount paid by the citizen.
start date of the taxperiod
end date of the taxperiod
Receipt Date.
Type of Receipt.
To be used by third party applications, to send the channel name.
Voucher header need to refer from Finanicals.
Boundary need to refer from Core services.
Manual Receipt Number for legacy reciepts.
Manual Receipt date for legacy reciepts.
collectionType of the payment.
Description of the bill.
Expiry date in epoch
Remarks related to cancellation of payment
uuid of the billAccountDetail.
tenantId of the billAccountDetail.
uuid of the parent billDetail.
uuid of the demand for which the parent billDetail is created.
Priority of the account detail.
Amount to be paid for the bill account detail
The amount paid against the bill account detail
The taxHeadCode of the bill account detail
Additional fields can be captured in this object as map
purpose of the bill account detail.
Any additional fields can be captured here as a map
The person who is paying the bill
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
Unique id of tenant.
Payment created sucessfully.
Unique id of tenant.
Unique id of tenant.
Total amount due.
Unique id of tenant.
Transaction number of the payment
The date of payment in epoch
Mode of payment used.
The instrument date
The number of the instrument like dd number,cheque number etc.
The status of the instrument
IFSC code of the bank to which payment is made
Any additional fields can be captured here as a map
Payment details of each bill
id of the payment detail
tenantId of the payment detail
The total amount to be paid for the bill corresponding to the payment detail
The amount that is being paid
Receipt number entered manually for legacy data.
The receipt number generated for the payment against the bill
The receipt type generated for the payment against the bill
The epoch receipt date generated for the payment against the bill
The code of the businessService to which the bill belongs
The id of the bill for which the payment is made
Name of the Person who is making payment.
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
status of the bill.
The reason for cancellation of bill
Boolean indicating if the bill is cancelled
Additional fields can be captured here
The list of collection modes that are not allowed
Boolean flag indicating if partial payment is allowed to be collected
Flag indicating if advance can be collected
The minumun amount that can be paid against the bill
The businessService of the entity for which the bill is generated
The total amount to be paid for the bill
The consumer code for which bill is generated
The bill number generated by system
The date on which bill is generated
uuid of the billDetail.
tenantId of the billDetail.
The id of the corresponding demand .
The id of the parent bill.
Amount to be paid for the bill detail.
Amount paid by the citizen.
start date of the taxperiod
end date of the taxperiod
Receipt Date.
Type of Receipt.
To be used by third party applications, to send the channel name.
Voucher header need to refer from Finanicals.
Boundary need to refer from Core services.
Manual Receipt Number for legacy reciepts.
Manual Receipt date for legacy reciepts.
collectionType of the payment.
Description of the bill.
Expiry date in epoch
Remarks related to cancellation of payment
uuid of the billAccountDetail.
tenantId of the billAccountDetail.
uuid of the parent billDetail.
uuid of the demand for which the parent billDetail is created.
Priority of the account detail.
Amount to be paid for the bill account detail
The amount paid against the bill account detail
The taxHeadCode of the bill account detail
Additional fields can be captured in this object as map
purpose of the bill account detail.
Any additional fields can be captured here as a map
The person who is paying the bill
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
Unique id of tenant.
The API runs the following set of validations on the payment request.
The request to be validated
Unique id of tenant.
Unique id of tenant.
Total amount due.
Unique id of tenant.
Transaction number of the payment
The date of payment in epoch
Mode of payment used.
The instrument date
The number of the instrument like dd number,cheque number etc.
The status of the instrument
IFSC code of the bank to which payment is made
Any additional fields can be captured here as a map
Payment details of each bill
id of the payment detail
tenantId of the payment detail
The total amount to be paid for the bill corresponding to the payment detail
The amount that is being paid
Receipt number entered manually for legacy data.
The receipt number generated for the payment against the bill
The receipt type generated for the payment against the bill
The epoch receipt date generated for the payment against the bill
The code of the businessService to which the bill belongs
The id of the bill for which the payment is made
Name of the Person who is making payment.
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
status of the bill.
The reason for cancellation of bill
Boolean indicating if the bill is cancelled
Additional fields can be captured here
The list of collection modes that are not allowed
Boolean flag indicating if partial payment is allowed to be collected
Flag indicating if advance can be collected
The minumun amount that can be paid against the bill
The businessService of the entity for which the bill is generated
The total amount to be paid for the bill
The consumer code for which bill is generated
The bill number generated by system
The date on which bill is generated
uuid of the billDetail.
tenantId of the billDetail.
The id of the corresponding demand .
The id of the parent bill.
Amount to be paid for the bill detail.
Amount paid by the citizen.
start date of the taxperiod
end date of the taxperiod
Receipt Date.
Type of Receipt.
To be used by third party applications, to send the channel name.
Voucher header need to refer from Finanicals.
Boundary need to refer from Core services.
Manual Receipt Number for legacy reciepts.
Manual Receipt date for legacy reciepts.
collectionType of the payment.
Description of the bill.
Expiry date in epoch
Remarks related to cancellation of payment
uuid of the billAccountDetail.
tenantId of the billAccountDetail.
uuid of the parent billDetail.
uuid of the demand for which the parent billDetail is created.
Priority of the account detail.
Amount to be paid for the bill account detail
The amount paid against the bill account detail
The taxHeadCode of the bill account detail
Additional fields can be captured in this object as map
purpose of the bill account detail.
Any additional fields can be captured here as a map
The person who is paying the bill
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
Unique id of tenant.
Payment info validated sucessfully.
Unique id of tenant.
Unique id of tenant.
Total amount due.
Unique id of tenant.
Transaction number of the payment
The date of payment in epoch
Mode of payment used.
The instrument date
The number of the instrument like dd number,cheque number etc.
The status of the instrument
IFSC code of the bank to which payment is made
Any additional fields can be captured here as a map
Payment details of each bill
id of the payment detail
tenantId of the payment detail
The total amount to be paid for the bill corresponding to the payment detail
The amount that is being paid
Receipt number entered manually for legacy data.
The receipt number generated for the payment against the bill
The receipt type generated for the payment against the bill
The epoch receipt date generated for the payment against the bill
The code of the businessService to which the bill belongs
The id of the bill for which the payment is made
Name of the Person who is making payment.
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
status of the bill.
The reason for cancellation of bill
Boolean indicating if the bill is cancelled
Additional fields can be captured here
The list of collection modes that are not allowed
Boolean flag indicating if partial payment is allowed to be collected
Flag indicating if advance can be collected
The minumun amount that can be paid against the bill
The businessService of the entity for which the bill is generated
The total amount to be paid for the bill
The consumer code for which bill is generated
The bill number generated by system
The date on which bill is generated
uuid of the billDetail.
tenantId of the billDetail.
The id of the corresponding demand .
The id of the parent bill.
Amount to be paid for the bill detail.
Amount paid by the citizen.
start date of the taxperiod
end date of the taxperiod
Receipt Date.
Type of Receipt.
To be used by third party applications, to send the channel name.
Voucher header need to refer from Finanicals.
Boundary need to refer from Core services.
Manual Receipt Number for legacy reciepts.
Manual Receipt date for legacy reciepts.
collectionType of the payment.
Description of the bill.
Expiry date in epoch
Remarks related to cancellation of payment
uuid of the billAccountDetail.
tenantId of the billAccountDetail.
uuid of the parent billDetail.
uuid of the demand for which the parent billDetail is created.
Priority of the account detail.
Amount to be paid for the bill account detail
The amount paid against the bill account detail
The taxHeadCode of the bill account detail
Additional fields can be captured in this object as map
purpose of the bill account detail.
Any additional fields can be captured here as a map
The person who is paying the bill
The mobileNumber of person who is paying
The owner of the bill
The address of the owner of the bill
The email id of the owner of the bill
The system user id of the owner of the bill
Unique id of tenant.