A dynamic cryptogram is a payment card security code that changes automatically on a schedule instead of staying fixed. It helps reduce reuse of copied card data in card-not-present transactions. The issuer or processor validates the current value at authorisation time, which makes the code less useful to fraudsters.
What the dynamic cryptogram changes in card security
A dynamic cryptogram replaces a static card security code with one that refreshes on a schedule, so a copied value ages out quickly. That changes the fraud equation for card-not-present payments: the code is still an authentication signal, but it becomes far less reusable if intercepted, skimmed, or stored from a prior transaction.
Because the value is only valid for a limited window, the control is designed to make simple replay attacks less effective. It does not remove the need for the rest of the cardholder authentication and fraud stack, but it raises the cost of using stolen card data as a reusable credential.
How issuers and processors validate a rotating code
The practical distinction is that validation happens against the current expected value at authorisation time, rather than against a fixed code printed on the card or stored in merchant systems. That means the payment path must support timely verification, and the issuer or processor becomes the authority on whether the presented code matches the active one.
This model is only useful when the ecosystem can retrieve or derive the live code reliably during the transaction. If a merchant, gateway, or tokenisation flow cannot present the latest value, the transaction may fail even though the underlying account is legitimate.
Why the moving code matters for fraud reduction
The main security value is reduction of data reuse. If an attacker captures a card number and security code from a compromised checkout flow, a static code can be reused in future attempts, but a dynamic cryptogram narrows that window and limits the value of any one theft event.
It also helps against “store and replay” abuse in card-not-present environments, where attackers rely on merchants, third parties, or malware to preserve payment data long enough for later misuse. The protection is strongest when the rest of the payment flow also limits exposure of card data and enforces transaction-specific checks.
Operational trade-offs and implementation considerations
Dynamic cryptograms improve resilience against reuse, but they add dependence on issuer, processor, and payment-channel timing. That creates a stricter availability and integration requirement than a fixed verification code, especially where authorisation latency, offline flows, or legacy checkout systems are involved.
For this reason, the control is best understood as a fraud-reduction mechanism, not a standalone guarantee. It works as part of a broader payment security design that still needs monitoring, anomaly detection, token handling, and careful exposure management for card data in transit and at rest.
Risk and Threat Considerations
Dynamic cryptograms reduce the usefulness of captured card verification data, but they also introduce dependency on live validation paths. If a merchant environment, gateway integration, or fallback process mishandles the current value, legitimate payments can fail or attackers may look for weaker alternate checkout paths.
Failure mechanism: Replay risk drops only when the current code is checked at authorisation time. Weak integration, delayed validation, or legacy fallback behaviour can leave the attacker with a usable path if the rotating value is not enforced consistently.
Impact: Stolen card data becomes less reusable, which lowers card-not-present fraud potential and shrinks the window for abuse after a compromise.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP API Security Top 10 | API2 — Broken Authentication | Dynamic cryptograms strengthen transaction authentication at authorisation time. |
| Recommendation — Verify that payment transactions check the live code, not a reusable static value. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Rotating payment codes are authenticator material with a lifecycle and validation window. |
| Recommendation — Manage the code lifecycle so only the current value is accepted at authorisation. | ||
| CIS Controls v8 | CIS-5 — Account Management | The control supports managing authentication material and limiting reuse across payment flows. |
| Recommendation — Restrict reuse of payment authentication data and review where it is stored or exposed. | ||
| NIST CSF 2.0 | PR.AA-05 — Identity and Access Management | The term is about validating a payment authenticator at transaction time. |
| Recommendation — Enforce transaction-time verification for payment authentication material. | ||
Practitioner Guidance
Why practitioners should care: Dynamic cryptograms are most valuable where merchants face repeated card-not-present abuse, but the control only works if the payment stack can validate the live value without creating brittle checkout failures. Treat it as a fraud-control design choice, not just a card feature.
Common misunderstanding: A rotating code does not make payment data “safe” if the card number, session, or token exposure remains broad elsewhere in the flow. The gain comes from limiting reuse, not from eliminating the need for secure handling of the rest of the transaction.
Practitioner takeaway: Evaluate whether your authorisation path, gateway timing, and fallback handling can support live verification before relying on dynamic cryptograms as a primary anti-fraud measure.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org