Sorry, you need to enable JavaScript to visit this website.
Skip to main content
Emandate Registration

contains 1 APIs

To resolve this, the requirement is to host API for corporates to publish the status of dropped out cases.
Feature Icon
feature icon
Feature description
e-Mandate is used for registering mandates digitally. Entire workflow consists of page redirection from Corporate to Sponsor bank, Sponsor bank to NPCI, NPCI to Destination bank (Net Banking, Debit Card), Destination bank to NPCI, NPCI to Sponsor bank and Sponsor bank to Corporate.
    APIs

    1 APIs used

    API's Severity Documentation Try It Now

    e_Mandate_Double_Verification

    API display name : E-Mandate Double Verification
    Description : e-Mandate is used for registering mandates digitally. Entire workflow consists of page redirection from Corporate to Sponsor bank, Sponsor bank to NPCI, NPCI to Destination bank (Net Banking, Debit Card), Destination bank to NPCI, NPCI to Sponsor bank and Sponsor bank to Corporate.

    Status of the dropped out cases are not known to Corporates.
    To resolve this, the requirement is to host API for corporates to publish the status of dropped out cases.

    As per Legal directions, source application should match the eKYC name with the customer name provided in source application. If source application is satisfied with the name match then only XML should be pushed to NPCI for mandate registration.
    Since each source application will have their own Name Match percentage tolerance limit hence eMandate hosted a Rest API for source application to confirm whether they are accepting the Aadhar based eMandate with given eKYC details or not. If they are ok then they will pass the value as “Accepted” else they will pass the value as “Rejected” with reason.