Understand Remote Key Injection
Last updated
Last updated
WizarPOS has developed a Remote Key Injection (RKI) system that is PCI PIN 3.1 certified, meeting the needs for secure, remote key injection.
This system allows customers to inject keys into their terminals remotely and securely, particularly useful for those without their own key injection systems or a secure key injection environment.
Enhanced Security: Prevents interception or manual manipulation of keys and data.
Cost-Effective: Reduces the need for personnel training and certification, lowering overall costs.
Scalability: Ideal for distributors or service providers needing to inject keys into multiple POS terminals at different locations.
PCI PIN 3.1 Approval: Ensures compliance with industry security standards.
Mutual Authentication: Ensures a secure channel between devices and servers.
Protocol Support: Complies with TR31 and TR34 key exchange block protocols.
Key Type Support: Compatible with all major key types.
For integrating with an existing host server, provide documentation on how the server works with the terminal side for customized agent adaptor development.
AIDL Interface: WizarPOS offers two terminal AIDL interfaces, as demonstrated in 'For Systems Without an Existing Host Server'.
Developing a remote key injection system from scratch is time-consuming and typically uncertified by PCI, making it suitable only for testing or internal use.
WizarPOS offers a remote key injection demo system for reference, including:
Remote_Key_Inject_Deployment.docx, it describes how to deploy and run the keyinjection jar in server.
Note: While WizarPOS provides a comprehensive RKI solution, the demo system is for reference and testing purposes only. When deploying in a live environment, ensure to replace the demo certificate with a valid, secure certificate.
, it describes the whole demo system, and the detail information for the certificates, core process.
The demo uses a certificate that replaces the original terminal certificate. Download the and run it to initialize the demo certificate. is necessary after use.