Clés de paiement et clés de caissier
Cardflo utilise les clés de paiement (Checkout Keys) et les clés de caissier (Cashier Keys) pour offrir des options d'intégration sécurisées et flexibles aux commerçants.
Les clés de paiement gèrent l'initiation de la session de paiement et la collecte des données client, tandis que les clés de caissier facilitent le traitement des transactions côté serveur.
Cette séparation garantit la conformité PCI et une sécurité robuste pour tous les flux de paiement.
- Catégorie
- Développeur
- Capacités
- 10
- Disponible sur
- Tous les plans
L'aperçu
The separation of credentials into checkout keys and cashier keys represents a foundational security architecture in modern payment orchestration. Checkout keys are public-facing identifiers used within client-side environments, such as web browsers or mobile applications, to initialise payment components and collect sensitive cardholder data.
These keys allow a merchant to render a checkout interface without exposing sensitive backend permissions. Conversely, cashier keys are restricted, server-side credentials designed for authenticated communication between a merchant server and the payment gateway.
By bifurcating these roles, the system ensures that a compromise of the client-side code does not grant an attacker the ability to perform administrative actions, such as initiating refunds or capturing authorised payments.
This architectural approach assists in maintaining PCI DSS compliance by minimising the scope of systems that interact directly with raw payment credentials while allowing for a programmable, granular control over transaction lifecycles.
Comment ça marche
Client-side session initiation
The integration begins with the checkout key being utilised within the frontend application to request a secure session.
This key identifies the merchant identity (MID) and authorises the rendering of secure payment elements, ensuring that customer card details are tokenised before they ever reach the merchant infrastructure.
Secure data tokenisation
As the customer enters their payment details, the checkout key facilitates a direct connection to the vault. Sensitve fields like the PAN and CVV are converted into temporary tokens.
This process ensures that the merchant environment remains outside the primary scope of PCI DSS requirements.
Server-to-server authorisation
Once a token is generated, the merchant server uses its cashier key to request a formal authorisation from the acquirer. This private key confirms the request is legitimate and allows the gateway to map the temporary token back to the stored payment data for processing.
Transaction lifecycle management
Post-authorisation actions, including capture, settlement, and refunds, are exclusively handled via the cashier key. Because these actions involve the movement of funds, they require the higher level of authentication and restricted access that the server-side cashier key provides to the merchant administrator.
Pourquoi c'est important
Risk and liability mitigation
Dividing credentials reduces the blast radius of a potential security breach. If a checkout key is intercepted from a website source code, the attacker cannot use it to withdraw funds or access historical transaction records.
The cashier key remains protected on a secure backend, ensuring that only authorised server environments can execute financial movements, which is a critical defence against common injection attacks.
Simplified PCI DSS compliance
By utilising checkout keys to handle cardholder data via hosted fields or components, merchants typically qualify for a reduced compliance burden, such as SAQ A or SAQ A-EP.
The cashier key ensures that sensitive data is handled in a tokenised format on the backend, removing the need for the merchant to store, process, or transmit raw credit card information on their own servers.
Cas d'usage
E-commerce web applications
Merchants use checkout keys to embed secure payment forms directly into their websites, while the cashier key is stored in their backend environment to finalise the capture of funds once the order is confirmed.
Native mobile apps
Mobile developers use checkout keys within iOS or Android apps to securely gather payment signatures, relying on server-side cashier keys to manage the complex logic of multi-currency settlement and recurring billing.
Subscription and recurring billing
After the initial checkout key collects the card details, the cashier key is used to establish a merchant-initiated transaction (MIT) framework, allowing for automated renewals without further customer intervention.
En chiffres
Industry standards suggest that offloading data capture to hosted components via client-side keys can reduce the number of applicable PCI requirements by over 90 percent.
Standardised key-based architectures typically allow developers to implement a basic secure checkout flow within approximately two working days of development time.
Professional payment gateways require 100 percent of server-side requests to be authenticated via a private key to ensure the integrity of the transaction lifecycle.
Termes associés
Talk to our team about a live rollout on your acquiring stack.
What you get with Clés de paiement et clés de caissier
- Initier en toute sécurité les sessions de paiement avec les clés de paiement
- Traiter les transactions côté serveur à l'aide des clés de caissier
- Maintenir la conformité PCI en isolant les données sensibles
- Intégrer avec divers frameworks front-end et back-end
- Contrôler les niveaux d'accès pour différents points d'intégration
- Améliorer la sécurité de la gestion des données de paiement des clients
- Reduce the probability of fraudulent fund transfers via compromised client-side code
- Facilitate secure tokenisation of cardholder details at the point of initial entry
- Enable merchant-initiated transactions for subscription models using secure backend authentication
- Provide clear audit trails for both client-side sessions and server-side management actions
A short scoping call, then a written plan for your MIDs.
Questions about Clés de paiement et clés de caissier
Quelle est la différence entre une clé de paiement et une clé de caissier ?
Une clé de paiement (Checkout Key) est utilisée sur le frontend pour initier une session de paiement et collecter en toute sécurité les données de paiement du client.
Une clé de caissier (Cashier Key) est utilisée côté serveur pour finaliser la transaction, envoyer les demandes de paiement et gérer les remboursements, garantissant que les opérations sensibles restent contrôlées par le serveur.
Comment ces clés contribuent-elles à la conformité PCI ?
En séparant les clés, Cardflo aide les commerçants à maintenir la conformité PCI.
Les clés de paiement gèrent la collecte des données client de manière sécurisée et tokenisée, tandis que les clés de caissier, utilisées côté serveur, empêchent les données de carte sensibles d'atteindre directement vos serveurs, réduisant ainsi votre portée PCI.
Puis-je utiliser à la fois les clés de paiement et les clés de caissier dans mon intégration ?
Oui, l'utilisation des deux types de clés est l'approche d'intégration recommandée et la plus sécurisée pour Cardflo. Cette combinaison fournit un cadre robuste pour gérer à la fois les interactions client front-end et le traitement des transactions back-end, optimisant la sécurité et les fonctionnalités.
How should cashier keys be stored within a merchant's infrastructure?
Cashier keys must be treated as highly sensitive credentials. They should never be hard-coded into source files or stored in version control systems like Git.
Instead, they should be managed using environment variables or a dedicated secret management service. Access to these keys should be restricted to the specific server instances that require them to communicate with the payment processor for transaction finalisation and reporting.
What happens if a checkout key is leaked or compromised?
If a checkout key is compromised, the impact is generally low compared to a secret key leak.
An attacker could potentially use the key to submit junk data or attempt to create tokens through the merchant's MID, but they cannot access existing customer data or funds.
However, it is still standard practice to rotate the leaked checkout key to prevent any unauthorised use of the merchant's frontend assets and to maintain clean transaction logs.
Do cashier keys support different levels of permission based on the user?
While the cashier key itself represents a high-level server credential, industry-standard gateways often allow for the creation of multiple keys with various scopes.
For example, one cashier key might be restricted to read-only access for reporting, while another might have the authority to process captures and refunds.
This follows the principle of least privilege, ensuring each part of a merchant's backend system only has the permissions it needs to function.
Prêt à accélérer ?
Parlez-nous de votre activité. Nous vous mettrons en relation avec les bons partenaires acquéreurs et la bonne route, généralement en moins d'une semaine.