Decoding FASTag: How National Electronic Toll Collection (NETC) Works?

The National Payments Corporation of India (NPCI) has built the RFID-enabled National Electronic Toll Collection (NETC) program poised to fulfil the electronic tolling needs of the transport market of India. For the same objective, NPCI now offers a national interoperable toll-payment solution that also inculcates within its scope the offering of clearinghouse services for settlement of disputes. Within its spectrum of offering ‘Interoperability’ (applied to NETC system), it includes a common set of procedures, business rules and technical specifications allowing a customer to utilise their FASTag as a payment mode on either of the toll plazas, regardless of the specifics of the acquirer of the toll plaza.

The various objectives of NETC FASTag are: i. creating a compatible and interoperable toll-collection ecosystem to use nationally. ii. through a simple and robust framework, increase transparency and efficiency in transaction processing. iii. achieving the sub-goals of the Government of India of electronification of retail payments, reducing air pollution via decreased toll plaza congestion, plummeting fuel consumption and promoting cashless transactions, enhancing audit control via user account centralisation

NETC – the technical ecosystem on which the FASTag is based – supports multiple issuers and acquirers authorised for the NETC program. The transaction request from the Toll Plaza is sent to the Acquiring System for transactional validation, and it then moves further so as to finally reach the NETC Switch. The NPCI routes these transactions to the relevant Issuer Bank for debiting the tag-holder account. During the entire process, a particular transaction travels through an 8-step (LEGs) process.

The NETC transaction process flow emanates at the Toll Plaza System (capturing the FASTag data, viz. Tag ID, TID, Vehicle Class, etc.) and travels through the Acquirer Bank for processing, which then sends a request to the Online Switch & Mapper (i.e., the NETC validation mechanism that responds with such details as Vehicle class, VRN, Tag Status, etc. – upon an absence of the Tag ID in NETC Mapper, a response is issued stating that the Tag ID isn’t registered). Following the receipt of a Tag ID validation from the NETC Mapper, the acquirer host calculates the relevant toll fare and emanates a debit request to the NETC system. Then the NETC system switches the debit request to the relevant issuer bank for debiting the customer account.

The Issuer host then debits the linked tag holder account and sends an SMS alert to the tag holder. It also sends the response message to the NETC system. Upon failing to send the response within the defined TAT (Turn-Around-Time), the transaction is considered as Deemed Accepted. The response is then notified to the acquirer host for notifying the respective toll plaza system.