結帳金鑰和收銀金鑰
Cardflo 利用結帳金鑰和收銀金鑰為商戶提供安全靈活的集成選項。 結帳金鑰管理支付會話啟動和客戶數據收集，而收銀金鑰則促進伺服器端交易處理。
這種分離確保了 PCI 合規性和所有支付流程的穩健安全性。
- 類別
- 開發者
- 功能數
- 10
- 適用於
- 所有方案
概覽
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.
運作方式
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.
為何重要
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.
應用案例
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.
數據概覽
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.
相關術語
Talk to our team about a live rollout on your acquiring stack.
What you get with 結帳金鑰和收銀金鑰
- 使用結帳金鑰安全地啟動支付會話
- 使用收銀金鑰處理伺服器端交易
- 通過隔離敏感數據來保持 PCI 合規性
- 與各種前端和後端框架集成
- 控制不同集成點的存取級別
- 增強客戶支付數據處理的安全性
- 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 結帳金鑰和收銀金鑰
結帳金鑰和收銀金鑰有什麼區別？
結帳金鑰用於前端啟動支付會話並安全地收集客戶支付數據。 收銀金鑰用於您的伺服器端完成交易、發送支付請求和管理退款，確保敏感操作仍由伺服器控制。
這些金鑰如何有助於 PCI 合規性？
Cardflo 通過分離金鑰幫助商戶保持 PCI 合規性。 結帳金鑰以安全、標記化的方式處理客戶數據收集，而收銀金鑰（在伺服器端使用）可防止敏感卡數據直接接觸您的伺服器，從而減少您的 PCI 範圍。
我可以在我的集成中使用結帳金鑰和收銀金鑰嗎？
是的，同時使用結帳金鑰和收銀金鑰是 Cardflo 推薦且最安全的集成方法。 這種組合為處理前端客戶交互和後端交易處理提供了強大的框架，優化了安全性和功能。
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.