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

package/README.md

@@ -202,6 +202,13 @@ GenerateAs2805KekValidation
 </details>
 <details>
 <summary>
+GenerateAuthRequestCryptogram
+</summary>
+
+[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/payment-cryptography-data/command/GenerateAuthRequestCryptogramCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-payment-cryptography-data/Interface/GenerateAuthRequestCryptogramCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-payment-cryptography-data/Interface/GenerateAuthRequestCryptogramCommandOutput/)
+</details>
+<details>
+<summary>
 GenerateCardValidationData
 </summary>
 

package/dist-cjs/index.js

@@ -144,6 +144,18 @@ class GenerateAs2805KekValidationCommand extends client.Command
     .build() {
 }
 
+class GenerateAuthRequestCryptogramCommand extends client.Command
+    .classBuilder()
+    .ep(commonParams)
+    .m(function (Command, cs, config, o) {
+    return [endpoints.getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
+})
+    .s("PaymentCryptographyDataPlane", "GenerateAuthRequestCryptogram", {})
+    .n("PaymentCryptographyDataClient", "GenerateAuthRequestCryptogramCommand")
+    .sc(schemas_0.GenerateAuthRequestCryptogram$)
+    .build() {
+}
+
 class GenerateCardValidationDataCommand extends client.Command
     .classBuilder()
     .ep(commonParams)
@@ -280,6 +292,7 @@ const commands = {
     DecryptDataCommand,
     EncryptDataCommand,
     GenerateAs2805KekValidationCommand,
+    GenerateAuthRequestCryptogramCommand,
     GenerateCardValidationDataCommand,
     GenerateMacCommand,
     GenerateMacEmvPinChangeCommand,
@@ -311,6 +324,11 @@ const SymmetricKeyAlgorithm = {
     TDES_2KEY: "TDES_2KEY",
     TDES_3KEY: "TDES_3KEY",
 };
+const RandomKeyMaxLength = {
+    BYTES_16: "BYTES_16",
+    BYTES_24: "BYTES_24",
+    BYTES_8: "BYTES_8",
+};
 const PaddingType = {
     OAEP_SHA1: "OAEP_SHA1",
     OAEP_SHA256: "OAEP_SHA256",
@@ -431,6 +449,7 @@ exports.EmvMajorKeyDerivationMode = EmvMajorKeyDerivationMode;
 exports.EncryptDataCommand = EncryptDataCommand;
 exports.EncryptionMode = EncryptionMode;
 exports.GenerateAs2805KekValidationCommand = GenerateAs2805KekValidationCommand;
+exports.GenerateAuthRequestCryptogramCommand = GenerateAuthRequestCryptogramCommand;
 exports.GenerateCardValidationDataCommand = GenerateCardValidationDataCommand;
 exports.GenerateMacCommand = GenerateMacCommand;
 exports.GenerateMacEmvPinChangeCommand = GenerateMacEmvPinChangeCommand;
@@ -447,6 +466,7 @@ exports.PinBlockFormatForEmvPinChange = PinBlockFormatForEmvPinChange;
 exports.PinBlockFormatForPinData = PinBlockFormatForPinData;
 exports.PinBlockLengthPosition = PinBlockLengthPosition;
 exports.PinBlockPaddingType = PinBlockPaddingType;
+exports.RandomKeyMaxLength = RandomKeyMaxLength;
 exports.RandomKeySendVariantMask = RandomKeySendVariantMask;
 exports.ReEncryptDataCommand = ReEncryptDataCommand;
 exports.SessionKeyDerivationMode = SessionKeyDerivationMode;

package/dist-cjs/schemas/schemas_0.js

@@ -1,8 +1,8 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.KekValidationRequest$ = exports.IncomingDiffieHellmanTr31KeyBlock$ = exports.Ibm3624RandomPin$ = exports.Ibm3624PinVerification$ = exports.Ibm3624PinOffset$ = exports.Ibm3624PinFromOffset$ = exports.Ibm3624NaturalPin$ = exports.GeneratePinDataOutput$ = exports.GeneratePinDataInput$ = exports.GenerateMacOutput$ = exports.GenerateMacInput$ = exports.GenerateMacEmvPinChangeOutput$ = exports.GenerateMacEmvPinChangeInput$ = exports.GenerateCardValidationDataOutput$ = exports.GenerateCardValidationDataInput$ = exports.GenerateAs2805KekValidationOutput$ = exports.GenerateAs2805KekValidationInput$ = exports.EncryptDataOutput$ = exports.EncryptDataInput$ = exports.EmvEncryptionAttributes$ = exports.EmvCommonAttributes$ = exports.Emv2000Attributes$ = exports.EcdhDerivationAttributes$ = exports.DynamicCardVerificationValue$ = exports.DynamicCardVerificationCode$ = exports.DukptEncryptionAttributes$ = exports.DukptDerivationAttributes$ = exports.DukptAttributes$ = exports.DiscoverDynamicCardVerificationCode$ = exports.DecryptDataOutput$ = exports.DecryptDataInput$ = exports.CurrentPinAttributes$ = exports.CryptogramVerificationArpcMethod2$ = exports.CryptogramVerificationArpcMethod1$ = exports.CardVerificationValue2$ = exports.CardVerificationValue1$ = exports.CardHolderVerificationValue$ = exports.AsymmetricEncryptionAttributes$ = exports.As2805PekDerivationAttributes$ = exports.AmexCardSecurityCodeVersion2$ = exports.AmexCardSecurityCodeVersion1$ = exports.AmexAttributes$ = exports.errorTypeRegistries = exports.VerificationFailedException$ = exports.ValidationException$ = exports.ThrottlingException$ = exports.ResourceNotFoundException$ = exports.InternalServerException$ = exports.AccessDeniedException$ = exports.PaymentCryptographyDataServiceException$ = void 0;
-exports.ReEncryptionAttributes$ = exports.PinVerificationAttributes$ = exports.PinGenerationAttributes$ = exports.PinData$ = exports.OutgoingKeyMaterial$ = exports.MacAttributes$ = exports.IncomingKeyMaterial$ = exports.EncryptionDecryptionAttributes$ = exports.DiffieHellmanDerivationData$ = exports.DerivationMethodAttributes$ = exports.CryptogramAuthResponse$ = exports.CardVerificationAttributes$ = exports.CardGenerationAttributes$ = exports.As2805KekValidationType$ = exports.WrappedWorkingKey$ = exports.WrappedKey$ = exports.VisaPinVerificationValue$ = exports.VisaPinVerification$ = exports.VisaPin$ = exports.VisaAttributes$ = exports.VisaAmexDerivationOutputs$ = exports.VerifyPinDataOutput$ = exports.VerifyPinDataInput$ = exports.VerifyMacOutput$ = exports.VerifyMacInput$ = exports.VerifyCardValidationDataOutput$ = exports.VerifyCardValidationDataInput$ = exports.VerifyAuthRequestCryptogramOutput$ = exports.VerifyAuthRequestCryptogramInput$ = exports.ValidationExceptionField$ = exports.TranslationPinDataIsoFormat1$ = exports.TranslationPinDataIsoFormat034$ = exports.TranslationPinDataAs2805Format0$ = exports.TranslatePinDataOutput$ = exports.TranslatePinDataInput$ = exports.TranslateKeyMaterialOutput$ = exports.TranslateKeyMaterialInput$ = exports.SymmetricEncryptionAttributes$ = exports.SessionKeyVisa$ = exports.SessionKeyMastercard$ = exports.SessionKeyEmvCommon$ = exports.SessionKeyEmv2000$ = exports.SessionKeyAmex$ = exports.ReEncryptDataOutput$ = exports.ReEncryptDataInput$ = exports.OutgoingTr31KeyBlock$ = exports.MasterCardAttributes$ = exports.MacAlgorithmEmv$ = exports.MacAlgorithmDukpt$ = exports.KekValidationResponse$ = void 0;
-exports.VerifyPinData$ = exports.VerifyMac$ = exports.VerifyCardValidationData$ = exports.VerifyAuthRequestCryptogram$ = exports.TranslatePinData$ = exports.TranslateKeyMaterial$ = exports.ReEncryptData$ = exports.GeneratePinData$ = exports.GenerateMacEmvPinChange$ = exports.GenerateMac$ = exports.GenerateCardValidationData$ = exports.GenerateAs2805KekValidation$ = exports.EncryptData$ = exports.DecryptData$ = exports.WrappedKeyMaterial$ = exports.TranslationIsoFormats$ = exports.SessionKeyDerivationValue$ = exports.SessionKeyDerivation$ = void 0;
+exports.Ibm3624RandomPin$ = exports.Ibm3624PinVerification$ = exports.Ibm3624PinOffset$ = exports.Ibm3624PinFromOffset$ = exports.Ibm3624NaturalPin$ = exports.GeneratePinDataOutput$ = exports.GeneratePinDataInput$ = exports.GenerateMacOutput$ = exports.GenerateMacInput$ = exports.GenerateMacEmvPinChangeOutput$ = exports.GenerateMacEmvPinChangeInput$ = exports.GenerateCardValidationDataOutput$ = exports.GenerateCardValidationDataInput$ = exports.GenerateAuthRequestCryptogramOutput$ = exports.GenerateAuthRequestCryptogramInput$ = exports.GenerateAs2805KekValidationOutput$ = exports.GenerateAs2805KekValidationInput$ = exports.EncryptDataOutput$ = exports.EncryptDataInput$ = exports.EmvEncryptionAttributes$ = exports.EmvCommonAttributes$ = exports.Emv2000Attributes$ = exports.EcdhDerivationAttributes$ = exports.DynamicCardVerificationValue$ = exports.DynamicCardVerificationCode$ = exports.DukptEncryptionAttributes$ = exports.DukptDerivationAttributes$ = exports.DukptAttributes$ = exports.DiscoverDynamicCardVerificationCode$ = exports.DecryptDataOutput$ = exports.DecryptDataInput$ = exports.CurrentPinAttributes$ = exports.CryptogramVerificationArpcMethod2$ = exports.CryptogramVerificationArpcMethod1$ = exports.CardVerificationValue2$ = exports.CardVerificationValue1$ = exports.CardHolderVerificationValue$ = exports.AsymmetricEncryptionAttributes$ = exports.As2805PekDerivationAttributes$ = exports.AmexCardSecurityCodeVersion2$ = exports.AmexCardSecurityCodeVersion1$ = exports.AmexAttributes$ = exports.errorTypeRegistries = exports.VerificationFailedException$ = exports.ValidationException$ = exports.ThrottlingException$ = exports.ResourceNotFoundException$ = exports.InternalServerException$ = exports.AccessDeniedException$ = exports.PaymentCryptographyDataServiceException$ = void 0;
+exports.PinGenerationAttributes$ = exports.PinData$ = exports.OutgoingKeyMaterial$ = exports.MacAttributes$ = exports.IncomingKeyMaterial$ = exports.EncryptionDecryptionAttributes$ = exports.DiffieHellmanDerivationData$ = exports.DerivationMethodAttributes$ = exports.CryptogramAuthResponse$ = exports.CardVerificationAttributes$ = exports.CardGenerationAttributes$ = exports.As2805KekValidationType$ = exports.WrappedWorkingKey$ = exports.WrappedKey$ = exports.VisaPinVerificationValue$ = exports.VisaPinVerification$ = exports.VisaPin$ = exports.VisaAttributes$ = exports.VisaAmexDerivationOutputs$ = exports.VerifyPinDataOutput$ = exports.VerifyPinDataInput$ = exports.VerifyMacOutput$ = exports.VerifyMacInput$ = exports.VerifyCardValidationDataOutput$ = exports.VerifyCardValidationDataInput$ = exports.VerifyAuthRequestCryptogramOutput$ = exports.VerifyAuthRequestCryptogramInput$ = exports.ValidationExceptionField$ = exports.TranslationPinDataIsoFormat1$ = exports.TranslationPinDataIsoFormat034$ = exports.TranslationPinDataAs2805Format0$ = exports.TranslatePinDataOutput$ = exports.TranslatePinDataInput$ = exports.TranslateKeyMaterialOutput$ = exports.TranslateKeyMaterialInput$ = exports.SymmetricEncryptionAttributes$ = exports.SessionKeyVisa$ = exports.SessionKeyMastercard$ = exports.SessionKeyEmvCommon$ = exports.SessionKeyEmv2000$ = exports.SessionKeyAmex$ = exports.ReEncryptDataOutput$ = exports.ReEncryptDataInput$ = exports.OutgoingTr31KeyBlock$ = exports.MasterCardAttributes$ = exports.MacAlgorithmEmv$ = exports.MacAlgorithmDukpt$ = exports.KekValidationResponse$ = exports.KekValidationRequest$ = exports.IncomingDiffieHellmanTr31KeyBlock$ = void 0;
+exports.VerifyPinData$ = exports.VerifyMac$ = exports.VerifyCardValidationData$ = exports.VerifyAuthRequestCryptogram$ = exports.TranslatePinData$ = exports.TranslateKeyMaterial$ = exports.ReEncryptData$ = exports.GeneratePinData$ = exports.GenerateMacEmvPinChange$ = exports.GenerateMac$ = exports.GenerateCardValidationData$ = exports.GenerateAuthRequestCryptogram$ = exports.GenerateAs2805KekValidation$ = exports.EncryptData$ = exports.DecryptData$ = exports.WrappedKeyMaterial$ = exports.TranslationIsoFormats$ = exports.SessionKeyDerivationValue$ = exports.SessionKeyDerivation$ = exports.ReEncryptionAttributes$ = exports.PinVerificationAttributes$ = void 0;
 const _A = "Amex";
 const _AA = "AmexAttributes";
 const _AC = "ApplicationCryptogram";
@@ -97,6 +97,9 @@ const _GA = "GenerationAttributes";
 const _GAKV = "GenerateAs2805KekValidation";
 const _GAKVI = "GenerateAs2805KekValidationInput";
 const _GAKVO = "GenerateAs2805KekValidationOutput";
+const _GARC = "GenerateAuthRequestCryptogram";
+const _GARCI = "GenerateAuthRequestCryptogramInput";
+const _GARCO = "GenerateAuthRequestCryptogramOutput";
 const _GCVD = "GenerateCardValidationData";
 const _GCVDI = "GenerateCardValidationDataInput";
 const _GCVDO = "GenerateCardValidationDataOutput";
@@ -204,6 +207,7 @@ const _RED = "ReEncryptData";
 const _REDI = "ReEncryptDataInput";
 const _REDO = "ReEncryptDataOutput";
 const _RI = "ResourceId";
+const _RKML = "RandomKeyMaxLength";
 const _RKR = "RandomKeyReceive";
 const _RKS = "RandomKeySend";
 const _RKSVM = "RandomKeySendVariantMask";
@@ -509,6 +513,16 @@ exports.GenerateAs2805KekValidationOutput$ = [3, n0, _GAKVO,
     [_KA, _KCV, _RKS, _RKR],
     [0, 0, [() => As2805RandomKeyMaterial, 0], [() => As2805RandomKeyMaterial, 0]], 4
 ];
+exports.GenerateAuthRequestCryptogramInput$ = [3, n0, _GARCI,
+    0,
+    [_KI, _TDr, _MKDM, _SKDA],
+    [0, [() => TransactionDataType, 0], 0, [() => exports.SessionKeyDerivation$, 0]], 4
+];
+exports.GenerateAuthRequestCryptogramOutput$ = [3, n0, _GARCO,
+    0,
+    [_KA, _KCV, _ARCu],
+    [0, 0, [() => AuthRequestCryptogramType, 0]], 3
+];
 exports.GenerateCardValidationDataInput$ = [3, n0, _GCVDI,
     0,
     [_KI, _PAN, _GA, _VDL],
@@ -581,8 +595,8 @@ exports.IncomingDiffieHellmanTr31KeyBlock$ = [3, n0, _IDHTKB,
 ];
 exports.KekValidationRequest$ = [3, n0, _KVR,
     0,
-    [_DKA],
-    [0], 1
+    [_DKA, _RKML],
+    [0, 0], 1
 ];
 exports.KekValidationResponse$ = [3, n0, _KVRe,
     0,
@@ -866,6 +880,9 @@ exports.EncryptData$ = [9, n0, _ED,
 exports.GenerateAs2805KekValidation$ = [9, n0, _GAKV,
     { [_h]: ["POST", "/as2805kekvalidation/generate", 200] }, () => exports.GenerateAs2805KekValidationInput$, () => exports.GenerateAs2805KekValidationOutput$
 ];
+exports.GenerateAuthRequestCryptogram$ = [9, n0, _GARC,
+    { [_h]: ["POST", "/cryptogram/generate", 200] }, () => exports.GenerateAuthRequestCryptogramInput$, () => exports.GenerateAuthRequestCryptogramOutput$
+];
 exports.GenerateCardValidationData$ = [9, n0, _GCVD,
     { [_h]: ["POST", "/cardvalidationdata/generate", 200] }, () => exports.GenerateCardValidationDataInput$, () => exports.GenerateCardValidationDataOutput$
 ];

package/dist-es/PaymentCryptographyData.js

@@ -2,6 +2,7 @@ import { createAggregatedClient } from "@smithy/core/client";
 import { DecryptDataCommand, } from "./commands/DecryptDataCommand";
 import { EncryptDataCommand, } from "./commands/EncryptDataCommand";
 import { GenerateAs2805KekValidationCommand, } from "./commands/GenerateAs2805KekValidationCommand";
+import { GenerateAuthRequestCryptogramCommand, } from "./commands/GenerateAuthRequestCryptogramCommand";
 import { GenerateCardValidationDataCommand, } from "./commands/GenerateCardValidationDataCommand";
 import { GenerateMacCommand, } from "./commands/GenerateMacCommand";
 import { GenerateMacEmvPinChangeCommand, } from "./commands/GenerateMacEmvPinChangeCommand";
@@ -18,6 +19,7 @@ const commands = {
     DecryptDataCommand,
     EncryptDataCommand,
     GenerateAs2805KekValidationCommand,
+    GenerateAuthRequestCryptogramCommand,
     GenerateCardValidationDataCommand,
     GenerateMacCommand,
     GenerateMacEmvPinChangeCommand,

package/dist-es/commands/GenerateAuthRequestCryptogramCommand.js

@@ -0,0 +1,16 @@
+import { Command as $Command } from "@smithy/core/client";
+import { getEndpointPlugin } from "@smithy/core/endpoints";
+import { commonParams } from "../endpoint/EndpointParameters";
+import { GenerateAuthRequestCryptogram$ } from "../schemas/schemas_0";
+export { $Command };
+export class GenerateAuthRequestCryptogramCommand extends $Command
+    .classBuilder()
+    .ep(commonParams)
+    .m(function (Command, cs, config, o) {
+    return [getEndpointPlugin(config, Command.getEndpointParameterInstructions())];
+})
+    .s("PaymentCryptographyDataPlane", "GenerateAuthRequestCryptogram", {})
+    .n("PaymentCryptographyDataClient", "GenerateAuthRequestCryptogramCommand")
+    .sc(GenerateAuthRequestCryptogram$)
+    .build() {
+}

package/dist-es/commands/index.js

@@ -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-es/models/enums.js

@@ -13,6 +13,11 @@ export const SymmetricKeyAlgorithm = {
     TDES_2KEY: "TDES_2KEY",
     TDES_3KEY: "TDES_3KEY",
 };
+export const RandomKeyMaxLength = {
+    BYTES_16: "BYTES_16",
+    BYTES_24: "BYTES_24",
+    BYTES_8: "BYTES_8",
+};
 export const PaddingType = {
     OAEP_SHA1: "OAEP_SHA1",
     OAEP_SHA256: "OAEP_SHA256",

package/dist-es/schemas/schemas_0.js

@@ -92,6 +92,9 @@ const _GA = "GenerationAttributes";
 const _GAKV = "GenerateAs2805KekValidation";
 const _GAKVI = "GenerateAs2805KekValidationInput";
 const _GAKVO = "GenerateAs2805KekValidationOutput";
+const _GARC = "GenerateAuthRequestCryptogram";
+const _GARCI = "GenerateAuthRequestCryptogramInput";
+const _GARCO = "GenerateAuthRequestCryptogramOutput";
 const _GCVD = "GenerateCardValidationData";
 const _GCVDI = "GenerateCardValidationDataInput";
 const _GCVDO = "GenerateCardValidationDataOutput";
@@ -199,6 +202,7 @@ const _RED = "ReEncryptData";
 const _REDI = "ReEncryptDataInput";
 const _REDO = "ReEncryptDataOutput";
 const _RI = "ResourceId";
+const _RKML = "RandomKeyMaxLength";
 const _RKR = "RandomKeyReceive";
 const _RKS = "RandomKeySend";
 const _RKSVM = "RandomKeySendVariantMask";
@@ -504,6 +508,16 @@ export var GenerateAs2805KekValidationOutput$ = [3, n0, _GAKVO,
     [_KA, _KCV, _RKS, _RKR],
     [0, 0, [() => As2805RandomKeyMaterial, 0], [() => As2805RandomKeyMaterial, 0]], 4
 ];
+export var GenerateAuthRequestCryptogramInput$ = [3, n0, _GARCI,
+    0,
+    [_KI, _TDr, _MKDM, _SKDA],
+    [0, [() => TransactionDataType, 0], 0, [() => SessionKeyDerivation$, 0]], 4
+];
+export var GenerateAuthRequestCryptogramOutput$ = [3, n0, _GARCO,
+    0,
+    [_KA, _KCV, _ARCu],
+    [0, 0, [() => AuthRequestCryptogramType, 0]], 3
+];
 export var GenerateCardValidationDataInput$ = [3, n0, _GCVDI,
     0,
     [_KI, _PAN, _GA, _VDL],
@@ -576,8 +590,8 @@ export var IncomingDiffieHellmanTr31KeyBlock$ = [3, n0, _IDHTKB,
 ];
 export var KekValidationRequest$ = [3, n0, _KVR,
     0,
-    [_DKA],
-    [0], 1
+    [_DKA, _RKML],
+    [0, 0], 1
 ];
 export var KekValidationResponse$ = [3, n0, _KVRe,
     0,
@@ -861,6 +875,9 @@ export var EncryptData$ = [9, n0, _ED,
 export var GenerateAs2805KekValidation$ = [9, n0, _GAKV,
     { [_h]: ["POST", "/as2805kekvalidation/generate", 200] }, () => GenerateAs2805KekValidationInput$, () => GenerateAs2805KekValidationOutput$
 ];
+export var GenerateAuthRequestCryptogram$ = [9, n0, _GARC,
+    { [_h]: ["POST", "/cryptogram/generate", 200] }, () => GenerateAuthRequestCryptogramInput$, () => GenerateAuthRequestCryptogramOutput$
+];
 export var GenerateCardValidationData$ = [9, n0, _GCVD,
     { [_h]: ["POST", "/cardvalidationdata/generate", 200] }, () => GenerateCardValidationDataInput$, () => GenerateCardValidationDataOutput$
 ];

package/dist-types/PaymentCryptographyData.d.ts

@@ -2,6 +2,7 @@ import type { HttpHandlerOptions as __HttpHandlerOptions } from "@smithy/types";
 import { type DecryptDataCommandInput, type DecryptDataCommandOutput } from "./commands/DecryptDataCommand";
 import { type EncryptDataCommandInput, type EncryptDataCommandOutput } from "./commands/EncryptDataCommand";
 import { type GenerateAs2805KekValidationCommandInput, type GenerateAs2805KekValidationCommandOutput } from "./commands/GenerateAs2805KekValidationCommand";
+import { type GenerateAuthRequestCryptogramCommandInput, type GenerateAuthRequestCryptogramCommandOutput } from "./commands/GenerateAuthRequestCryptogramCommand";
 import { type GenerateCardValidationDataCommandInput, type GenerateCardValidationDataCommandOutput } from "./commands/GenerateCardValidationDataCommand";
 import { type GenerateMacCommandInput, type GenerateMacCommandOutput } from "./commands/GenerateMacCommand";
 import { type GenerateMacEmvPinChangeCommandInput, type GenerateMacEmvPinChangeCommandOutput } from "./commands/GenerateMacEmvPinChangeCommand";
@@ -33,6 +34,12 @@ export interface PaymentCryptographyData {
     generateAs2805KekValidation(args: GenerateAs2805KekValidationCommandInput, options?: __HttpHandlerOptions): Promise<GenerateAs2805KekValidationCommandOutput>;
     generateAs2805KekValidation(args: GenerateAs2805KekValidationCommandInput, cb: (err: any, data?: GenerateAs2805KekValidationCommandOutput) => void): void;
     generateAs2805KekValidation(args: GenerateAs2805KekValidationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GenerateAs2805KekValidationCommandOutput) => void): void;
+    /**
+     * @see {@link GenerateAuthRequestCryptogramCommand}
+     */
+    generateAuthRequestCryptogram(args: GenerateAuthRequestCryptogramCommandInput, options?: __HttpHandlerOptions): Promise<GenerateAuthRequestCryptogramCommandOutput>;
+    generateAuthRequestCryptogram(args: GenerateAuthRequestCryptogramCommandInput, cb: (err: any, data?: GenerateAuthRequestCryptogramCommandOutput) => void): void;
+    generateAuthRequestCryptogram(args: GenerateAuthRequestCryptogramCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GenerateAuthRequestCryptogramCommandOutput) => void): void;
     /**
      * @see {@link GenerateCardValidationDataCommand}
      */

package/dist-types/PaymentCryptographyDataClient.d.ts

@@ -9,6 +9,7 @@ import { type HttpAuthSchemeInputConfig, type HttpAuthSchemeResolvedConfig } fro
 import type { DecryptDataCommandInput, DecryptDataCommandOutput } from "./commands/DecryptDataCommand";
 import type { EncryptDataCommandInput, EncryptDataCommandOutput } from "./commands/EncryptDataCommand";
 import type { GenerateAs2805KekValidationCommandInput, GenerateAs2805KekValidationCommandOutput } from "./commands/GenerateAs2805KekValidationCommand";
+import type { GenerateAuthRequestCryptogramCommandInput, GenerateAuthRequestCryptogramCommandOutput } from "./commands/GenerateAuthRequestCryptogramCommand";
 import type { GenerateCardValidationDataCommandInput, GenerateCardValidationDataCommandOutput } from "./commands/GenerateCardValidationDataCommand";
 import type { GenerateMacCommandInput, GenerateMacCommandOutput } from "./commands/GenerateMacCommand";
 import type { GenerateMacEmvPinChangeCommandInput, GenerateMacEmvPinChangeCommandOutput } from "./commands/GenerateMacEmvPinChangeCommand";
@@ -26,11 +27,11 @@ export { __Client };
 /**
  * @public
  */
-export type ServiceInputTypes = DecryptDataCommandInput | EncryptDataCommandInput | GenerateAs2805KekValidationCommandInput | GenerateCardValidationDataCommandInput | GenerateMacCommandInput | GenerateMacEmvPinChangeCommandInput | GeneratePinDataCommandInput | ReEncryptDataCommandInput | TranslateKeyMaterialCommandInput | TranslatePinDataCommandInput | VerifyAuthRequestCryptogramCommandInput | VerifyCardValidationDataCommandInput | VerifyMacCommandInput | VerifyPinDataCommandInput;
+export type ServiceInputTypes = DecryptDataCommandInput | EncryptDataCommandInput | GenerateAs2805KekValidationCommandInput | GenerateAuthRequestCryptogramCommandInput | GenerateCardValidationDataCommandInput | GenerateMacCommandInput | GenerateMacEmvPinChangeCommandInput | GeneratePinDataCommandInput | ReEncryptDataCommandInput | TranslateKeyMaterialCommandInput | TranslatePinDataCommandInput | VerifyAuthRequestCryptogramCommandInput | VerifyCardValidationDataCommandInput | VerifyMacCommandInput | VerifyPinDataCommandInput;
 /**
  * @public
  */
-export type ServiceOutputTypes = DecryptDataCommandOutput | EncryptDataCommandOutput | GenerateAs2805KekValidationCommandOutput | GenerateCardValidationDataCommandOutput | GenerateMacCommandOutput | GenerateMacEmvPinChangeCommandOutput | GeneratePinDataCommandOutput | ReEncryptDataCommandOutput | TranslateKeyMaterialCommandOutput | TranslatePinDataCommandOutput | VerifyAuthRequestCryptogramCommandOutput | VerifyCardValidationDataCommandOutput | VerifyMacCommandOutput | VerifyPinDataCommandOutput;
+export type ServiceOutputTypes = DecryptDataCommandOutput | EncryptDataCommandOutput | GenerateAs2805KekValidationCommandOutput | GenerateAuthRequestCryptogramCommandOutput | GenerateCardValidationDataCommandOutput | GenerateMacCommandOutput | GenerateMacEmvPinChangeCommandOutput | GeneratePinDataCommandOutput | ReEncryptDataCommandOutput | TranslateKeyMaterialCommandOutput | TranslatePinDataCommandOutput | VerifyAuthRequestCryptogramCommandOutput | VerifyCardValidationDataCommandOutput | VerifyMacCommandOutput | VerifyPinDataCommandOutput;
 /**
  * @public
  */

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

@@ -29,7 +29,7 @@ declare const DecryptDataCommand_base: {
     };
 };
 /**
- * <p>Decrypts ciphertext data to plaintext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/decrypt-data.html">Decrypt data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>You can use an decryption key generated within Amazon Web Services Payment Cryptography, or you can import your own decryption key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. For this operation, the key must have <code>KeyModesOfUse</code> set to <code>Decrypt</code>. In asymmetric decryption, Amazon Web Services Payment Cryptography decrypts the ciphertext using the private component of the asymmetric encryption key pair. For data encryption outside of Amazon Web Services Payment Cryptography, you can export the public component of the asymmetric key pair by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html">GetPublicCertificate</a>.</p> <p>This operation also supports dynamic keys, allowing you to pass a dynamic decryption 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 decrypt using dynamic keys, the <code>keyARN</code> is the Key Encryption Key (KEK) of the TR-31 wrapped decryption 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 decryption, Amazon Web Services Payment Cryptography supports <code>TDES</code> and <code>AES</code> algorithms. For EMV decryption, Amazon Web Services Payment Cryptography supports <code>TDES</code> algorithms. For asymmetric decryption, Amazon Web Services Payment Cryptography supports <code>RSA</code>. </p> <p>When you use TDES or TDES DUKPT, the ciphertext data length must be a multiple of 8 bytes. For AES or AES DUKPT, the ciphertext data length must be a multiple of 16 bytes. For RSA, it sould be equal to the key size unless padding is enabled.</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>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>Decrypts ciphertext data to plaintext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/decrypt-data.html">Decrypt data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>You can use an decryption key generated within Amazon Web Services Payment Cryptography, or you can import your own decryption key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. For this operation, the key must have <code>KeyModesOfUse</code> set to <code>Decrypt</code>. In asymmetric decryption, Amazon Web Services Payment Cryptography decrypts the ciphertext using the private component of the asymmetric encryption key pair. For data encryption outside of Amazon Web Services Payment Cryptography, you can export the public component of the asymmetric key pair by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html">GetPublicCertificate</a>.</p> <p>This operation also supports dynamic keys, allowing you to pass a dynamic decryption 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 decrypt using dynamic keys, the <code>keyARN</code> is the Key Encryption Key (KEK) of the TR-31 wrapped decryption 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 decryption, Amazon Web Services Payment Cryptography supports <code>TDES</code> and <code>AES</code> algorithms. For EMV decryption, Amazon Web Services Payment Cryptography supports <code>TDES</code> algorithms. For asymmetric decryption, Amazon Web Services Payment Cryptography supports <code>RSA</code>. </p> <p>When you use TDES or TDES DUKPT, the ciphertext data length must be a multiple of 8 bytes. For AES or AES DUKPT, the ciphertext data length must be a multiple of 16 bytes. For RSA, it sould be equal to the key size unless padding is enabled.</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>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/EncryptDataCommand.d.ts

@@ -29,7 +29,7 @@ declare const EncryptDataCommand_base: {
     };
 };
 /**
- * <p>Encrypts plaintext data to ciphertext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/encrypt-data.html">Encrypt data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>You can 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>. You can import your own encryption key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>.</p> <p>For this operation, the key must have <code>KeyModesOfUse</code> set to <code>Encrypt</code>. In asymmetric encryption, plaintext is encrypted using public component. You can import the public component of an asymmetric key pair created outside Amazon Web Services Payment Cryptography by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. </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 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. For EMV encryption, Amazon Web Services Payment Cryptography supports <code>TDES</code> algorithms.For asymmetric encryption, Amazon Web Services Payment Cryptography supports <code>RSA</code>. </p> <p>When you use TDES or TDES DUKPT, the plaintext data length must be a multiple of 8 bytes. For AES or AES DUKPT, the plaintext data length must be a multiple of 16 bytes. For RSA, it sould be equal to the key size unless padding is enabled.</p> <p>To encrypt using DUKPT, you must already have a BDK (Base Derivation Key) key in your account with <code>KeyModesOfUse</code> set to <code>DeriveKey</code>, or you can generate a new DUKPT key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a>. To encrypt using EMV, you must already have an IMK (Issuer Master Key) key in your account with <code>KeyModesOfUse</code> set to <code>DeriveKey</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 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 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> <li> <p> <a>ReEncryptData</a> </p> </li> </ul>
+ * <p>Encrypts plaintext data to ciphertext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme. For more information, see <a href="https://docs.aws.amazon.com/payment-cryptography/latest/userguide/encrypt-data.html">Encrypt data</a> in the <i>Amazon Web Services Payment Cryptography User Guide</i>.</p> <p>You can 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>. You can import your own encryption key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>.</p> <p>For this operation, the key must have <code>KeyModesOfUse</code> set to <code>Encrypt</code>. In asymmetric encryption, plaintext is encrypted using public component. You can import the public component of an asymmetric key pair created outside Amazon Web Services Payment Cryptography by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html">ImportKey</a>. </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 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. For EMV encryption, Amazon Web Services Payment Cryptography supports <code>TDES</code> algorithms.For asymmetric encryption, Amazon Web Services Payment Cryptography supports <code>RSA</code>. </p> <p>When you use TDES or TDES DUKPT, the plaintext data length must be a multiple of 8 bytes. For AES or AES DUKPT, the plaintext data length must be a multiple of 16 bytes. For RSA, it sould be equal to the key size unless padding is enabled.</p> <p>To encrypt using DUKPT, you must already have a BDK (Base Derivation Key) key in your account with <code>KeyModesOfUse</code> set to <code>DeriveKey</code>, or you can generate a new DUKPT key by calling <a href="https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html">CreateKey</a>. To encrypt using EMV, you must already have an IMK (Issuer Master Key) key in your account with <code>KeyModesOfUse</code> set to <code>DeriveKey</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>DecryptData</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> <li> <p> <a>ReEncryptData</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/GenerateAs2805KekValidationCommand.d.ts

@@ -29,7 +29,7 @@ declare const GenerateAs2805KekValidationCommand_base: {
     };
 };
 /**
- * <p>Establishes node-to-node initialization between payment processing nodes such as an acquirer, issuer or payment network using Australian Standard 2805 (AS2805).</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>The node initiating communication can use <code>GenerateAS2805KekValidation</code> to generate a combined KEK validation request and KEK validation response to send to the partnering node for validation. When invoked, the API internally generates a random sending key encrypted under KEKs and provides a receiving key encrypted under KEKr as response. The initiating node sends the response returned by this API to its partner for validation.</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>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>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -43,6 +43,7 @@ declare const GenerateAs2805KekValidationCommand_base: {
  *   KekValidationType: { // As2805KekValidationType Union: only one key present
  *     KekValidationRequest: { // KekValidationRequest
  *       DeriveKeyAlgorithm: "TDES_2KEY" || "TDES_3KEY" || "AES_128" || "AES_192" || "AES_256" || "HMAC_SHA256" || "HMAC_SHA384" || "HMAC_SHA512" || "HMAC_SHA224", // required
+ *       RandomKeyMaxLength: "BYTES_8" || "BYTES_16" || "BYTES_24",
  *     },
  *     KekValidationResponse: { // KekValidationResponse
  *       RandomKeySend: "STRING_VALUE", // required

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

@@ -0,0 +1,121 @@
+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
+ *
+ * The input for {@link GenerateAuthRequestCryptogramCommand}.
+ */
+export interface GenerateAuthRequestCryptogramCommandInput extends GenerateAuthRequestCryptogramInput {
+}
+/**
+ * @public
+ *
+ * The output of {@link GenerateAuthRequestCryptogramCommand}.
+ */
+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;
+    };
+};
+/**
+ * <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>
+ * @example
+ * Use a bare-bones client and the command you need to make an API call.
+ * ```javascript
+ * import { PaymentCryptographyDataClient, GenerateAuthRequestCryptogramCommand } from "@aws-sdk/client-payment-cryptography-data"; // ES Modules import
+ * // const { PaymentCryptographyDataClient, GenerateAuthRequestCryptogramCommand } = require("@aws-sdk/client-payment-cryptography-data"); // CommonJS import
+ * // import type { PaymentCryptographyDataClientConfig } from "@aws-sdk/client-payment-cryptography-data";
+ * const config = {}; // type is PaymentCryptographyDataClientConfig
+ * const client = new PaymentCryptographyDataClient(config);
+ * const input = { // GenerateAuthRequestCryptogramInput
+ *   KeyIdentifier: "STRING_VALUE", // required
+ *   TransactionData: "STRING_VALUE", // required
+ *   MajorKeyDerivationMode: "EMV_OPTION_A" || "EMV_OPTION_B", // required
+ *   SessionKeyDerivationAttributes: { // SessionKeyDerivation Union: only one key present
+ *     EmvCommon: { // SessionKeyEmvCommon
+ *       PrimaryAccountNumber: "STRING_VALUE", // required
+ *       PanSequenceNumber: "STRING_VALUE", // required
+ *       ApplicationTransactionCounter: "STRING_VALUE", // required
+ *     },
+ *     Mastercard: { // SessionKeyMastercard
+ *       PrimaryAccountNumber: "STRING_VALUE", // required
+ *       PanSequenceNumber: "STRING_VALUE", // required
+ *       ApplicationTransactionCounter: "STRING_VALUE", // required
+ *       UnpredictableNumber: "STRING_VALUE", // required
+ *     },
+ *     Emv2000: { // SessionKeyEmv2000
+ *       PrimaryAccountNumber: "STRING_VALUE", // required
+ *       PanSequenceNumber: "STRING_VALUE", // required
+ *       ApplicationTransactionCounter: "STRING_VALUE", // required
+ *     },
+ *     Amex: { // SessionKeyAmex
+ *       PrimaryAccountNumber: "STRING_VALUE", // required
+ *       PanSequenceNumber: "STRING_VALUE", // required
+ *     },
+ *     Visa: { // SessionKeyVisa
+ *       PrimaryAccountNumber: "STRING_VALUE", // required
+ *       PanSequenceNumber: "STRING_VALUE", // required
+ *     },
+ *   },
+ * };
+ * const command = new GenerateAuthRequestCryptogramCommand(input);
+ * const response = await client.send(command);
+ * // { // GenerateAuthRequestCryptogramOutput
+ * //   KeyArn: "STRING_VALUE", // required
+ * //   KeyCheckValue: "STRING_VALUE", // required
+ * //   AuthRequestCryptogram: "STRING_VALUE", // required
+ * // };
+ *
+ * ```
+ *
+ * @param GenerateAuthRequestCryptogramCommandInput - {@link GenerateAuthRequestCryptogramCommandInput}
+ * @returns {@link GenerateAuthRequestCryptogramCommandOutput}
+ * @see {@link GenerateAuthRequestCryptogramCommandInput} for command's `input` shape.
+ * @see {@link GenerateAuthRequestCryptogramCommandOutput} for command's `response` shape.
+ * @see {@link PaymentCryptographyDataClientResolvedConfig | config} for PaymentCryptographyDataClient's `config` shape.
+ *
+ * @throws {@link AccessDeniedException} (client fault)
+ *  <p>You do not have sufficient access to perform this action.</p>
+ *
+ * @throws {@link InternalServerException} (server fault)
+ *  <p>The request processing has failed because of an unknown error, exception, or failure.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The request was denied due to an invalid resource error.</p>
+ *
+ * @throws {@link ThrottlingException} (client fault)
+ *  <p>The request was denied due to request throttling.</p>
+ *
+ * @throws {@link ValidationException} (client fault)
+ *  <p>The request was denied due to an invalid request error.</p>
+ *
+ * @throws {@link PaymentCryptographyDataServiceException}
+ * <p>Base exception class for all service exceptions from PaymentCryptographyData service.</p>
+ *
+ *
+ * @public
+ */
+export declare class GenerateAuthRequestCryptogramCommand extends GenerateAuthRequestCryptogramCommand_base {
+    /** @internal type navigation helper, not in runtime. */
+    protected static __types: {
+        api: {
+            input: GenerateAuthRequestCryptogramInput;
+            output: GenerateAuthRequestCryptogramOutput;
+        };
+        sdk: {
+            input: GenerateAuthRequestCryptogramCommandInput;
+            output: GenerateAuthRequestCryptogramCommandOutput;
+        };
+    };
+}

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

@@ -29,7 +29,7 @@ declare const GenerateCardValidationDataCommand_base: {
     };
 };
 /**
- * <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 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_ImportKey.html">ImportKey</a> </p> </li> <li> <p> <a>VerifyCardValidationData</a> </p> </li> </ul>
+ * <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>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -29,7 +29,7 @@ declare const GenerateMacCommand_base: {
     };
 };
 /**
- * <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 can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>VerifyMac</a> </p> </li> </ul>
+ * <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>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -29,7 +29,7 @@ declare const GenerateMacEmvPinChangeCommand_base: {
     };
 };
 /**
- * <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 can't be used across different Amazon Web Services accounts.</p> <p> <b>Related operations:</b> </p> <ul> <li> <p> <a>EncryptData</a> </p> </li> <li> <p> <a>GenerateMac</a> </p> </li> </ul>
+ * <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>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -29,7 +29,7 @@ declare const GeneratePinDataCommand_base: {
     };
 };
 /**
- * <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 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>TranslatePinData</a> </p> </li> <li> <p> <a>VerifyPinData</a> </p> </li> </ul>
+ * <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>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript