Security & Compliance
Review the exact hardware, payment application, SDK configuration and connected services against the customer’s requirements. Device or payment-component certification does not certify the entire kiosk deployment. The project team can discuss applicable evidence, test scope and responsibilities before rollout.
Agree encryption, service authentication, access controls, data retention and logging requirements for the complete deployment. Keep document images, biometric samples and payment data out of routine diagnostic logs. Protection depends on the application, SDK runtime, connected devices and backend services; confirm the controls and evidence for that configuration during evaluation.
Satellite provides application release and fleet-management workflows for supported Windows, Linux and Android devices. Select the intended devices, apply the release through the supported workflow and review the reported installation outcome. Platform capabilities and enterprise-policy requirements still apply; a reported installation is verified against the customer workflow rather than assumed from publication.
Azimut SDK connects supported document readers and biometric devices to the kiosk application. The application submits the required data to the configured identity or banking service. That service owns the verification decision; device capture alone does not establish identity or regulatory compliance. Required checks, retention and access controls are agreed for the deployment.