@aws-sdk/client-payment-cryptography-data

Description

AWS SDK for JavaScript PaymentCryptographyData Client for Node.js, Browser and React Native.

You use the Amazon Web Services Payment Cryptography Data Plane to manage how encryption keys are used for payment-related transaction processing and associated cryptographic operations. You can encrypt, decrypt, generate, verify, and translate payment-related cryptographic operations in Amazon Web Services Payment Cryptography. For more information, see Data operations in the Amazon Web Services Payment Cryptography User Guide.

To manage your encryption keys, you use the Amazon Web Services Payment Cryptography Control Plane. You can create, import, export, share, manage, and delete keys. You can also manage Identity and Access Management (IAM) policies for keys.

Installing

To install the this package, simply type add or install @aws-sdk/client-payment-cryptography-data using your favorite package manager:

• npm install @aws-sdk/client-payment-cryptography-data
• yarn add @aws-sdk/client-payment-cryptography-data
• pnpm add @aws-sdk/client-payment-cryptography-data

Getting Started

Import

The AWS SDK is modulized by clients and commands. To send a request, you only need to import the PaymentCryptographyDataClient and the commands you need, for example DecryptDataCommand:

// ES5 example
const { PaymentCryptographyDataClient, DecryptDataCommand } = require("@aws-sdk/client-payment-cryptography-data");

// ES6+ example
import { PaymentCryptographyDataClient, DecryptDataCommand } from "@aws-sdk/client-payment-cryptography-data";

Usage

To send a request, you:

• Initiate client with configuration (e.g. credentials, region).
• Initiate command with input parameters.
• Call send operation on client with command object as input.
• If you are using a custom http handler, you may call destroy() to close open connections.

// a client can be shared by different commands.
const client = new PaymentCryptographyDataClient({ region: "REGION" });

const params = {
  /** input parameters */
};
const command = new DecryptDataCommand(params);

Async/await

We recommend using await operator to wait for the promise returned by send operation as follows:

// async/await.
try {
  const data = await client.send(command);
  // process data.
} catch (error) {
  // error handling.
} finally {
  // finally.
}

Async-await is clean, concise, intuitive, easy to debug and has better error handling as compared to using Promise chains or callbacks.

Promises

You can also use Promise chaining to execute send operation.

client.send(command).then(
  (data) => {
    // process data.
  },
  (error) => {
    // error handling.
  }
);

Promises can also be called using .catch() and .finally() as follows:

client
  .send(command)
  .then((data) => {
    // process data.
  })
  .catch((error) => {
    // error handling.
  })
  .finally(() => {
    // finally.
  });

Callbacks

We do not recommend using callbacks because of callback hell, but they are supported by the send operation.

// callbacks.
client.send(command, (err, data) => {
  // process err and data.
});

v2 compatible style

The client can also send requests using v2 compatible style. However, it results in a bigger bundle size and may be dropped in next major version. More details in the blog post on modular packages in AWS SDK for JavaScript

import * as AWS from "@aws-sdk/client-payment-cryptography-data";
const client = new AWS.PaymentCryptographyData({ region: "REGION" });

// async/await.
try {
  const data = await client.decryptData(params);
  // process data.
} catch (error) {
  // error handling.
}

// Promises.
client
  .decryptData(params)
  .then((data) => {
    // process data.
  })
  .catch((error) => {
    // error handling.
  });

// callbacks.
client.decryptData(params, (err, data) => {
  // process err and data.
});

Troubleshooting

When the service returns an exception, the error will include the exception information, as well as response metadata (e.g. request id).

try {
  const data = await client.send(command);
  // process data.
} catch (error) {
  const { requestId, cfId, extendedRequestId } = error.$metadata;
  console.log({ requestId, cfId, extendedRequestId });
  /**
   * The keys within exceptions are also parsed.
   * You can access them by specifying exception names:
   * if (error.name === 'SomeServiceException') {
   *     const value = error.specialKeyInException;
   * }
   */
}

Getting Help

Please use these community resources for getting help. We use the GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.

• Visit Developer Guide or API Reference.
• Check out the blog posts tagged with aws-sdk-js on AWS Developer Blog.
• Ask a question on StackOverflow and tag it with aws-sdk-js.
• Join the AWS JavaScript community on gitter.
• If it turns out that you may have found a bug, please open an issue.

To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.

Contributing

This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-payment-cryptography-data package is updated. To contribute to client you can check our generate clients scripts.

License

This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.

Client Commands (Operations List)

DecryptData

Command API Reference / Input / Output

EncryptData

Command API Reference / Input / Output

GenerateCardValidationData

Command API Reference / Input / Output

GenerateMac

Command API Reference / Input / Output

GeneratePinData

Command API Reference / Input / Output

ReEncryptData

Command API Reference / Input / Output

TranslatePinData

Command API Reference / Input / Output

VerifyAuthRequestCryptogram

Command API Reference / Input / Output

VerifyCardValidationData

Command API Reference / Input / Output

VerifyMac

Command API Reference / Input / Output

VerifyPinData

Command API Reference / Input / Output