Skip to content

Add payment cryptography emulation operations, recipes, and validation guardrails#2334

Open
J8k3 wants to merge 13 commits intogchq:masterfrom
J8k3:master
Open

Add payment cryptography emulation operations, recipes, and validation guardrails#2334
J8k3 wants to merge 13 commits intogchq:masterfrom
J8k3:master

Conversation

@J8k3
Copy link
Copy Markdown

@J8k3 J8k3 commented Apr 25, 2026

Summary

This PR adds a payment-focused extension surface to CyberChef for software emulation, testing, interoperability work, and education.

It is intentionally documented as software-only tooling rather than a certified HSM or production key-custody surface. AI was used to ensure payment functionality is implemented per specifications or as close to as is possible with publicly available documentation.

What This Adds

  • A new Payments category with payment-facing operations for:
    • data encryption / decryption / re-encryption
    • MAC generation / verification
    • EMV ARQC / ARPC / MAC helpers
    • clear PIN block build / parse / translate
    • card validation data
    • DUKPT / ECDH / KCV helpers
    • test PAN generation / parsing
    • TR-31 / TR-34 inspection helpers
  • Payment recipe and chaining docs:
    • PAYMENT_RECIPES.md
    • AWS_PAYMENT_CRYPTOGRAPHY_RECIPES.md
    • PAYMENT_SIM_RECIPES.md
  • A validation audit with explicit guardrails:
    • PAYMENT_VALIDATION_AUDIT.md
  • UI improvements for payment operations:
    • inline recipe-card guidance
    • visible validation / scope / security wording
    • built-in test-data population helpers

Validation / Guardrails

The payment operations are explicitly classified in PAYMENT_VALIDATION_AUDIT.md as:

  • verified against public standards / vectors
  • vendor-aligned
  • externally cross-checked
  • emulation helpers

That status is also surfaced inline on higher-risk operations so users can see scope and limitations in the recipe UI.

Scope Notes

  • Intended for software emulation, QA, interoperability, and educational use.
  • Not a certified HSM implementation.
  • Not presented as a PCI-scoped production key-custody surface.

Verification

  • Docker build completed successfully from this branch.
  • Payment-focused vectors and operation tests were added/expanded in tests/operations/tests/Payment.mjs.
  • Common recipe chains are documented explicitly in the payment docs.

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Apr 25, 2026

CLA assistant check
All committers have signed the CLA.

@C85297 C85297 added the AI Used label Apr 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants