Amazon Payment Cryptography · Schema
KeyUsage
KeyUsage schema from Amazon Payment Cryptography
CryptographyFinancial-ServicesPayment ProcessingPCI
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/amazon-payment-cryptography/refs/heads/main/json-schema/openapi-key-usage-schema.json",
"title": "KeyUsage",
"description": "KeyUsage schema from Amazon Payment Cryptography",
"type": "string",
"enum": [
"TR31_B0_BASE_DERIVATION_KEY",
"TR31_C0_CARD_VERIFICATION_KEY",
"TR31_D0_SYMMETRIC_DATA_ENCRYPTION_KEY",
"TR31_D1_ASYMMETRIC_KEY_FOR_DATA_ENCRYPTION",
"TR31_E0_EMV_MKEY_APP_CRYPTOGRAMS",
"TR31_E1_EMV_MKEY_CONFIDENTIALITY",
"TR31_E2_EMV_MKEY_INTEGRITY",
"TR31_E4_EMV_MKEY_DYNAMIC_NUMBERS",
"TR31_E5_EMV_MKEY_CARD_PERSONALIZATION",
"TR31_E6_EMV_MKEY_OTHER",
"TR31_K0_KEY_ENCRYPTION_KEY",
"TR31_K1_KEY_BLOCK_PROTECTION_KEY",
"TR31_K3_ASYMMETRIC_KEY_FOR_KEY_AGREEMENT",
"TR31_M3_ISO_9797_3_MAC_KEY",
"TR31_M6_ISO_9797_5_CMAC_KEY",
"TR31_M7_HMAC_KEY",
"TR31_P0_PIN_ENCRYPTION_KEY",
"TR31_P1_PIN_GENERATION_KEY",
"TR31_S0_ASYMMETRIC_KEY_FOR_DIGITAL_SIGNATURE",
"TR31_V1_IBM3624_PIN_VERIFICATION_KEY",
"TR31_V2_VISA_PIN_VERIFICATION_KEY",
"TR31_K2_TR34_ASYMMETRIC_KEY"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/openapi-key-usage"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.