Chaves de checkout e chaves de caixa
A Cardflo utiliza Chaves de Checkout e Chaves de Caixa para fornecer opções de integração seguras e flexíveis para comerciantes.
As Chaves de Checkout gerem o início da sessão de pagamento e a recolha de dados do cliente, enquanto as Chaves de Caixa facilitam o processamento de transações do lado do servidor.
Esta separação garante a conformidade PCI e uma segurança robusta para todos os fluxos de pagamento.
- Categoria
- Programador
- Funcionalidades
- 10
- Disponível em
- Todos os planos
A visão geral
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.
Como funciona
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.
Por que importa
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.
Casos de uso
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.
Em números
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.
Termos relacionados
Talk to our team about a live rollout on your acquiring stack.
O que obtém com Chaves de checkout e chaves de caixa
- Inicie sessões de pagamento de forma segura com Chaves de Checkout
- Processe transações do lado do servidor usando Chaves de Caixa
- Mantenha a conformidade PCI isolando dados sensíveis
- Integre com várias frameworks de frontend e backend
- Controle os níveis de acesso para diferentes pontos de integração
- Melhore a segurança no manuseio de dados de pagamento do cliente
- 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.
Perguntas sobre Chaves de checkout e chaves de caixa
Qual é a diferença entre uma Chave de Checkout e uma Chave de Caixa?
Uma Chave de Checkout é usada no frontend para iniciar uma sessão de pagamento e recolher de forma segura os dados de pagamento do cliente.
Uma Chave de Caixa é usada no seu lado do servidor para finalizar a transação, enviar pedidos de pagamento e gerir reembolsos, garantindo que as operações sensíveis permanecem controladas pelo servidor.
Como estas chaves contribuem para a conformidade PCI?
Ao separar as chaves, a Cardflo ajuda os comerciantes a manter a conformidade PCI.
As Chaves de Checkout lidam com a recolha de dados do cliente de forma segura e tokenizada, enquanto as Chaves de Caixa, usadas do lado do servidor, impedem que os dados sensíveis do cartão entrem em contacto direto com os seus servidores,
reduzindo o seu âmbito PCI.
Posso usar ambas as Chaves de Checkout e Chaves de Caixa na minha integração?
Sim, usar ambas as Chaves de Checkout e Chaves de Caixa é a abordagem de integração recomendada e mais segura para a Cardflo.
Esta combinação proporciona uma framework robusta para lidar tanto com as interações do cliente no frontend quanto com o processamento de transações no backend, otimizando a segurança e a funcionalidade.
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.
Funcionalidades relacionadas.
Pronto para a velocidade?
Fale-nos do seu negócio. Iremos apresentá-lo aos parceiros adquirentes e à rota certa, normalmente em menos de uma semana.