BI2UE Article 5 is the most problematic, and it involves a complex story behind it:
The system we were building at the time was used by users from Hong Kong, Macao, and Taiwan as well. Initially, all functions were linked using ID card numbers, with Hong Kong, Macao, and Taiwanese residents using their locally-issued ID card numbers. Later, business requirements emerged to support mainland-issued residence permits, and these were prioritized. After all, the residence permit is essentially equivalent to our local ID card. Upon receiving this requirement, along with a time constraint (due to the need for official announcement), we immediately began researching how to address it. Technically, the system's historical data could not be modified; we had to continue using ID card numbers, otherwise, there would be significant disruption, and all associated links would break. Furthermore, Hong Kong, Macao, and Taiwanese residents have three different documents (their local ID card, a return/taocheng permit for entry and exit, and a mainland residence permit), and the travel permit requires a single document with a unique number, which must be supported by any system. The system interface also needed to display the residence permit instead of the Hong Kong, Macao, or Taiwanese ID card, so the changes required were substantial...
This only covers three types of identification. The platform also supports login with a Chinese passport, but in reality, the system cannot retrieve the ID number when using a passport, making it impossible to complete any transactions. Even if forced to allow passport logins, it is still impossible to link them to the individual, which would lead to more serious problems. Fortunately, no one uses a passport to conduct business on this system, so this method has been disabled, and a message prompting users to "use their resident ID card to log in" has been displayed.