CryptoBind® Payment HSM offers robust cryptographic support tailored for payment applications, safeguarding the entire lifecycle of cryptographic keys. As secure and tamper-resistant devices, CryptoBind Payment HSMs ensure the confidentiality, integrity, and availability of sensitive data.
PIN & Card Transaction
Verification
Encyption & Key Management
Supporting POS ATM Network Management
Protocol
Supporting Key/Data Exchange API standards
Generating PVV and CVV Data, Card Keyset
3-D SecureTM Issuance
& Authorization
Key Features
Below listed are some key feature of CryptoBind® Payment HSM (Hardware Security Module)
High Availability & Disaster Recovery: CryptoBind Payment HSM supports clustering across multiple regions, ensuring uninterrupted service and robust disaster recovery capabilities.
Cryptographic Isolation: With up to 42 isolated partitions, each
CryptoBind HSM can securely support multiple customers or
applications simultaneously.
Compliance Flexibility: Supports NIST FIPS 140-3 (Level-3) and PCI PTS HSM compliance on the same device. Additionally, non-FIPS mode allows for custom applications and algorithms.
Flexible Architecture: Through virtual machines, the CryptoBind Payment HSM enables the hosting of custom applications or algorithms within its secure FIPS boundary.
Future-Proof Security: Equipped to support emerging post-quantum algorithms in non-FIPS mode, with plans to incorporate these algorithms into FIPS mode upon NIST ratification.
Rapid Deployment: Accelerate time to market with a comprehensive software development kit and an API-first approach that simplifies integration across multi-cloud, hybrid, and OEM environments.
Unified Solution: Achieve the lowest total cost of ownership (TCO) by reducing capital expenditure (Cap-Ex) and operational expenditure (Op-Ex) with a single HSM solution for both General Purpose and Payments needs.
High Capacity & Speed: Manages millions of cryptographic keys and supports billions of transactions with superior performance and scalability.
Techical Specifications
Comprehensive Cryptographic Algorithms: | |
Asymmetric Keys: |
|
Symmetric Keys: |
|
Hash/Message digests: |
|
Key derivation: |
|
Secure Operations: | |
Random number generation (SP 800-90). | |
M of N quorum control for fault tolerance. | |
Hardware root of trust | |
Secure boot | |
Cryptographic agility for future-proof security, including post-quantum cryptography |
APIs | |
Java (JCA/JCE) | |
PKCS#11 | |
Secure boot | |
Customer API’s |
Physical Characteristics | |
Operating temperature: +10°C to +50°C (+50°F to +122°F) | |
Storage temperature: -10°C to +55°C (+14°F to +131°F) | |
Relative humidity: 10% to 95% non-condensing | |
RoHS Compliant | |
Complies with FCC standard for Electromagnetic compatibility (EMC) | |
Compliant to UL, CE, WEEE * | |
Dimensions (W x H x D): 17.2″ (437 mm) x 3.5″ (89 mm) x 25.5″ (647 mm) | |
Gross Weight: 52 lbs (23.59 kg) | |
Packaging (W x H x L): 26.7″ (678 mm) x 11.4″ (290 mm) x 34.5″ (876 mm) |
Security Certifications | |
FIPS 140-3 Level 3 certified Cryptographic Boundary | |
PCI PTS-HSM 4.0 certified Cryptographic Boundary |
Payment Functions | |
Integrated HSM: Combines general-purpose and payment HSM functionalities. | |
Cloud-Ready: Tailored for secure cloud environments, safeguarding issuers, payment switches, gateways, and acquirers. | |
LSPay API Library | |
TR-31 key block | |
TR-34 key transport | |
PIN translation formats (ISO-0/1/2/3) |
Management & Monitoring | |
Advanced Partitioning: Multiple partitions with flexible resource allocation and role-based access control (RBAC) | |
Multi-Tenancy: Vendor as root of trust, supporting hybrid cloud deployments. | |
Secure Channels: TLS-model tunnel with Perfect Forward Secrecy (PFS) for untrusted environments. | |
Remote Administration: Manage securely with attested audit logs, tamper-evident protections, and zeroization features. | |
Secure key storage | |
Certificate storage | |
SecureMachine (run custom code in HSM boundary) | |
Mixed-mode (FIPS and non-FIPS) flexible partition | |
Custom fairshare design to meet cloud SLAs in multi-tenant deployments |