@aws-sdk/client-payment-cryptography-data 3.1050.0 → 3.1052.0

package/dist-types/commands/ReEncryptDataCommand.d.ts

@@ -29,7 +29,7 @@ declare const ReEncryptDataCommand_base: {
     };
 };
 /**
- * <p>Re-encrypt ciphertext using DUKPT or Symmetric data encryption keys. </p> <p>You can either generate an encryption key within Amazon Web Services Payment Cryptography by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> or import your own encryption key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. The <code>KeyArn</code> for use with this operation must be in a compatible key state with <code>KeyModesOfUse</code> set to <code>Encrypt</code>. </p> <p>This operation also supports dynamic keys, allowing you to pass a dynamic encryption key as a TR-31 WrappedKeyBlock. This can be used when key material is frequently rotated, such as during every card transaction, and there is need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. To re-encrypt using dynamic keys, the <code>keyARN</code> is the Key Encryption Key (KEK) of the TR-31 wrapped encryption key material. The incoming wrapped key shall have a key purpose of D0 with a mode of use of B or D. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/use-cases-acquirers-dynamickeys.html">Using Dynamic Keys</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>For symmetric and DUKPT encryption, Amazon Web Services Payment Cryptography supports <code>TDES</code> and <code>AES</code> algorithms. To encrypt using DUKPT, a DUKPT key must already exist within your account with <code>KeyModesOfUse</code> set to <code>DeriveKey</code> or a new DUKPT can be generated by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a>.</p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>DecryptData</a> </p> </li> <li> <p> <a>EncryptData</a> </p> </li> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html">GetPublicCertificate</a> </p> </li> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a> </p> </li> </ul>
+ * <p>Re-encrypt ciphertext using DUKPT or Symmetric data encryption keys. </p> <p>You can either generate an encryption key within Amazon Web Services Payment Cryptography by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> or import your own encryption key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. The <code>KeyArn</code> for use with this operation must be in a compatible key state with <code>KeyModesOfUse</code> set to <code>Encrypt</code>. </p> <p>This operation also supports dynamic keys, allowing you to pass a dynamic encryption key as a TR-31 WrappedKeyBlock. This can be used when key material is frequently rotated, such as during every card transaction, and there is need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. To re-encrypt using dynamic keys, the <code>keyARN</code> is the Key Encryption Key (KEK) of the TR-31 wrapped encryption key material. The incoming wrapped key shall have a key purpose of D0 with a mode of use of B or D. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/use-cases-acquirers-dynamickeys.html">Using Dynamic Keys</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>For symmetric and DUKPT encryption, Amazon Web Services Payment Cryptography supports <code>TDES</code> and <code>AES</code> algorithms. To encrypt using DUKPT, a DUKPT key must already exist within your account with <code>KeyModesOfUse</code> set to <code>DeriveKey</code> or a new DUKPT can be generated by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a>.</p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html">Resource-based policies</a>.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>DecryptData</a> </p> </li> <li> <p> <a>EncryptData</a> </p> </li> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html">GetPublicCertificate</a> </p> </li> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a> </p> </li> </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/TranslateKeyMaterialCommand.d.ts

@@ -29,7 +29,7 @@ declare const TranslateKeyMaterialCommand_base: {
     };
 };
 /**
- * <p>Translates an cryptographic key between different wrapping keys without importing the key into Amazon Web Services Payment Cryptography.</p> <p>This operation can be used when key material is frequently rotated, such as during every card transaction, and there is a need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. It translates short-lived transaction keys such as <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.pek">PEK</a> generated for each transaction and wrapped with an <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.ecdh">ECDH</a> derived wrapping key to another <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.kek">KEK</a> wrapping key. </p> <p>Before using this operation, you must first request the public key certificate of the ECC key pair generated within Amazon Web Services Payment Cryptography to establish an ECDH key agreement. In <code>TranslateKeyData</code>, the service uses its own ECC key pair, public certificate of receiving ECC key pair, and the key derivation parameters to generate a derived key. The service uses this derived key to unwrap the incoming transaction key received as a TR31WrappedKeyBlock and re-wrap using a user provided KEK to generate an outgoing Tr31WrappedKeyBlock.</p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> </p> </li> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html">GetPublicCertificate</a> </p> </li> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a> </p> </li> </ul>
+ * <p>Translates an cryptographic key between different wrapping keys without importing the key into Amazon Web Services Payment Cryptography.</p> <p>This operation can be used when key material is frequently rotated, such as during every card transaction, and there is a need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. It translates short-lived transaction keys such as <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.pek">PEK</a> generated for each transaction and wrapped with an <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.ecdh">ECDH</a> derived wrapping key to another <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.kek">KEK</a> wrapping key. </p> <p>Before using this operation, you must first request the public key certificate of the ECC key pair generated within Amazon Web Services Payment Cryptography to establish an ECDH key agreement. In <code>TranslateKeyData</code>, the service uses its own ECC key pair, public certificate of receiving ECC key pair, and the key derivation parameters to generate a derived key. The service uses this derived key to unwrap the incoming transaction key received as a TR31WrappedKeyBlock and re-wrap using a user provided KEK to generate an outgoing Tr31WrappedKeyBlock.</p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html">Resource-based policies</a>.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> </p> </li> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html">GetPublicCertificate</a> </p> </li> <li> <p> <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a> </p> </li> </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/TranslatePinDataCommand.d.ts

@@ -29,7 +29,7 @@ declare const TranslatePinDataCommand_base: {
     };
 };
 /**
- * <p>Translates encrypted PIN block from and to ISO 9564 formats 0,1,3,4. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/translate-pin-data.html">Translate PIN data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>PIN block translation involves changing a PIN block from one encryption key to another and optionally change its format. PIN block translation occurs entirely within the HSM boundary and PIN data never enters or leaves Amazon Web Services Payment Cryptography in clear text. The encryption key transformation can be from PEK (Pin Encryption Key) to BDK (Base Derivation Key) for DUKPT or from BDK for DUKPT to PEK.</p> <p>Amazon Web Services Payment Cryptography also supports use of dynamic keys and ECDH (Elliptic Curve Diffie-Hellman) based key exchange for this operation.</p> <p>Dynamic keys allow you to pass a PEK as a TR-31 WrappedKeyBlock. They can be used when key material is frequently rotated, such as during every card transaction, and there is need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. To translate PIN block using dynamic keys, the <code>keyARN</code> is the Key Encryption Key (KEK) of the TR-31 wrapped PEK. The incoming wrapped key shall have a key purpose of P0 with a mode of use of B or D. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/use-cases-acquirers-dynamickeys.html">Using Dynamic Keys</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>Using ECDH key exchange, you can receive cardholder selectable PINs into Amazon Web Services Payment Cryptography. The ECDH derived key protects the incoming PIN block, which is translated to a PEK encrypted PIN block for use within the service. You can also use ECDH for reveal PIN, wherein the service translates the PIN block from PEK to a ECDH derived encryption key. For more information on establishing ECDH derived keys, see the <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/create-keys.html">Creating keys</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>The allowed combinations of PIN block format translations are guided by PCI. It is important to note that not all encrypted PIN block formats (example, format 1) require PAN (Primary Account Number) as input. And as such, PIN block format that requires PAN (example, formats 0,3,4) cannot be translated to a format (format 1) that does not require a PAN for generation. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <note> <p>Amazon Web Services Payment Cryptography currently supports ISO PIN block 4 translation for PIN block built using legacy PAN length. That is, PAN is the right most 12 digits excluding the check digits.</p> </note> <p> <b>Cross-account use</b>: This operation can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>GeneratePinData</a> </p> </li> <li> <p> <a>VerifyPinData</a> </p> </li> </ul>
+ * <p>Translates encrypted PIN block from and to ISO 9564 formats 0,1,3,4. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/translate-pin-data.html">Translate PIN data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>PIN block translation involves changing a PIN block from one encryption key to another and optionally change its format. PIN block translation occurs entirely within the HSM boundary and PIN data never enters or leaves Amazon Web Services Payment Cryptography in clear text. The encryption key transformation can be from PEK (Pin Encryption Key) to BDK (Base Derivation Key) for DUKPT or from BDK for DUKPT to PEK.</p> <p>Amazon Web Services Payment Cryptography also supports use of dynamic keys and ECDH (Elliptic Curve Diffie-Hellman) based key exchange for this operation.</p> <p>Dynamic keys allow you to pass a PEK as a TR-31 WrappedKeyBlock. They can be used when key material is frequently rotated, such as during every card transaction, and there is need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. To translate PIN block using dynamic keys, the <code>keyARN</code> is the Key Encryption Key (KEK) of the TR-31 wrapped PEK. The incoming wrapped key shall have a key purpose of P0 with a mode of use of B or D. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/use-cases-acquirers-dynamickeys.html">Using Dynamic Keys</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>Using ECDH key exchange, you can receive cardholder selectable PINs into Amazon Web Services Payment Cryptography. The ECDH derived key protects the incoming PIN block, which is translated to a PEK encrypted PIN block for use within the service. You can also use ECDH for reveal PIN, wherein the service translates the PIN block from PEK to a ECDH derived encryption key. For more information on establishing ECDH derived keys, see the <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/create-keys.html">Creating keys</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>The allowed combinations of PIN block format translations are guided by PCI. It is important to note that not all encrypted PIN block formats (example, format 1) require PAN (Primary Account Number) as input. And as such, PIN block format that requires PAN (example, formats 0,3,4) cannot be translated to a format (format 1) that does not require a PAN for generation. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <note> <p>Amazon Web Services Payment Cryptography currently supports ISO PIN block 4 translation for PIN block built using legacy PAN length. That is, PAN is the right most 12 digits excluding the check digits.</p> </note> <p> <b>Cross-account use</b>: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html">Resource-based policies</a>.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>GeneratePinData</a> </p> </li> <li> <p> <a>VerifyPinData</a> </p> </li> </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/VerifyAuthRequestCryptogramCommand.d.ts

@@ -29,7 +29,7 @@ declare const VerifyAuthRequestCryptogramCommand_base: {
     };
 };
 /**
- * <p>Verifies Authorization Request Cryptogram (ARQC) for a EMV chip payment card authorization. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/data-operations.verifyauthrequestcryptogram.html">Verify auth request cryptogram</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>ARQC generation is done outside of Amazon Web Services Payment Cryptography and is typically generated on a point of sale terminal for an EMV chip card to obtain payment authorization during transaction time. For ARQC verification, you must first import the ARQC generated outside of Amazon Web Services Payment Cryptography by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. This operation uses the imported ARQC and an major encryption key (DUKPT) created by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> to either provide a boolean ARQC verification result or provide an APRC (Authorization Response Cryptogram) response using Method 1 or Method 2. The <code>ARPC_METHOD_1</code> uses <code>AuthResponseCode</code> to generate ARPC and <code>ARPC_METHOD_2</code> uses <code>CardStatusUpdate</code> to generate ARPC. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p> <b>Cross-account use</b>: This operation can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>VerifyCardValidationData</a> </p> </li> <li> <p> <a>VerifyPinData</a> </p> </li> </ul>
+ * <p>Verifies Authorization Request Cryptogram (ARQC) for a EMV chip payment card authorization. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/data-operations.verifyauthrequestcryptogram.html">Verify auth request cryptogram</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>ARQC generation is done outside of Amazon Web Services Payment Cryptography and is typically generated on a point of sale terminal for an EMV chip card to obtain payment authorization during transaction time. For ARQC verification, you must first import the ARQC generated outside of Amazon Web Services Payment Cryptography by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. This operation uses the imported ARQC and an major encryption key (DUKPT) created by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> to either provide a boolean ARQC verification result or provide an APRC (Authorization Response Cryptogram) response using Method 1 or Method 2. The <code>ARPC_METHOD_1</code> uses <code>AuthResponseCode</code> to generate ARPC and <code>ARPC_METHOD_2</code> uses <code>CardStatusUpdate</code> to generate ARPC. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p> <b>Cross-account use</b>: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html">Resource-based policies</a>.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>VerifyCardValidationData</a> </p> </li> <li> <p> <a>VerifyPinData</a> </p> </li> </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/VerifyCardValidationDataCommand.d.ts

@@ -29,7 +29,7 @@ declare const VerifyCardValidationDataCommand_base: {
     };
 };
 /**
- * <p>Verifies card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2) and Card Security Codes (CSC). For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/verify-card-data.html">Verify card data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>This operation validates the CVV or CSC codes that is printed on a payment credit or debit card during card payment transaction. The input values are typically provided as part of an inbound transaction to an issuer or supporting platform partner. Amazon Web Services Payment Cryptography uses CVV or CSC, PAN (Primary Account Number) and expiration date of the card to check its validity during transaction processing. In this operation, the CVK (Card Verification Key) encryption key for use with card data verification is same as the one in used for <a>GenerateCardValidationData</a>. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>GenerateCardValidationData</a> </p> </li> <li> <p> <a>VerifyAuthRequestCryptogram</a> </p> </li> <li> <p> <a>VerifyPinData</a> </p> </li> </ul>
+ * <p>Verifies card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2) and Card Security Codes (CSC). For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/verify-card-data.html">Verify card data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>This operation validates the CVV or CSC codes that is printed on a payment credit or debit card during card payment transaction. The input values are typically provided as part of an inbound transaction to an issuer or supporting platform partner. Amazon Web Services Payment Cryptography uses CVV or CSC, PAN (Primary Account Number) and expiration date of the card to check its validity during transaction processing. In this operation, the CVK (Card Verification Key) encryption key for use with card data verification is same as the one in used for <a>GenerateCardValidationData</a>. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html">Resource-based policies</a>.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>GenerateCardValidationData</a> </p> </li> <li> <p> <a>VerifyAuthRequestCryptogram</a> </p> </li> <li> <p> <a>VerifyPinData</a> </p> </li> </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/VerifyMacCommand.d.ts

@@ -29,7 +29,7 @@ declare const VerifyMacCommand_base: {
     };
 };
 /**
- * <p>Verifies a Message Authentication Code (MAC). </p> <p>You can use this operation to verify MAC for message data authentication such as . In this operation, you must use the same message data, secret encryption key and MAC algorithm that was used to generate MAC. You can use this operation to verify a DUPKT, CMAC, HMAC or EMV MAC by setting generation attributes and algorithm to the associated values. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>GenerateMac</a> </p> </li> </ul>
+ * <p>Verifies a Message Authentication Code (MAC). </p> <p>You can use this operation to verify MAC for message data authentication such as . In this operation, you must use the same message data, secret encryption key and MAC algorithm that was used to generate MAC. You can use this operation to verify a DUPKT, CMAC, HMAC or EMV MAC by setting generation attributes and algorithm to the associated values. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html">Resource-based policies</a>.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>GenerateMac</a> </p> </li> </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/VerifyPinDataCommand.d.ts

@@ -29,7 +29,7 @@ declare const VerifyPinDataCommand_base: {
     };
 };
 /**
- * <p>Verifies pin-related data such as PIN and PIN Offset using algorithms including VISA PVV and IBM3624. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/verify-pin-data.html">Verify PIN data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>This operation verifies PIN data for user payment card. A card holder PIN data is never transmitted in clear to or from Amazon Web Services Payment Cryptography. This operation uses PIN Verification Key (PVK) for PIN or PIN Offset generation and then encrypts it using PIN Encryption Key (PEK) to create an <code>EncryptedPinBlock</code> for transmission from Amazon Web Services Payment Cryptography. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>GeneratePinData</a> </p> </li> <li> <p> <a>TranslatePinData</a> </p> </li> </ul>
+ * <p>Verifies pin-related data such as PIN and PIN Offset using algorithms including VISA PVV and IBM3624. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/verify-pin-data.html">Verify PIN data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>This operation verifies PIN data for user payment card. A card holder PIN data is never transmitted in clear to or from Amazon Web Services Payment Cryptography. This operation uses PIN Verification Key (PVK) for PIN or PIN Offset generation and then encrypts it using PIN Encryption Key (PEK) to create an <code>EncryptedPinBlock</code> for transmission from Amazon Web Services Payment Cryptography. </p> <p>For information about valid keys for this operation, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html">Understanding key attributes</a> and <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html">Key types for specific data operations</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>. </p> <p> <b>Cross-account use</b>: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html">Resource-based policies</a>.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>GeneratePinData</a> </p> </li> <li> <p> <a>TranslatePinData</a> </p> </li> </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/index.d.ts

@@ -1,6 +1,7 @@
 export * from "./DecryptDataCommand";
 export * from "./EncryptDataCommand";
 export * from "./GenerateAs2805KekValidationCommand";
+export * from "./GenerateAuthRequestCryptogramCommand";
 export * from "./GenerateCardValidationDataCommand";
 export * from "./GenerateMacCommand";
 export * from "./GenerateMacEmvPinChangeCommand";

package/dist-types/models/enums.d.ts

@@ -29,6 +29,19 @@ export declare const SymmetricKeyAlgorithm: {
  * @public
  */
 export type SymmetricKeyAlgorithm = (typeof SymmetricKeyAlgorithm)[keyof typeof SymmetricKeyAlgorithm];
+/**
+ * @public
+ * @enum
+ */
+export declare const RandomKeyMaxLength: {
+    readonly BYTES_16: "BYTES_16";
+    readonly BYTES_24: "BYTES_24";
+    readonly BYTES_8: "BYTES_8";
+};
+/**
+ * @public
+ */
+export type RandomKeyMaxLength = (typeof RandomKeyMaxLength)[keyof typeof RandomKeyMaxLength];
 /**
  * @public
  * @enum

package/dist-types/models/models_0.d.ts

@@ -1,4 +1,4 @@
-import type { DukptDerivationType, DukptEncryptionMode, DukptKeyVariant, EmvEncryptionMode, EmvMajorKeyDerivationMode, EncryptionMode, KeyCheckValueAlgorithm, KeyDerivationFunction, KeyDerivationHashAlgorithm, MacAlgorithm, MajorKeyDerivationMode, PaddingType, PinBlockFormatForEmvPinChange, PinBlockFormatForPinData, PinBlockLengthPosition, PinBlockPaddingType, RandomKeySendVariantMask, SessionKeyDerivationMode, SymmetricKeyAlgorithm, WrappedKeyMaterialFormat } from "./enums";
+import type { DukptDerivationType, DukptEncryptionMode, DukptKeyVariant, EmvEncryptionMode, EmvMajorKeyDerivationMode, EncryptionMode, KeyCheckValueAlgorithm, KeyDerivationFunction, KeyDerivationHashAlgorithm, MacAlgorithm, MajorKeyDerivationMode, PaddingType, PinBlockFormatForEmvPinChange, PinBlockFormatForPinData, PinBlockLengthPosition, PinBlockPaddingType, RandomKeyMaxLength, RandomKeySendVariantMask, SessionKeyDerivationMode, SymmetricKeyAlgorithm, WrappedKeyMaterialFormat } from "./enums";
 /**
  * <p>The parameter values of the current PIN to be changed on the EMV chip card.</p>
  * @public
@@ -88,6 +88,11 @@ export interface KekValidationRequest {
      * @public
      */
     DeriveKeyAlgorithm: SymmetricKeyAlgorithm | undefined;
+    /**
+     * <p>The maximum length of the random key to generate for a KEK validation request.</p>
+     * @public
+     */
+    RandomKeyMaxLength?: RandomKeyMaxLength | undefined;
 }
 /**
  * <p>Parameter information for generating a KEK validation response during node-to-node initialization.</p>
@@ -95,7 +100,7 @@ export interface KekValidationRequest {
  */
 export interface KekValidationResponse {
     /**
-     * <p>The random key for generating a KEK validation response.</p>
+     * <p>The random key send value received from the initiating node to generate a KEK validation response.</p>
      * @public
      */
     RandomKeySend: string | undefined;
@@ -1327,7 +1332,7 @@ export interface GenerateAs2805KekValidationInput {
      */
     KeyIdentifier: string | undefined;
     /**
-     * <p>Parameter information for generating a random key for KEK validation to perform node-to-node initialization.</p>
+     * <p>Defines whether to generate a KEK validation request or KEK validation response for node-to-node initialization.</p>
      * @public
      */
     KekValidationType: As2805KekValidationType | undefined;
@@ -1362,6 +1367,244 @@ export interface GenerateAs2805KekValidationOutput {
      */
     RandomKeyReceive: string | undefined;
 }
+/**
+ * <p>Parameters to derive session key for an Amex payment card.</p>
+ * @public
+ */
+export interface SessionKeyAmex {
+    /**
+     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
+     * @public
+     */
+    PrimaryAccountNumber: string | undefined;
+    /**
+     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
+     * @public
+     */
+    PanSequenceNumber: string | undefined;
+}
+/**
+ * <p>Parameters to derive session key for an Emv2000 payment card for ARQC verification.</p>
+ * @public
+ */
+export interface SessionKeyEmv2000 {
+    /**
+     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
+     * @public
+     */
+    PrimaryAccountNumber: string | undefined;
+    /**
+     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
+     * @public
+     */
+    PanSequenceNumber: string | undefined;
+    /**
+     * <p>The transaction counter that is provided by the terminal during transaction processing.</p>
+     * @public
+     */
+    ApplicationTransactionCounter: string | undefined;
+}
+/**
+ * <p>Parameters to derive session key for an Emv common payment card for ARQC verification.</p>
+ * @public
+ */
+export interface SessionKeyEmvCommon {
+    /**
+     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
+     * @public
+     */
+    PrimaryAccountNumber: string | undefined;
+    /**
+     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
+     * @public
+     */
+    PanSequenceNumber: string | undefined;
+    /**
+     * <p>The transaction counter that is provided by the terminal during transaction processing.</p>
+     * @public
+     */
+    ApplicationTransactionCounter: string | undefined;
+}
+/**
+ * <p>Parameters to derive session key for Mastercard payment card for ARQC verification.</p>
+ * @public
+ */
+export interface SessionKeyMastercard {
+    /**
+     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
+     * @public
+     */
+    PrimaryAccountNumber: string | undefined;
+    /**
+     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
+     * @public
+     */
+    PanSequenceNumber: string | undefined;
+    /**
+     * <p>The transaction counter that is provided by the terminal during transaction processing.</p>
+     * @public
+     */
+    ApplicationTransactionCounter: string | undefined;
+    /**
+     * <p>A random number generated by the issuer.</p>
+     * @public
+     */
+    UnpredictableNumber: string | undefined;
+}
+/**
+ * <p>Parameters to derive session key for Visa payment card for ARQC verification.</p>
+ * @public
+ */
+export interface SessionKeyVisa {
+    /**
+     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
+     * @public
+     */
+    PrimaryAccountNumber: string | undefined;
+    /**
+     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
+     * @public
+     */
+    PanSequenceNumber: string | undefined;
+}
+/**
+ * <p>Parameters to derive a session key for Authorization Response Cryptogram (ARQC) verification.</p>
+ * @public
+ */
+export type SessionKeyDerivation = SessionKeyDerivation.AmexMember | SessionKeyDerivation.Emv2000Member | SessionKeyDerivation.EmvCommonMember | SessionKeyDerivation.MastercardMember | SessionKeyDerivation.VisaMember | SessionKeyDerivation.$UnknownMember;
+/**
+ * @public
+ */
+export declare namespace SessionKeyDerivation {
+    /**
+     * <p>Parameters to derive session key for an Emv common payment card for ARQC verification.</p>
+     * @public
+     */
+    interface EmvCommonMember {
+        EmvCommon: SessionKeyEmvCommon;
+        Mastercard?: never;
+        Emv2000?: never;
+        Amex?: never;
+        Visa?: never;
+        $unknown?: never;
+    }
+    /**
+     * <p>Parameters to derive session key for a Mastercard payment card for ARQC verification.</p>
+     * @public
+     */
+    interface MastercardMember {
+        EmvCommon?: never;
+        Mastercard: SessionKeyMastercard;
+        Emv2000?: never;
+        Amex?: never;
+        Visa?: never;
+        $unknown?: never;
+    }
+    /**
+     * <p>Parameters to derive session key for an Emv2000 payment card for ARQC verification.</p>
+     * @public
+     */
+    interface Emv2000Member {
+        EmvCommon?: never;
+        Mastercard?: never;
+        Emv2000: SessionKeyEmv2000;
+        Amex?: never;
+        Visa?: never;
+        $unknown?: never;
+    }
+    /**
+     * <p>Parameters to derive session key for an Amex payment card for ARQC verification.</p>
+     * @public
+     */
+    interface AmexMember {
+        EmvCommon?: never;
+        Mastercard?: never;
+        Emv2000?: never;
+        Amex: SessionKeyAmex;
+        Visa?: never;
+        $unknown?: never;
+    }
+    /**
+     * <p>Parameters to derive session key for a Visa payment cardfor ARQC verification.</p>
+     * @public
+     */
+    interface VisaMember {
+        EmvCommon?: never;
+        Mastercard?: never;
+        Emv2000?: never;
+        Amex?: never;
+        Visa: SessionKeyVisa;
+        $unknown?: never;
+    }
+    /**
+     * @public
+     */
+    interface $UnknownMember {
+        EmvCommon?: never;
+        Mastercard?: never;
+        Emv2000?: never;
+        Amex?: never;
+        Visa?: never;
+        $unknown: [string, any];
+    }
+    /**
+     * @deprecated unused in schema-serde mode.
+     *
+     */
+    interface Visitor<T> {
+        EmvCommon: (value: SessionKeyEmvCommon) => T;
+        Mastercard: (value: SessionKeyMastercard) => T;
+        Emv2000: (value: SessionKeyEmv2000) => T;
+        Amex: (value: SessionKeyAmex) => T;
+        Visa: (value: SessionKeyVisa) => T;
+        _: (name: string, value: any) => T;
+    }
+}
+/**
+ * @public
+ */
+export interface GenerateAuthRequestCryptogramInput {
+    /**
+     * <p>The <code>keyARN</code> of the IMK-AC (TR31_E0_EMV_MKEY_APP_CRYPTOGRAMS) that Amazon Web Services Payment Cryptography uses to generate the ARQC.</p>
+     * @public
+     */
+    KeyIdentifier: string | undefined;
+    /**
+     * <p>The transaction data that Amazon Web Services Payment Cryptography uses for ARQC generation. The same transaction data is used for ARQC verification by the issuer using <a>VerifyAuthRequestCryptogram</a>.</p>
+     * @public
+     */
+    TransactionData: string | undefined;
+    /**
+     * <p>The method to use when deriving the major encryption key for ARQC generation within Amazon Web Services Payment Cryptography.</p>
+     * @public
+     */
+    MajorKeyDerivationMode: MajorKeyDerivationMode | undefined;
+    /**
+     * <p>The attributes and values to use for deriving a session key for ARQC generation within Amazon Web Services Payment Cryptography.</p>
+     * @public
+     */
+    SessionKeyDerivationAttributes: SessionKeyDerivation | undefined;
+}
+/**
+ * @public
+ */
+export interface GenerateAuthRequestCryptogramOutput {
+    /**
+     * <p>The <code>keyARN</code> of the IMK-AC that Amazon Web Services Payment Cryptography uses for ARQC generation.</p>
+     * @public
+     */
+    KeyArn: string | undefined;
+    /**
+     * <p>The key check value (KCV) of the encryption key. The KCV is used to check if all parties holding a given key have the same key or to detect that a key has changed.</p> <p>Amazon Web Services Payment Cryptography computes the KCV according to the CMAC specification.</p>
+     * @public
+     */
+    KeyCheckValue: string | undefined;
+    /**
+     * <p>The Authorization Request Cryptogram (ARQC) generated by Amazon Web Services Payment Cryptography using the specified key and transaction data.</p>
+     * @public
+     */
+    AuthRequestCryptogram: string | undefined;
+}
 /**
  * @public
  */
@@ -2613,199 +2856,6 @@ export interface TranslatePinDataOutput {
      */
     KeyCheckValue: string | undefined;
 }
-/**
- * <p>Parameters to derive session key for an Amex payment card.</p>
- * @public
- */
-export interface SessionKeyAmex {
-    /**
-     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
-     * @public
-     */
-    PrimaryAccountNumber: string | undefined;
-    /**
-     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
-     * @public
-     */
-    PanSequenceNumber: string | undefined;
-}
-/**
- * <p>Parameters to derive session key for an Emv2000 payment card for ARQC verification.</p>
- * @public
- */
-export interface SessionKeyEmv2000 {
-    /**
-     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
-     * @public
-     */
-    PrimaryAccountNumber: string | undefined;
-    /**
-     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
-     * @public
-     */
-    PanSequenceNumber: string | undefined;
-    /**
-     * <p>The transaction counter that is provided by the terminal during transaction processing.</p>
-     * @public
-     */
-    ApplicationTransactionCounter: string | undefined;
-}
-/**
- * <p>Parameters to derive session key for an Emv common payment card for ARQC verification.</p>
- * @public
- */
-export interface SessionKeyEmvCommon {
-    /**
-     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
-     * @public
-     */
-    PrimaryAccountNumber: string | undefined;
-    /**
-     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
-     * @public
-     */
-    PanSequenceNumber: string | undefined;
-    /**
-     * <p>The transaction counter that is provided by the terminal during transaction processing.</p>
-     * @public
-     */
-    ApplicationTransactionCounter: string | undefined;
-}
-/**
- * <p>Parameters to derive session key for Mastercard payment card for ARQC verification.</p>
- * @public
- */
-export interface SessionKeyMastercard {
-    /**
-     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
-     * @public
-     */
-    PrimaryAccountNumber: string | undefined;
-    /**
-     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
-     * @public
-     */
-    PanSequenceNumber: string | undefined;
-    /**
-     * <p>The transaction counter that is provided by the terminal during transaction processing.</p>
-     * @public
-     */
-    ApplicationTransactionCounter: string | undefined;
-    /**
-     * <p>A random number generated by the issuer.</p>
-     * @public
-     */
-    UnpredictableNumber: string | undefined;
-}
-/**
- * <p>Parameters to derive session key for Visa payment card for ARQC verification.</p>
- * @public
- */
-export interface SessionKeyVisa {
-    /**
-     * <p>The Primary Account Number (PAN) of the cardholder. A PAN is a unique identifier for a payment credit or debit card and associates the card to a specific account holder.</p>
-     * @public
-     */
-    PrimaryAccountNumber: string | undefined;
-    /**
-     * <p>A number that identifies and differentiates payment cards with the same Primary Account Number (PAN).</p>
-     * @public
-     */
-    PanSequenceNumber: string | undefined;
-}
-/**
- * <p>Parameters to derive a session key for Authorization Response Cryptogram (ARQC) verification.</p>
- * @public
- */
-export type SessionKeyDerivation = SessionKeyDerivation.AmexMember | SessionKeyDerivation.Emv2000Member | SessionKeyDerivation.EmvCommonMember | SessionKeyDerivation.MastercardMember | SessionKeyDerivation.VisaMember | SessionKeyDerivation.$UnknownMember;
-/**
- * @public
- */
-export declare namespace SessionKeyDerivation {
-    /**
-     * <p>Parameters to derive session key for an Emv common payment card for ARQC verification.</p>
-     * @public
-     */
-    interface EmvCommonMember {
-        EmvCommon: SessionKeyEmvCommon;
-        Mastercard?: never;
-        Emv2000?: never;
-        Amex?: never;
-        Visa?: never;
-        $unknown?: never;
-    }
-    /**
-     * <p>Parameters to derive session key for a Mastercard payment card for ARQC verification.</p>
-     * @public
-     */
-    interface MastercardMember {
-        EmvCommon?: never;
-        Mastercard: SessionKeyMastercard;
-        Emv2000?: never;
-        Amex?: never;
-        Visa?: never;
-        $unknown?: never;
-    }
-    /**
-     * <p>Parameters to derive session key for an Emv2000 payment card for ARQC verification.</p>
-     * @public
-     */
-    interface Emv2000Member {
-        EmvCommon?: never;
-        Mastercard?: never;
-        Emv2000: SessionKeyEmv2000;
-        Amex?: never;
-        Visa?: never;
-        $unknown?: never;
-    }
-    /**
-     * <p>Parameters to derive session key for an Amex payment card for ARQC verification.</p>
-     * @public
-     */
-    interface AmexMember {
-        EmvCommon?: never;
-        Mastercard?: never;
-        Emv2000?: never;
-        Amex: SessionKeyAmex;
-        Visa?: never;
-        $unknown?: never;
-    }
-    /**
-     * <p>Parameters to derive session key for a Visa payment cardfor ARQC verification.</p>
-     * @public
-     */
-    interface VisaMember {
-        EmvCommon?: never;
-        Mastercard?: never;
-        Emv2000?: never;
-        Amex?: never;
-        Visa: SessionKeyVisa;
-        $unknown?: never;
-    }
-    /**
-     * @public
-     */
-    interface $UnknownMember {
-        EmvCommon?: never;
-        Mastercard?: never;
-        Emv2000?: never;
-        Amex?: never;
-        Visa?: never;
-        $unknown: [string, any];
-    }
-    /**
-     * @deprecated unused in schema-serde mode.
-     *
-     */
-    interface Visitor<T> {
-        EmvCommon: (value: SessionKeyEmvCommon) => T;
-        Mastercard: (value: SessionKeyMastercard) => T;
-        Emv2000: (value: SessionKeyEmv2000) => T;
-        Amex: (value: SessionKeyAmex) => T;
-        Visa: (value: SessionKeyVisa) => T;
-        _: (name: string, value: any) => T;
-    }
-}
 /**
  * @public
  */