Certificate
SecurePay PQC Integration
Merchant integrates with SecurePay using Post-Quantum Cryptographic (PQC) signatures. The objective is to ensure that all API requests sent to SecurePay are cryptographically signed and verified using quantum-resistant keys and certificates.
Key Concepts
KAZ-SIGN Key Pair
The merchant’s Post-Quantum signing key pair. Generated locally by the merchant.
CSR (Certificate Signing Request)
A request generated by the merchant to obtain a signed PQC certificate from SecurePay CA.
SecurePay CA
SecurePay’s Certificate Authority (issues PQC certificates).
PQC Certificate
A cryptographic certificate that binds the merchant’s public key + identity. Used by SecurePay to verify signatures.
Setup & Workflow

API Key Creation Flow Overview
To start using the API, users must create a cryptographic key pair associated with their interface (e.g., version2 interface).
Merchant have two options for adding keys: Generate a new key pair automatically or Import an existing public key.
Key Generation Process
Provide a descriptive name for the key
Choose the cryptographic algorithm. Current options include:
RSA (production-ready)
PQC (Post-Quantum Cryptography - Experimental)
In the Import Your Own Public Key section, paste your public key in PEM format
Optionally, set an expiration date for the key.
After clicking Create Key, the system will display the private key once—be sure to save it securely.

Upon successful upload, the system redirects you to the key details page showing your key information.

Last updated
