An authentication is triggered via Digio link sent over SMS/Email or SDK trigger using eNACH id and identifier provided by Digio. In both cases below screens open - 

• NPCI then redirects the Customer to the Destination Bank’s NetBanking or to a Debit card authorization gateway.

Netbanking authentication example

Debit Card authentication example

• Post the authorization step, an NPCI status screen with the transaction Ref ID is shown.

• Then the flow redirects back to Digio’s green confirmation screen denoting that the mandate has been registered or back to the mandate form if failed (with reason). The customer may retry.

Note - 

• UMRN (Unique Mandate Ref No) is received immediately with a success authentication. 

• Maximum amount for this type of Mandate is Rs 10Lacs. (from 01/08/2020)

• Please refer to the NPCI website for live Destination Banks.

• If SDK integration: create auth session in front end with mandate ID and customer_identifier.

• If you want DIGIO to send a link of the NACH form to the customer: pass notify_customer : true. DIGIO will send the mandate link to customer_identifier passed.

• Customer and Customer bank A/C details in the form can be frozen (prefiled and uneditable) if passed by the Corporate. If left blank, the Customer fills up said details.

• The Customer previews the form, selects auth mode (Netbanking/Debit Card) depending on what the Destination Bank supports and proceeds to the Destination Bank via. NPCI ONMAGS gateway.

• Post authentication, NPCI summary screen shows the NPCI Ref ID, UMRN and Mandate registration status.

• DIGIO triggers a webhook event basis success/failure. If success, the DIGIO payload will have the UMRN.

• The Sponsor bank is supposed to receive data on EOD of the same working day from NPCI and share the same with DIGIO over H2H/SFTP.