Skip to content

RFID Processing

The server-side RFID reprocessing lets you perform complete server-side verification for electronic document chip. While reading is performed on mobile via NFC, the server is involved in the process for generation and storage of session keys and challenges.

This allows further reprocessing of the captured reading session in the “zero-trust to mobile” model to validate the chip and its data authenticity and validity via Chip Authentication, Active Authentication and Passive Authentication on the server-side.

To enable the server-side RFID processing, make sure to deploy a local service and data storage for the session keys and challenges. On the service side, set the Chip Verification parameters and/or Passive Authentication parameters.

PA Notification Codes

You can configure RFID chip processing parameters at the request time.

Use paIgnoreNotificationCodes to define notification codes that should be ignored during passive authentication (PA). For the full list of notification codes, see the eLDS_ParsingNotificationCodes enumeration.

Here is an example with two PA sensitive codes defined:

{
    "processParam": {
        "rfid": {
            "paIgnoreNotificationCodes": [
                -1879047658,
                -1879047667
            ]
        }
    }
}

Data Processing

You can perform either of the two variants of the RFID Data Processing:

Verify Entire Session

To reprocess the entire RFID session, retrieved by Regula reader devices, send the request to the Web Service in the following form:

{
    "processParam": {
        "scenario": "RFID"
    },
    "List": [
        {
            "ByteArray": "<Base64-encoded data>",
            "result_type": 48
        }
    ]
}

Set the RFID processing scenario, the 48 result type for the entire RFID session, and the Base64-encoded content of the RFID_Session.dat file, produced by the Regula document reader device.

Verify Data Groups

To reprocess the specific RFID Data Groups (DG), retrieved by either Regula or other third-party compatible reader devices, send the request to the Web Service in the following form: 

{
    "processParam": {
        "scenario": "RFID"
    },
    "List": [ 
        {
            "TDocBinaryInfo": {
                "RFID_RAW_DATA": [
                    {
                        "Data": "<Base64-encoded DG data>",
                        "FieldType": "<eRFID_DataFile_Type>"
                    },
                    ...
                ]  
            },
            "result_type": 101
        }
    ]
}

Set the RFID processing scenario, optionally add the Base64-encoded image data with the applied light source reference, and provide the RFID_RAW_DATA container with Base64-encoded data of the specific Data Group(s). The result_type must be correspondingly set to 101 which stands for RFID_RAW_DATA.

Next Steps