Add payment cryptography emulation operations, recipes, and validation guardrails#2334
Open
J8k3 wants to merge 13 commits intogchq:masterfrom
Open
Add payment cryptography emulation operations, recipes, and validation guardrails#2334J8k3 wants to merge 13 commits intogchq:masterfrom
J8k3 wants to merge 13 commits intogchq:masterfrom
Conversation
Added a section for Payment Cryptography Extensions detailing the scope, future extensions, non-goals, and organization of custom operations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Paymentscategory with payment-facing operations for:PAYMENT_RECIPES.mdAWS_PAYMENT_CRYPTOGRAPHY_RECIPES.mdPAYMENT_SIM_RECIPES.mdPAYMENT_VALIDATION_AUDIT.mdValidation / Guardrails
The payment operations are explicitly classified in
PAYMENT_VALIDATION_AUDIT.mdas:That status is also surfaced inline on higher-risk operations so users can see scope and limitations in the recipe UI.
Scope Notes
Verification
tests/operations/tests/Payment.mjs.