@aws-sdk/client-payment-cryptography-data 3.1077.0 → 3.1079.0

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { GenerateAs2805KekValidationInput, GenerateAs2805KekValidationOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface GenerateAs2805KekValidationCommandInput extends GenerateAs2805K
 export interface GenerateAs2805KekValidationCommandOutput extends GenerateAs2805KekValidationOutput, __MetadataBearer {
 }
 declare const GenerateAs2805KekValidationCommand_base: {
-    new (input: GenerateAs2805KekValidationCommandInput): import("@smithy/core/client").CommandImpl<GenerateAs2805KekValidationCommandInput, GenerateAs2805KekValidationCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: GenerateAs2805KekValidationCommandInput): import("@smithy/core/client").CommandImpl<GenerateAs2805KekValidationCommandInput, GenerateAs2805KekValidationCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: GenerateAs2805KekValidationCommandInput): import("@smithy/core/client").CommandImpl<GenerateAs2805KekValidationCommandInput, GenerateAs2805KekValidationCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: GenerateAs2805KekValidationCommandInput): import("@smithy/core/client").CommandImpl<GenerateAs2805KekValidationCommandInput, GenerateAs2805KekValidationCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Generates a <code>KekValidationRequest</code> or a <code>KekValidationResponse</code> for node-to-node initialization between payment processing nodes using <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/as2805.html">Australian Standard 2805 (AS2805)</a>.</p> <p>During node-to-node initialization, both communicating nodes must validate that they possess the correct Key Encrypting Keys (KEKs) before proceeding with session key exchange. In AS2805, the sending KEK (KEKs) of one node corresponds to the receiving KEK (KEKr) of its partner node. Each node uses its KEK to encrypt and decrypt session keys exchanged between the nodes. A KEK can be created or imported into Amazon Web Services Payment Cryptography using either the <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> or <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a> operations.</p> <p>To use <code>GenerateAs2805KekValidation</code> to generate a KEK validation request, set <code>KekValidationType</code> to <code>KekValidationRequest</code>. This operation returns both <code>RandomKeySend</code> (KRs) and <code>RandomKeyReceive</code> (KRr) as response values. The partnering node receives the KRs, uses its KEKr to decrypt it, and generates a KRr which is an inverted value of KRs. The node receiving the KRr validates it against its own KRr generated during KEK validation request outside of Amazon Web Services Payment Cryptography.</p> <p>You can also use this operation to generate a KEK validation response, by setting <code>KekValidationType</code> to <code>KekValidationResponse</code> and providing the incoming KRs. This operation then calculates a KRr. To learn more about more about node-to-node initialization, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/as2805.kekvalidation.html">Validation of KEK</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { GenerateAuthRequestCryptogramInput, GenerateAuthRequestCryptogramOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface GenerateAuthRequestCryptogramCommandInput extends GenerateAuthR
 export interface GenerateAuthRequestCryptogramCommandOutput extends GenerateAuthRequestCryptogramOutput, __MetadataBearer {
 }
 declare const GenerateAuthRequestCryptogramCommand_base: {
-    new (input: GenerateAuthRequestCryptogramCommandInput): import("@smithy/core/client").CommandImpl<GenerateAuthRequestCryptogramCommandInput, GenerateAuthRequestCryptogramCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: GenerateAuthRequestCryptogramCommandInput): import("@smithy/core/client").CommandImpl<GenerateAuthRequestCryptogramCommandInput, GenerateAuthRequestCryptogramCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: GenerateAuthRequestCryptogramCommandInput): import("@smithy/core/client").CommandImpl<GenerateAuthRequestCryptogramCommandInput, GenerateAuthRequestCryptogramCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: GenerateAuthRequestCryptogramCommandInput): import("@smithy/core/client").CommandImpl<GenerateAuthRequestCryptogramCommandInput, GenerateAuthRequestCryptogramCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Generates an Authorization Request Cryptogram (ARQC) for an EMV chip payment card authorization. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/data-operations.generateauthrequestcryptogram.html">Generate auth request cryptogram</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>ARQC generation uses an Issuer Master Key (IMK) for application cryptograms (TR31_E0_EMV_MKEY_APP_CRYPTOGRAMS) to derive a session key, which is then used to generate the cryptogram from the provided transaction data (when applicable). To use this operation, you must first create or import an IMK-AC key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> or <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. The <code>KeyModesOfUse</code> should be set to <code>DeriveKey</code> for the IMK-AC encryption key.</p> <important> <p>This operation is intended for development and testing scenarios only. It is not recommended to use this operation as a substitute for card-based cryptogram generation in production payment flows.</p> </important> <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>VerifyAuthRequestCryptogram</a> </p> </li> </ul>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { GenerateCardValidationDataInput, GenerateCardValidationDataOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface GenerateCardValidationDataCommandInput extends GenerateCardVali
 export interface GenerateCardValidationDataCommandOutput extends GenerateCardValidationDataOutput, __MetadataBearer {
 }
 declare const GenerateCardValidationDataCommand_base: {
-    new (input: GenerateCardValidationDataCommandInput): import("@smithy/core/client").CommandImpl<GenerateCardValidationDataCommandInput, GenerateCardValidationDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: GenerateCardValidationDataCommandInput): import("@smithy/core/client").CommandImpl<GenerateCardValidationDataCommandInput, GenerateCardValidationDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: GenerateCardValidationDataCommandInput): import("@smithy/core/client").CommandImpl<GenerateCardValidationDataCommandInput, GenerateCardValidationDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: GenerateCardValidationDataCommandInput): import("@smithy/core/client").CommandImpl<GenerateCardValidationDataCommandInput, GenerateCardValidationDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Generates card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2), or Card Security Codes (CSC). For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/generate-card-data.html">Generate card data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>This operation generates a CVV or CSC value that is printed on a payment credit or debit card during card production. The CVV or CSC, PAN (Primary Account Number) and expiration date of the card are required to check its validity during transaction processing. To begin this operation, a CVK (Card Verification Key) encryption key is required. You can use <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a> or <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a> to establish a CVK within Amazon Web Services Payment Cryptography. The <code>KeyModesOfUse</code> should be set to <code>Generate</code> and <code>Verify</code> for a CVK encryption key. </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_ImportKey.html">ImportKey</a> </p> </li> <li> <p> <a>VerifyCardValidationData</a> </p> </li> </ul>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { GenerateMacInput, GenerateMacOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface GenerateMacCommandInput extends GenerateMacInput {
 export interface GenerateMacCommandOutput extends GenerateMacOutput, __MetadataBearer {
 }
 declare const GenerateMacCommand_base: {
-    new (input: GenerateMacCommandInput): import("@smithy/core/client").CommandImpl<GenerateMacCommandInput, GenerateMacCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: GenerateMacCommandInput): import("@smithy/core/client").CommandImpl<GenerateMacCommandInput, GenerateMacCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: GenerateMacCommandInput): import("@smithy/core/client").CommandImpl<GenerateMacCommandInput, GenerateMacCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: GenerateMacCommandInput): import("@smithy/core/client").CommandImpl<GenerateMacCommandInput, GenerateMacCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Generates a Message Authentication Code (MAC) cryptogram within Amazon Web Services Payment Cryptography. </p> <p>You can use this operation to authenticate card-related data by using known data values to generate MAC for data validation between the sending and receiving parties. This operation uses message data, a secret encryption key and MAC algorithm to generate a unique MAC value for transmission. The receiving party of the MAC must use the same message data, secret encryption key and MAC algorithm to reproduce another MAC value for comparision.</p> <p>You can use this operation to generate a DUPKT, CMAC, HMAC or EMV MAC by setting generation attributes and algorithm to the associated values. The MAC generation encryption key must have valid values for <code>KeyUsage</code> such as <code>TR31_M7_HMAC_KEY</code> for HMAC generation, and the key must have <code>KeyModesOfUse</code> set to <code>Generate</code>.</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>VerifyMac</a> </p> </li> </ul>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { GenerateMacEmvPinChangeInput, GenerateMacEmvPinChangeOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface GenerateMacEmvPinChangeCommandInput extends GenerateMacEmvPinCh
 export interface GenerateMacEmvPinChangeCommandOutput extends GenerateMacEmvPinChangeOutput, __MetadataBearer {
 }
 declare const GenerateMacEmvPinChangeCommand_base: {
-    new (input: GenerateMacEmvPinChangeCommandInput): import("@smithy/core/client").CommandImpl<GenerateMacEmvPinChangeCommandInput, GenerateMacEmvPinChangeCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: GenerateMacEmvPinChangeCommandInput): import("@smithy/core/client").CommandImpl<GenerateMacEmvPinChangeCommandInput, GenerateMacEmvPinChangeCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: GenerateMacEmvPinChangeCommandInput): import("@smithy/core/client").CommandImpl<GenerateMacEmvPinChangeCommandInput, GenerateMacEmvPinChangeCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: GenerateMacEmvPinChangeCommandInput): import("@smithy/core/client").CommandImpl<GenerateMacEmvPinChangeCommandInput, GenerateMacEmvPinChangeCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Generates an issuer script mac for EMV payment cards that use offline PINs as the cardholder verification method (CVM).</p> <p>This operation generates an authenticated issuer script response by appending the incoming message data (APDU command) with the target encrypted PIN block in ISO2 format. The command structure and method to send the issuer script update to the card is not defined by this operation and is typically determined by the applicable payment card scheme.</p> <p>The primary inputs to this operation include the incoming new encrypted pinblock, PIN encryption key (PEK), issuer master key (IMK), primary account number (PAN), and the payment card derivation method.</p> <p>The operation uses two issuer master keys - secure messaging for confidentiality (IMK-SMC) and secure messaging for integrity (IMK-SMI). The SMC key is used to internally derive a key to secure the pin, while SMI key is used to internally derive a key to authenticate the script reponse as per the <a href="https://www.emvco.com/specifications/">EMV 4.4 - Book 2 - Security and Key Management</a> specification. </p> <p>This operation supports Amex, EMV2000, EMVCommon, Mastercard and Visa derivation methods, each requiring specific input parameters. Users must follow the specific derivation method and input parameters defined by the respective payment card scheme.</p> <note> <p>Use <a>GenerateMac</a> operation when sending a script update to an EMV card that does not involve PIN change. When assigning IAM permissions, it is important to understand that <a>EncryptData</a> using EMV keys and <a>GenerateMac</a> perform similar functions to this command.</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>EncryptData</a> </p> </li> <li> <p> <a>GenerateMac</a> </p> </li> </ul>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { GeneratePinDataInput, GeneratePinDataOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface GeneratePinDataCommandInput extends GeneratePinDataInput {
 export interface GeneratePinDataCommandOutput extends GeneratePinDataOutput, __MetadataBearer {
 }
 declare const GeneratePinDataCommand_base: {
-    new (input: GeneratePinDataCommandInput): import("@smithy/core/client").CommandImpl<GeneratePinDataCommandInput, GeneratePinDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: GeneratePinDataCommandInput): import("@smithy/core/client").CommandImpl<GeneratePinDataCommandInput, GeneratePinDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: GeneratePinDataCommandInput): import("@smithy/core/client").CommandImpl<GeneratePinDataCommandInput, GeneratePinDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: GeneratePinDataCommandInput): import("@smithy/core/client").CommandImpl<GeneratePinDataCommandInput, GeneratePinDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <p>Generates pin-related data such as PIN, PIN Verification Value (PVV), PIN Block, and PIN Offset during new card issuance or reissuance. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/generate-pin-data.html">Generate PIN data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>PIN data is never transmitted in clear to or from Amazon Web Services Payment Cryptography. This operation generates PIN, PVV, or PIN Offset and then encrypts it using Pin Encryption Key (PEK) to create an <code>EncryptedPinBlock</code> for transmission from Amazon Web Services Payment Cryptography. This operation uses a separate Pin Verification Key (PVK) for VISA PVV generation. </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. You can also use it for reveal PIN, wherein the generated PIN block is protected by the ECDH derived key before transmission from Amazon Web Services Payment Cryptography. For more information on establishing ECDH derived keys, see the <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/create-keys.html">Generating keys</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</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>TranslatePinData</a> </p> </li> <li> <p> <a>VerifyPinData</a> </p> </li> </ul>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { ReEncryptDataInput, ReEncryptDataOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface ReEncryptDataCommandInput extends ReEncryptDataInput {
 export interface ReEncryptDataCommandOutput extends ReEncryptDataOutput, __MetadataBearer {
 }
 declare const ReEncryptDataCommand_base: {
-    new (input: ReEncryptDataCommandInput): import("@smithy/core/client").CommandImpl<ReEncryptDataCommandInput, ReEncryptDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: ReEncryptDataCommandInput): import("@smithy/core/client").CommandImpl<ReEncryptDataCommandInput, ReEncryptDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: ReEncryptDataCommandInput): import("@smithy/core/client").CommandImpl<ReEncryptDataCommandInput, ReEncryptDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: ReEncryptDataCommandInput): import("@smithy/core/client").CommandImpl<ReEncryptDataCommandInput, ReEncryptDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { TranslateKeyMaterialInput, TranslateKeyMaterialOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface TranslateKeyMaterialCommandInput extends TranslateKeyMaterialIn
 export interface TranslateKeyMaterialCommandOutput extends TranslateKeyMaterialOutput, __MetadataBearer {
 }
 declare const TranslateKeyMaterialCommand_base: {
-    new (input: TranslateKeyMaterialCommandInput): import("@smithy/core/client").CommandImpl<TranslateKeyMaterialCommandInput, TranslateKeyMaterialCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: TranslateKeyMaterialCommandInput): import("@smithy/core/client").CommandImpl<TranslateKeyMaterialCommandInput, TranslateKeyMaterialCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: TranslateKeyMaterialCommandInput): import("@smithy/core/client").CommandImpl<TranslateKeyMaterialCommandInput, TranslateKeyMaterialCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: TranslateKeyMaterialCommandInput): import("@smithy/core/client").CommandImpl<TranslateKeyMaterialCommandInput, TranslateKeyMaterialCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { TranslatePinDataInput, TranslatePinDataOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface TranslatePinDataCommandInput extends TranslatePinDataInput {
 export interface TranslatePinDataCommandOutput extends TranslatePinDataOutput, __MetadataBearer {
 }
 declare const TranslatePinDataCommand_base: {
-    new (input: TranslatePinDataCommandInput): import("@smithy/core/client").CommandImpl<TranslatePinDataCommandInput, TranslatePinDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: TranslatePinDataCommandInput): import("@smithy/core/client").CommandImpl<TranslatePinDataCommandInput, TranslatePinDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: TranslatePinDataCommandInput): import("@smithy/core/client").CommandImpl<TranslatePinDataCommandInput, TranslatePinDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: TranslatePinDataCommandInput): import("@smithy/core/client").CommandImpl<TranslatePinDataCommandInput, TranslatePinDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { VerifyAuthRequestCryptogramInput, VerifyAuthRequestCryptogramOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface VerifyAuthRequestCryptogramCommandInput extends VerifyAuthReque
 export interface VerifyAuthRequestCryptogramCommandOutput extends VerifyAuthRequestCryptogramOutput, __MetadataBearer {
 }
 declare const VerifyAuthRequestCryptogramCommand_base: {
-    new (input: VerifyAuthRequestCryptogramCommandInput): import("@smithy/core/client").CommandImpl<VerifyAuthRequestCryptogramCommandInput, VerifyAuthRequestCryptogramCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: VerifyAuthRequestCryptogramCommandInput): import("@smithy/core/client").CommandImpl<VerifyAuthRequestCryptogramCommandInput, VerifyAuthRequestCryptogramCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: VerifyAuthRequestCryptogramCommandInput): import("@smithy/core/client").CommandImpl<VerifyAuthRequestCryptogramCommandInput, VerifyAuthRequestCryptogramCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: VerifyAuthRequestCryptogramCommandInput): import("@smithy/core/client").CommandImpl<VerifyAuthRequestCryptogramCommandInput, VerifyAuthRequestCryptogramCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { VerifyCardValidationDataInput, VerifyCardValidationDataOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface VerifyCardValidationDataCommandInput extends VerifyCardValidati
 export interface VerifyCardValidationDataCommandOutput extends VerifyCardValidationDataOutput, __MetadataBearer {
 }
 declare const VerifyCardValidationDataCommand_base: {
-    new (input: VerifyCardValidationDataCommandInput): import("@smithy/core/client").CommandImpl<VerifyCardValidationDataCommandInput, VerifyCardValidationDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: VerifyCardValidationDataCommandInput): import("@smithy/core/client").CommandImpl<VerifyCardValidationDataCommandInput, VerifyCardValidationDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: VerifyCardValidationDataCommandInput): import("@smithy/core/client").CommandImpl<VerifyCardValidationDataCommandInput, VerifyCardValidationDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: VerifyCardValidationDataCommandInput): import("@smithy/core/client").CommandImpl<VerifyCardValidationDataCommandInput, VerifyCardValidationDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { VerifyMacInput, VerifyMacOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface VerifyMacCommandInput extends VerifyMacInput {
 export interface VerifyMacCommandOutput extends VerifyMacOutput, __MetadataBearer {
 }
 declare const VerifyMacCommand_base: {
-    new (input: VerifyMacCommandInput): import("@smithy/core/client").CommandImpl<VerifyMacCommandInput, VerifyMacCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: VerifyMacCommandInput): import("@smithy/core/client").CommandImpl<VerifyMacCommandInput, VerifyMacCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: VerifyMacCommandInput): import("@smithy/core/client").CommandImpl<VerifyMacCommandInput, VerifyMacCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: VerifyMacCommandInput): import("@smithy/core/client").CommandImpl<VerifyMacCommandInput, VerifyMacCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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>

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

@@ -1,12 +1,9 @@
-import { Command as $Command } from "@smithy/core/client";
 import type { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import type { VerifyPinDataInput, VerifyPinDataOutput } from "../models/models_0";
-import type { PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../PaymentCryptographyDataClient";
 /**
  * @public
  */
 export type { __MetadataBearer };
-export { $Command };
 /**
  * @public
  *
@@ -22,11 +19,9 @@ export interface VerifyPinDataCommandInput extends VerifyPinDataInput {
 export interface VerifyPinDataCommandOutput extends VerifyPinDataOutput, __MetadataBearer {
 }
 declare const VerifyPinDataCommand_base: {
-    new (input: VerifyPinDataCommandInput): import("@smithy/core/client").CommandImpl<VerifyPinDataCommandInput, VerifyPinDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    new (input: VerifyPinDataCommandInput): import("@smithy/core/client").CommandImpl<VerifyPinDataCommandInput, VerifyPinDataCommandOutput, PaymentCryptographyDataClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes>;
-    getEndpointParameterInstructions(): {
-        [x: string]: unknown;
-    };
+    new (input: VerifyPinDataCommandInput): import("@smithy/core/client").CommandImpl<VerifyPinDataCommandInput, VerifyPinDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    new (input: VerifyPinDataCommandInput): import("@smithy/core/client").CommandImpl<VerifyPinDataCommandInput, VerifyPinDataCommandOutput, import("..").PaymentCryptographyDataClientResolvedConfig, import("..").ServiceInputTypes, import("..").ServiceOutputTypes>;
+    getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 /**
  * <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>

package/dist-types/index.d.ts

@@ -9,6 +9,7 @@ export type { ClientInputEndpointParameters } from "./endpoint/EndpointParameter
 export type { RuntimeExtension } from "./runtimeExtensions";
 export type { PaymentCryptographyDataExtensionConfiguration } from "./extensionConfiguration";
 export * from "./commands";
+export { Command as $Command } from "@smithy/core/client";
 export * from "./schemas/schemas_0";
 export * from "./models/enums";
 export * from "./models/errors";

package/dist-types/ts3.4/commandBuilder.d.ts

@@ -0,0 +1,46 @@
+import { EndpointParameterInstructions } from "@smithy/types";
+import {
+  PaymentCryptographyDataClientResolvedConfig,
+  ServiceInputTypes,
+  ServiceOutputTypes,
+} from "./PaymentCryptographyDataClient";
+export declare const command: <
+  I extends ServiceInputTypes,
+  O extends ServiceOutputTypes
+>(
+  added: EndpointParameterInstructions,
+  plugins: (
+    CommandCtor: any,
+    clientStack: any,
+    config: any,
+    options: any
+  ) => import("@smithy/types").Pluggable<any, any>[],
+  op: string,
+  $: import("@smithy/types").StaticOperationSchema,
+  smithyContext?: Record<string, unknown>
+) => {
+  new (input: I): import("@smithy/core/client").CommandImpl<
+    I,
+    O,
+    PaymentCryptographyDataClientResolvedConfig,
+    ServiceInputTypes,
+    ServiceOutputTypes
+  >;
+  new (
+    ...[input]: import("@smithy/types").OptionalParameter<I>
+  ): import("@smithy/core/client").CommandImpl<
+    I,
+    O,
+    PaymentCryptographyDataClientResolvedConfig,
+    ServiceInputTypes,
+    ServiceOutputTypes
+  >;
+  getEndpointParameterInstructions(): EndpointParameterInstructions;
+};
+export declare const _ep0: EndpointParameterInstructions;
+export declare const _mw0: (
+  Command: any,
+  cs: any,
+  config: any,
+  o: any
+) => never[];

package/dist-types/ts3.4/commands/DecryptDataCommand.d.ts

@@ -1,13 +1,6 @@
-import { Command as $Command } from "@smithy/core/client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import { DecryptDataInput, DecryptDataOutput } from "../models/models_0";
-import {
-  PaymentCryptographyDataClientResolvedConfig,
-  ServiceInputTypes,
-  ServiceOutputTypes,
-} from "../PaymentCryptographyDataClient";
 export { __MetadataBearer };
-export { $Command };
 export interface DecryptDataCommandInput extends DecryptDataInput {}
 export interface DecryptDataCommandOutput
   extends DecryptDataOutput,
@@ -18,22 +11,20 @@ declare const DecryptDataCommand_base: {
   ): import("@smithy/core/client").CommandImpl<
     DecryptDataCommandInput,
     DecryptDataCommandOutput,
-    PaymentCryptographyDataClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").PaymentCryptographyDataClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
   new (
     input: DecryptDataCommandInput
   ): import("@smithy/core/client").CommandImpl<
     DecryptDataCommandInput,
     DecryptDataCommandOutput,
-    PaymentCryptographyDataClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").PaymentCryptographyDataClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
-  getEndpointParameterInstructions(): {
-    [x: string]: unknown;
-  };
+  getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 export declare class DecryptDataCommand extends DecryptDataCommand_base {
   protected static __types: {

package/dist-types/ts3.4/commands/EncryptDataCommand.d.ts

@@ -1,13 +1,6 @@
-import { Command as $Command } from "@smithy/core/client";
 import { MetadataBearer as __MetadataBearer } from "@smithy/types";
 import { EncryptDataInput, EncryptDataOutput } from "../models/models_0";
-import {
-  PaymentCryptographyDataClientResolvedConfig,
-  ServiceInputTypes,
-  ServiceOutputTypes,
-} from "../PaymentCryptographyDataClient";
 export { __MetadataBearer };
-export { $Command };
 export interface EncryptDataCommandInput extends EncryptDataInput {}
 export interface EncryptDataCommandOutput
   extends EncryptDataOutput,
@@ -18,22 +11,20 @@ declare const EncryptDataCommand_base: {
   ): import("@smithy/core/client").CommandImpl<
     EncryptDataCommandInput,
     EncryptDataCommandOutput,
-    PaymentCryptographyDataClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").PaymentCryptographyDataClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
   new (
     input: EncryptDataCommandInput
   ): import("@smithy/core/client").CommandImpl<
     EncryptDataCommandInput,
     EncryptDataCommandOutput,
-    PaymentCryptographyDataClientResolvedConfig,
-    ServiceInputTypes,
-    ServiceOutputTypes
+    import("..").PaymentCryptographyDataClientResolvedConfig,
+    import("..").ServiceInputTypes,
+    import("..").ServiceOutputTypes
   >;
-  getEndpointParameterInstructions(): {
-    [x: string]: unknown;
-  };
+  getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions;
 };
 export declare class EncryptDataCommand extends EncryptDataCommand_base {
   protected static __types: {