

# Actions
<a name="API_Operations"></a>

The following actions are supported:
+  [AddKeyReplicationRegions](API_AddKeyReplicationRegions.md) 
+  [CreateAlias](API_CreateAlias.md) 
+  [CreateKey](API_CreateKey.md) 
+  [DeleteAlias](API_DeleteAlias.md) 
+  [DeleteKey](API_DeleteKey.md) 
+  [DisableDefaultKeyReplicationRegions](API_DisableDefaultKeyReplicationRegions.md) 
+  [EnableDefaultKeyReplicationRegions](API_EnableDefaultKeyReplicationRegions.md) 
+  [ExportKey](API_ExportKey.md) 
+  [GetAlias](API_GetAlias.md) 
+  [GetCertificateSigningRequest](API_GetCertificateSigningRequest.md) 
+  [GetDefaultKeyReplicationRegions](API_GetDefaultKeyReplicationRegions.md) 
+  [GetKey](API_GetKey.md) 
+  [GetParametersForExport](API_GetParametersForExport.md) 
+  [GetParametersForImport](API_GetParametersForImport.md) 
+  [GetPublicKeyCertificate](API_GetPublicKeyCertificate.md) 
+  [ImportKey](API_ImportKey.md) 
+  [ListAliases](API_ListAliases.md) 
+  [ListKeys](API_ListKeys.md) 
+  [ListTagsForResource](API_ListTagsForResource.md) 
+  [RemoveKeyReplicationRegions](API_RemoveKeyReplicationRegions.md) 
+  [RestoreKey](API_RestoreKey.md) 
+  [StartKeyUsage](API_StartKeyUsage.md) 
+  [StopKeyUsage](API_StopKeyUsage.md) 
+  [TagResource](API_TagResource.md) 
+  [UntagResource](API_UntagResource.md) 
+  [UpdateAlias](API_UpdateAlias.md) 

# AddKeyReplicationRegions
<a name="API_AddKeyReplicationRegions"></a>

Adds replication AWS Regions to an existing AWS Payment Cryptography key, enabling the key to be used for cryptographic operations in additional AWS Regions.

 [Multi-Region key replication](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html) allow you to use the same key material across multiple AWS Regions, providing lower latency for applications distributed across regions. When you add Replication Regions, AWS Payment Cryptography securely replicates the key material to the specified AWS Regions.

The key must be in an active state to add Replication Regions. You can add multiple regions in a single operation, and the key will be available for use in those regions once replication is complete.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [RemoveKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_RemoveKeyReplicationRegions.html) 
+  [EnableDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_EnableDefaultKeyReplicationRegions.html) 
+  [GetDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetDefaultKeyReplicationRegions.html) 

## Request Syntax
<a name="API_AddKeyReplicationRegions_RequestSyntax"></a>

```
{
   "KeyIdentifier": "string",
   "ReplicationRegions": [ "string" ]
}
```

## Request Parameters
<a name="API_AddKeyReplicationRegions_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyIdentifier](#API_AddKeyReplicationRegions_RequestSyntax) **   <a name="paymentcryptography-AddKeyReplicationRegions-request-KeyIdentifier"></a>
The key identifier (ARN or alias) of the key for which to add replication regions.  
This key must exist and be in a valid state for replication operations.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

 ** [ReplicationRegions](#API_AddKeyReplicationRegions_RequestSyntax) **   <a name="paymentcryptography-AddKeyReplicationRegions-request-ReplicationRegions"></a>
The list of AWS Regions to add to the key's replication configuration.  
Each region must be a valid AWS Region where AWS Payment Cryptography is available. The key will be replicated to these regions, allowing cryptographic operations to be performed closer to your applications.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+`   
Required: Yes

## Response Syntax
<a name="API_AddKeyReplicationRegions_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_AddKeyReplicationRegions_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_AddKeyReplicationRegions_ResponseSyntax) **   <a name="paymentcryptography-AddKeyReplicationRegions-response-Key"></a>
The updated key metadata after adding the replication regions.  
This includes the current state of the key and its replication configuration.  
Type: [Key](API_Key.md) object

## Errors
<a name="API_AddKeyReplicationRegions_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_AddKeyReplicationRegions_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/AddKeyReplicationRegions) 

# CreateAlias
<a name="API_CreateAlias"></a>

Creates an *alias*, or a friendly name, for an AWS Payment Cryptography key. You can use an alias to identify a key in the console and when you call cryptographic operations such as [EncryptData](https://docs.aws.amazon.com/payment-cryptography/latest/DataAPIReference/API_EncryptData.html) or [DecryptData](https://docs.aws.amazon.com/payment-cryptography/latest/DataAPIReference/API_DecryptData.html).

You can associate the alias with any key in the same AWS Region. Each alias is associated with only one key at a time, but a key can have multiple aliases. You can't create an alias without a key. The alias must be unique in the account and AWS Region, but you can create another alias with the same name in a different AWS Region.

To change the key that's associated with the alias, call [UpdateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html). To delete the alias, call [DeleteAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html). These operations don't affect the underlying key. To get the alias that you created, call [ListAliases](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html).

 **Cross-account use**: This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [DeleteAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html) 
+  [GetAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetAlias.html) 
+  [ListAliases](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html) 
+  [UpdateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html) 

## Request Syntax
<a name="API_CreateAlias_RequestSyntax"></a>

```
{
   "AliasName": "string",
   "KeyArn": "string"
}
```

## Request Parameters
<a name="API_CreateAlias_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [AliasName](#API_CreateAlias_RequestSyntax) **   <a name="paymentcryptography-CreateAlias-request-AliasName"></a>
A friendly name that you can use to refer to a key. An alias must begin with `alias/` followed by a name, for example `alias/ExampleAlias`. It can contain only alphanumeric characters, forward slashes (/), underscores (\$1), and dashes (-).  
Don't include personal, confidential or sensitive information in this field. This field may be displayed in plaintext in AWS CloudTrail logs and other output.
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 256.  
Pattern: `alias/[a-zA-Z0-9/_-]+`   
Required: Yes

 ** [KeyArn](#API_CreateAlias_RequestSyntax) **   <a name="paymentcryptography-CreateAlias-request-KeyArn"></a>
The `KeyARN` of the key to associate with the alias.  
Type: String  
Length Constraints: Minimum length of 70. Maximum length of 150.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:key/[0-9a-zA-Z]{16,64}`   
Required: No

## Response Syntax
<a name="API_CreateAlias_ResponseSyntax"></a>

```
{
   "Alias": { 
      "AliasName": "string",
      "KeyArn": "string"
   }
}
```

## Response Elements
<a name="API_CreateAlias_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Alias](#API_CreateAlias_ResponseSyntax) **   <a name="paymentcryptography-CreateAlias-response-Alias"></a>
The alias for the key.  
Type: [Alias](API_Alias.md) object

## Errors
<a name="API_CreateAlias_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_CreateAlias_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/CreateAlias) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/CreateAlias) 

# CreateKey
<a name="API_CreateKey"></a>

Creates an AWS Payment Cryptography key, a logical representation of a cryptographic key, that is unique in your account and AWS Region. You use keys for cryptographic functions such as encryption and decryption. 

In addition to the key material used in cryptographic operations, an AWS Payment Cryptography key includes metadata such as the key ARN, key usage, key origin, creation date, description, and key state.

When you create a key, you specify both immutable and mutable data about the key. The immutable data contains key attributes that define the scope and cryptographic operations that you can perform using the key, for example key class (example: `SYMMETRIC_KEY`), key algorithm (example: `TDES_2KEY`), key usage (example: `TR31_P0_PIN_ENCRYPTION_KEY`) and key modes of use (example: `Encrypt`). AWS Payment Cryptography binds key attributes to keys using key blocks when you store or export them. AWS Payment Cryptography stores the key contents wrapped and never stores or transmits them in the clear.

For information about valid combinations of key attributes, see [Understanding key attributes](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html) in the * AWS Payment Cryptography User Guide*. The mutable data contained within a key includes usage timestamp and key deletion timestamp and can be modified after creation.

You can use the `CreateKey` operation to generate an ECC (Elliptic Curve Cryptography) key pair used for establishing an ECDH (Elliptic Curve Diffie-Hellman) key agreement between two parties. In the ECDH key agreement process, both parties generate their own ECC key pair with key usage K3 and exchange the public keys. Each party then use their private key, the received public key from the other party, and the key derivation parameters including key derivation function, hash algorithm, derivation data, and key algorithm to derive a shared key.

To maintain the single-use principle of cryptographic keys in payments, ECDH derived keys should not be used for multiple purposes, such as a `TR31_P0_PIN_ENCRYPTION_KEY` and `TR31_K1_KEY_BLOCK_PROTECTION_KEY`. When creating ECC key pairs in AWS Payment Cryptography you can optionally set the `DeriveKeyUsage` parameter, which defines the key usage bound to the symmetric key that will be derived using the ECC key pair.

 **Cross-account use**: This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [DeleteKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html) 
+  [GetKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetKey.html) 
+  [ListKeys](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListKeys.html) 

## Request Syntax
<a name="API_CreateKey_RequestSyntax"></a>

```
{
   "DeriveKeyUsage": "string",
   "Enabled": boolean,
   "Exportable": boolean,
   "KeyAttributes": { 
      "KeyAlgorithm": "string",
      "KeyClass": "string",
      "KeyModesOfUse": { 
         "Decrypt": boolean,
         "DeriveKey": boolean,
         "Encrypt": boolean,
         "Generate": boolean,
         "NoRestrictions": boolean,
         "Sign": boolean,
         "Unwrap": boolean,
         "Verify": boolean,
         "Wrap": boolean
      },
      "KeyUsage": "string"
   },
   "KeyCheckValueAlgorithm": "string",
   "ReplicationRegions": [ "string" ],
   "Tags": [ 
      { 
         "Key": "string",
         "Value": "string"
      }
   ]
}
```

## Request Parameters
<a name="API_CreateKey_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [DeriveKeyUsage](#API_CreateKey_RequestSyntax) **   <a name="paymentcryptography-CreateKey-request-DeriveKeyUsage"></a>
The intended cryptographic usage of keys derived from the ECC key pair to be created.  
After creating an ECC key pair, you cannot change the intended cryptographic usage of keys derived from it using ECDH.  
Type: String  
Valid Values: `TR31_B0_BASE_DERIVATION_KEY | TR31_C0_CARD_VERIFICATION_KEY | TR31_D0_SYMMETRIC_DATA_ENCRYPTION_KEY | TR31_E0_EMV_MKEY_APP_CRYPTOGRAMS | TR31_E1_EMV_MKEY_CONFIDENTIALITY | TR31_E2_EMV_MKEY_INTEGRITY | TR31_E4_EMV_MKEY_DYNAMIC_NUMBERS | TR31_E5_EMV_MKEY_CARD_PERSONALIZATION | TR31_E6_EMV_MKEY_OTHER | TR31_K0_KEY_ENCRYPTION_KEY | TR31_K1_KEY_BLOCK_PROTECTION_KEY | TR31_M3_ISO_9797_3_MAC_KEY | TR31_M1_ISO_9797_1_MAC_KEY | TR31_M6_ISO_9797_5_CMAC_KEY | TR31_M7_HMAC_KEY | TR31_P0_PIN_ENCRYPTION_KEY | TR31_P1_PIN_GENERATION_KEY | TR31_V1_IBM3624_PIN_VERIFICATION_KEY | TR31_V2_VISA_PIN_VERIFICATION_KEY`   
Required: No

 ** [Enabled](#API_CreateKey_RequestSyntax) **   <a name="paymentcryptography-CreateKey-request-Enabled"></a>
Specifies whether to enable the key. If the key is enabled, it is activated for use within the service. If the key is not enabled, then it is created but not activated. The default value is enabled.  
Type: Boolean  
Required: No

 ** [Exportable](#API_CreateKey_RequestSyntax) **   <a name="paymentcryptography-CreateKey-request-Exportable"></a>
Specifies whether the key is exportable from the service.  
Type: Boolean  
Required: Yes

 ** [KeyAttributes](#API_CreateKey_RequestSyntax) **   <a name="paymentcryptography-CreateKey-request-KeyAttributes"></a>
The role of the key, the algorithm it supports, and the cryptographic operations allowed with the key. This data is immutable after the key is created.  
Type: [KeyAttributes](API_KeyAttributes.md) object  
Required: Yes

 ** [KeyCheckValueAlgorithm](#API_CreateKey_RequestSyntax) **   <a name="paymentcryptography-CreateKey-request-KeyCheckValueAlgorithm"></a>
The algorithm that AWS Payment Cryptography uses to calculate the key check value (KCV). It is used to validate the key integrity.  
For TDES keys, the KCV is computed by encrypting 8 bytes, each with value of zero, with the key to be checked and retaining the 3 highest order bytes of the encrypted result. For AES keys, the KCV is computed using a CMAC algorithm where the input data is 16 bytes of zero and retaining the 3 highest order bytes of the encrypted result.  
Type: String  
Valid Values: `CMAC | ANSI_X9_24 | HMAC | SHA_1`   
Required: No

 ** [ReplicationRegions](#API_CreateKey_RequestSyntax) **   <a name="paymentcryptography-CreateKey-request-ReplicationRegions"></a>
A list of AWS Regions for key replication operations.  
Each region in the list must be a valid AWS Region identifier where AWS Payment Cryptography is available. This list is used to specify which regions should be added to or removed from a key's replication configuration.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+`   
Required: No

 ** [Tags](#API_CreateKey_RequestSyntax) **   <a name="paymentcryptography-CreateKey-request-Tags"></a>
Assigns one or more tags to the AWS Payment Cryptography key. Use this parameter to tag a key when it is created. To tag an existing AWS Payment Cryptography key, use the [TagResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_TagResource.html) operation.  
Each tag consists of a tag key and a tag value. Both the tag key and the tag value are required, but the tag value can be an empty (null) string. You can't have more than one tag on an AWS Payment Cryptography key with the same tag key.   
Don't include personal, confidential or sensitive information in this field. This field may be displayed in plaintext in AWS CloudTrail logs and other output.
Tagging or untagging an AWS Payment Cryptography key can allow or deny permission to the key.
Type: Array of [Tag](API_Tag.md) objects  
Array Members: Minimum number of 0 items. Maximum number of 200 items.  
Required: No

## Response Syntax
<a name="API_CreateKey_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_CreateKey_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_CreateKey_ResponseSyntax) **   <a name="paymentcryptography-CreateKey-response-Key"></a>
The key material that contains all the key attributes.  
Type: [Key](API_Key.md) object

## Errors
<a name="API_CreateKey_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_CreateKey_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/CreateKey) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/CreateKey) 

# DeleteAlias
<a name="API_DeleteAlias"></a>

Deletes the alias, but doesn't affect the underlying key.

Each key can have multiple aliases. To get the aliases of all keys, use the [UpdateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html) operation. To change the alias of a key, first use [DeleteAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html) to delete the current alias and then use [CreateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html) to create a new alias. To associate an existing alias with a different key, call [UpdateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html).

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [CreateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html) 
+  [GetAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetAlias.html) 
+  [ListAliases](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html) 
+  [UpdateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html) 

## Request Syntax
<a name="API_DeleteAlias_RequestSyntax"></a>

```
{
   "AliasName": "string"
}
```

## Request Parameters
<a name="API_DeleteAlias_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [AliasName](#API_DeleteAlias_RequestSyntax) **   <a name="paymentcryptography-DeleteAlias-request-AliasName"></a>
A friendly name that you can use to refer AWS Payment Cryptography key. This value must begin with `alias/` followed by a name, such as `alias/ExampleAlias`.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 256.  
Pattern: `alias/[a-zA-Z0-9/_-]+`   
Required: Yes

## Response Elements
<a name="API_DeleteAlias_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.

## Errors
<a name="API_DeleteAlias_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_DeleteAlias_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/DeleteAlias) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/DeleteAlias) 

# DeleteKey
<a name="API_DeleteKey"></a>

Deletes the key material and metadata associated with AWS Payment Cryptography key.

Key deletion is irreversible. After a key is deleted, you can't perform cryptographic operations using the key. For example, you can't decrypt data that was encrypted by a deleted AWS Payment Cryptography key, and the data may become unrecoverable. Because key deletion is destructive, AWS Payment Cryptography has a safety mechanism to prevent accidental deletion of a key. When you call this operation, AWS Payment Cryptography disables the specified key but doesn't delete it until after a waiting period set using `DeleteKeyInDays`. The default waiting period is 7 days. During the waiting period, the `KeyState` is `DELETE_PENDING`. After the key is deleted, the `KeyState` is `DELETE_COMPLETE`.

You should delete a key only when you are sure that you don't need to use it anymore and no other parties are utilizing this key. If you aren't sure, consider deactivating it instead by calling [StopKeyUsage](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StopKeyUsage.html).

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [RestoreKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_RestoreKey.html) 
+  [StartKeyUsage](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StartKeyUsage.html) 
+  [StopKeyUsage](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StopKeyUsage.html) 

## Request Syntax
<a name="API_DeleteKey_RequestSyntax"></a>

```
{
   "DeleteKeyInDays": number,
   "KeyIdentifier": "string"
}
```

## Request Parameters
<a name="API_DeleteKey_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [DeleteKeyInDays](#API_DeleteKey_RequestSyntax) **   <a name="paymentcryptography-DeleteKey-request-DeleteKeyInDays"></a>
The waiting period for key deletion. The default value is seven days.  
Type: Integer  
Valid Range: Minimum value of 3. Maximum value of 180.  
Required: No

 ** [KeyIdentifier](#API_DeleteKey_RequestSyntax) **   <a name="paymentcryptography-DeleteKey-request-KeyIdentifier"></a>
The `KeyARN` of the key that is scheduled for deletion.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

## Response Syntax
<a name="API_DeleteKey_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_DeleteKey_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_DeleteKey_ResponseSyntax) **   <a name="paymentcryptography-DeleteKey-response-Key"></a>
The `KeyARN` of the key that is scheduled for deletion.  
Type: [Key](API_Key.md) object

## Errors
<a name="API_DeleteKey_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_DeleteKey_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/DeleteKey) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/DeleteKey) 

# DisableDefaultKeyReplicationRegions
<a name="API_DisableDefaultKeyReplicationRegions"></a>

Disables [Multi-Region key replication](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html) settings for the specified AWS Regions in your AWS account, preventing new keys from being automatically replicated to those regions.

After disabling Multi-Region key replication for specific regions, new keys created in your account will not be automatically replicated to those regions. You can still manually add replication to those regions for individual keys using the [AddKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_AddKeyReplicationRegions.html) operation.

This operation does not affect existing keys or their current replication configuration.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [EnableDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_EnableDefaultKeyReplicationRegions.html) 
+  [GetDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetDefaultKeyReplicationRegions.html) 

## Request Syntax
<a name="API_DisableDefaultKeyReplicationRegions_RequestSyntax"></a>

```
{
   "ReplicationRegions": [ "string" ]
}
```

## Request Parameters
<a name="API_DisableDefaultKeyReplicationRegions_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [ReplicationRegions](#API_DisableDefaultKeyReplicationRegions_RequestSyntax) **   <a name="paymentcryptography-DisableDefaultKeyReplicationRegions-request-ReplicationRegions"></a>
The list of AWS Regions to remove from the account's default replication regions.  
New keys created after this operation will not automatically be replicated to these regions, though existing keys with replication to these regions will be unaffected.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+`   
Required: Yes

## Response Syntax
<a name="API_DisableDefaultKeyReplicationRegions_ResponseSyntax"></a>

```
{
   "EnabledReplicationRegions": [ "string" ]
}
```

## Response Elements
<a name="API_DisableDefaultKeyReplicationRegions_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [EnabledReplicationRegions](#API_DisableDefaultKeyReplicationRegions_ResponseSyntax) **   <a name="paymentcryptography-DisableDefaultKeyReplicationRegions-response-EnabledReplicationRegions"></a>
The remaining list of regions where default key replication is still enabled for the account.  
This reflects the account's default replication configuration after removing the specified regions.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+` 

## Errors
<a name="API_DisableDefaultKeyReplicationRegions_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_DisableDefaultKeyReplicationRegions_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/DisableDefaultKeyReplicationRegions) 

# EnableDefaultKeyReplicationRegions
<a name="API_EnableDefaultKeyReplicationRegions"></a>

Enables [Multi-Region key replication](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html) settings for your AWS account, causing new keys to be automatically replicated to the specified AWS Regions when created.

When Multi-Region key replication are enabled, any new keys created in your account will automatically be replicated to these regions unless you explicitly override this behavior during key creation. This simplifies key management for applications that operate across multiple regions.

Existing keys are not affected by this operation - only keys created after enabling default replication will be automatically replicated.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [DisableDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DisableDefaultKeyReplicationRegions.html) 
+  [GetDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetDefaultKeyReplicationRegions.html) 

## Request Syntax
<a name="API_EnableDefaultKeyReplicationRegions_RequestSyntax"></a>

```
{
   "ReplicationRegions": [ "string" ]
}
```

## Request Parameters
<a name="API_EnableDefaultKeyReplicationRegions_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [ReplicationRegions](#API_EnableDefaultKeyReplicationRegions_RequestSyntax) **   <a name="paymentcryptography-EnableDefaultKeyReplicationRegions-request-ReplicationRegions"></a>
The list of AWS Regions to enable as default replication regions for the AWS account for [Multi-Region key replication](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html).  
New keys created in this account will automatically be replicated to these regions unless explicitly overridden during key creation.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+`   
Required: Yes

## Response Syntax
<a name="API_EnableDefaultKeyReplicationRegions_ResponseSyntax"></a>

```
{
   "EnabledReplicationRegions": [ "string" ]
}
```

## Response Elements
<a name="API_EnableDefaultKeyReplicationRegions_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [EnabledReplicationRegions](#API_EnableDefaultKeyReplicationRegions_ResponseSyntax) **   <a name="paymentcryptography-EnableDefaultKeyReplicationRegions-response-EnabledReplicationRegions"></a>
The complete list of regions where default key replication is now enabled for the account.  
This includes both previously enabled regions and the newly added regions from this operation.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+` 

## Errors
<a name="API_EnableDefaultKeyReplicationRegions_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_EnableDefaultKeyReplicationRegions_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/EnableDefaultKeyReplicationRegions) 

# ExportKey
<a name="API_ExportKey"></a>

Exports a key from AWS Payment Cryptography.

 AWS Payment Cryptography simplifies key exchange by replacing the existing paper-based approach with a modern electronic approach. With `ExportKey` you can export symmetric keys using either symmetric and asymmetric key exchange mechanisms. Using this operation, you can share your AWS Payment Cryptography generated keys with other service partners to perform cryptographic operations outside of AWS Payment Cryptography 

For symmetric key exchange, AWS Payment Cryptography uses the ANSI X9 TR-31 norm in accordance with PCI PIN guidelines. And for asymmetric key exchange, AWS Payment Cryptography supports ANSI X9 TR-34 norm, RSA unwrap, and ECDH (Elliptic Curve Diffie-Hellman) key exchange mechanisms. Asymmetric key exchange methods are typically used to establish bi-directional trust between the two parties exhanging keys and are used for initial key exchange such as Key Encryption Key (KEK). After which you can export working keys using symmetric method to perform various cryptographic operations within AWS Payment Cryptography.

PCI requires specific minimum key strength of wrapping keys used to protect the keys being exchanged electronically. These requirements can change when PCI standards are revised. The rules specify that wrapping keys used for transport must be at least as strong as the key being protected. For more information on recommended key strength of wrapping keys and key exchange mechanism, see [Importing and exporting keys](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-importexport.html) in the * AWS Payment Cryptography User Guide*.

You can also use `ExportKey` functionality to generate and export an IPEK (Initial Pin Encryption Key) from AWS Payment Cryptography using either TR-31 or TR-34 export key exchange. IPEK is generated from BDK (Base Derivation Key) and `ExportDukptInitialKey` attribute KSN (`KeySerialNumber`). The generated IPEK does not persist within AWS Payment Cryptography and has to be re-generated each time during export.

For key exchange using TR-31 or TR-34 key blocks, you can also export optional blocks within the key block header which contain additional attribute information about the key. The `KeyVersion` within `KeyBlockHeaders` indicates the version of the key within the key block. Furthermore, `KeyExportability` within `KeyBlockHeaders` can be used to further restrict exportability of the key after export from AWS Payment Cryptography.

The `OptionalBlocks` contain the additional data related to the key. For information on data type that can be included within optional blocks, refer to [ASC X9.143-2022](https://webstore.ansi.org/standards/ascx9/ansix91432022).

**Note**  
Data included in key block headers is signed but transmitted in clear text. Sensitive or confidential information should not be included in optional blocks. Refer to ASC X9.143-2022 standard for information on allowed data type.

 **To export initial keys (KEK) or IPEK using TR-34** 

Using this operation, you can export initial key using TR-34 asymmetric key exchange. You can only export KEK generated within AWS Payment Cryptography. In TR-34 terminology, the sending party of the key is called Key Distribution Host (KDH) and the receiving party of the key is called Key Receiving Device (KRD). During key export process, KDH is AWS Payment Cryptography which initiates key export and KRD is the user receiving the key.

To initiate TR-34 key export, the KRD must obtain an export token by calling [GetParametersForExport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForExport.html). This operation also generates a key pair for the purpose of key export, signs the key and returns back the signing public key certificate (also known as KDH signing certificate) and root certificate chain. The KDH uses the private key to sign the the export payload and the signing public key certificate is provided to KRD to verify the signature. The KRD can import the root certificate into its Hardware Security Module (HSM), as required. The export token and the associated KDH signing certificate expires after 30 days. 

Next the KRD generates a key pair for the the purpose of encrypting the KDH key and provides the public key cerificate (also known as KRD wrapping certificate) back to KDH. The KRD will also import the root cerificate chain into AWS Payment Cryptography by calling [ImportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html) for `RootCertificatePublicKey`. The KDH, AWS Payment Cryptography, will use the KRD wrapping cerificate to encrypt (wrap) the key under export and signs it with signing private key to generate a TR-34 WrappedKeyBlock. For more information on TR-34 key export, see section [Exporting symmetric keys](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-export.html) in the * AWS Payment Cryptography User Guide*. 

Set the following parameters:
+  `ExportAttributes`: Specify export attributes in case of IPEK export. This parameter is optional for KEK export.
+  `ExportKeyIdentifier`: The `KeyARN` of the KEK or BDK (in case of IPEK) under export.
+  `KeyMaterial`: Use `Tr34KeyBlock` parameters.
+  `CertificateAuthorityPublicKeyIdentifier`: The `KeyARN` of the certificate chain that signed the KRD wrapping key certificate.
+  `ExportToken`: Obtained from KDH by calling [GetParametersForImport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html).
+  `WrappingKeyCertificate`: The public key certificate in PEM format (base64 encoded) of the KRD wrapping key AWS Payment Cryptography uses for encryption of the TR-34 export payload. This certificate must be signed by the root certificate (CertificateAuthorityPublicKeyIdentifier) imported into AWS Payment Cryptography.

When this operation is successful, AWS Payment Cryptography returns the KEK or IPEK as a TR-34 WrappedKeyBlock. 

 **To export initial keys (KEK) or IPEK using RSA Wrap and Unwrap** 

Using this operation, you can export initial key using asymmetric RSA wrap and unwrap key exchange method. To initiate export, generate an asymmetric key pair on the receiving HSM and obtain the public key certificate in PEM format (base64 encoded) for the purpose of wrapping and the root certifiate chain. Import the root certificate into AWS Payment Cryptography by calling [ImportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html) for `RootCertificatePublicKey`.

Next call `ExportKey` and set the following parameters:
+  `CertificateAuthorityPublicKeyIdentifier`: The `KeyARN` of the certificate chain that signed wrapping key certificate.
+  `KeyMaterial`: Set to `KeyCryptogram`.
+  `WrappingKeyCertificate`: The public key certificate in PEM format (base64 encoded) obtained by the receiving HSM and signed by the root certificate (CertificateAuthorityPublicKeyIdentifier) imported into AWS Payment Cryptography. The receiving HSM uses its private key component to unwrap the WrappedKeyCryptogram.

When this operation is successful, AWS Payment Cryptography returns the WrappedKeyCryptogram. 

 **To export working keys or IPEK using TR-31** 

Using this operation, you can export working keys or IPEK using TR-31 symmetric key exchange. In TR-31, you must use an initial key such as KEK to encrypt or wrap the key under export. To establish a KEK, you can use [CreateKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html) or [ImportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html). 

Set the following parameters:
+  `ExportAttributes`: Specify export attributes in case of IPEK export. This parameter is optional for KEK export.
+  `ExportKeyIdentifier`: The `KeyARN` of the KEK or BDK (in case of IPEK) under export.
+  `KeyMaterial`: Use `Tr31KeyBlock` parameters.

 **To export working keys using ECDH** 

You can also use ECDH key agreement to export working keys in a TR-31 keyblock, where the wrapping key is an ECDH derived key.

To initiate a TR-31 key export using ECDH, both sides must create an ECC key pair with key usage K3 and exchange public key certificates. In AWS Payment Cryptography, you can do this by calling `CreateKey`. If you have not already done so, you must import the CA chain that issued the receiving public key certificate by calling `ImportKey` with input `RootCertificatePublicKey` for root CA or `TrustedPublicKey` for intermediate CA. You can then complete a TR-31 key export by deriving a shared wrapping key using the service ECC key pair, public certificate of your ECC key pair outside of AWS Payment Cryptography, and the key derivation parameters including key derivation function, hash algorithm, derivation data, key algorithm.
+  `KeyMaterial`: Use `DiffieHellmanTr31KeyBlock` parameters.
+  `PrivateKeyIdentifier`: The `KeyArn` of the ECC key pair created within AWS Payment Cryptography to derive a shared KEK.
+  `PublicKeyCertificate`: The public key certificate of the receiving ECC key pair in PEM format (base64 encoded) to derive a shared KEK.
+  `CertificateAuthorityPublicKeyIdentifier`: The `keyARN` of the CA that signed the public key certificate of the receiving ECC key pair.

When this operation is successful, AWS Payment Cryptography returns the working key as a TR-31 WrappedKeyBlock, where the wrapping key is the ECDH derived key.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [GetParametersForExport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForExport.html) 
+  [ImportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html) 

## Request Syntax
<a name="API_ExportKey_RequestSyntax"></a>

```
{
   "ExportAttributes": { 
      "ExportDukptInitialKey": { 
         "KeySerialNumber": "string"
      },
      "KeyCheckValueAlgorithm": "string"
   },
   "ExportKeyIdentifier": "string",
   "KeyMaterial": { ... }
}
```

## Request Parameters
<a name="API_ExportKey_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [ExportAttributes](#API_ExportKey_RequestSyntax) **   <a name="paymentcryptography-ExportKey-request-ExportAttributes"></a>
The attributes for IPEK generation during export.  
Type: [ExportAttributes](API_ExportAttributes.md) object  
Required: No

 ** [ExportKeyIdentifier](#API_ExportKey_RequestSyntax) **   <a name="paymentcryptography-ExportKey-request-ExportKeyIdentifier"></a>
The `KeyARN` of the key under export from AWS Payment Cryptography.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

 ** [KeyMaterial](#API_ExportKey_RequestSyntax) **   <a name="paymentcryptography-ExportKey-request-KeyMaterial"></a>
The key block format type, for example, TR-34 or TR-31, to use during key material export.  
Type: [ExportKeyMaterial](API_ExportKeyMaterial.md) object  
 **Note: **This object is a Union. Only one member of this object can be specified or returned.  
Required: Yes

## Response Syntax
<a name="API_ExportKey_ResponseSyntax"></a>

```
{
   "WrappedKey": { 
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyMaterial": "string",
      "WrappedKeyMaterialFormat": "string",
      "WrappingKeyArn": "string"
   }
}
```

## Response Elements
<a name="API_ExportKey_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [WrappedKey](#API_ExportKey_ResponseSyntax) **   <a name="paymentcryptography-ExportKey-response-WrappedKey"></a>
The key material under export as a TR-34 WrappedKeyBlock or a TR-31 WrappedKeyBlock. or a RSA WrappedKeyCryptogram.  
Type: [WrappedKey](API_WrappedKey.md) object

## Errors
<a name="API_ExportKey_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_ExportKey_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/ExportKey) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/ExportKey) 

# GetAlias
<a name="API_GetAlias"></a>

Gets the AWS Payment Cryptography key associated with the alias.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [CreateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html) 
+  [DeleteAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html) 
+  [ListAliases](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html) 
+  [UpdateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html) 

## Request Syntax
<a name="API_GetAlias_RequestSyntax"></a>

```
{
   "AliasName": "string"
}
```

## Request Parameters
<a name="API_GetAlias_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [AliasName](#API_GetAlias_RequestSyntax) **   <a name="paymentcryptography-GetAlias-request-AliasName"></a>
The alias of the AWS Payment Cryptography key.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 256.  
Pattern: `alias/[a-zA-Z0-9/_-]+`   
Required: Yes

## Response Syntax
<a name="API_GetAlias_ResponseSyntax"></a>

```
{
   "Alias": { 
      "AliasName": "string",
      "KeyArn": "string"
   }
}
```

## Response Elements
<a name="API_GetAlias_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Alias](#API_GetAlias_ResponseSyntax) **   <a name="paymentcryptography-GetAlias-response-Alias"></a>
The alias of the AWS Payment Cryptography key.  
Type: [Alias](API_Alias.md) object

## Errors
<a name="API_GetAlias_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_GetAlias_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/GetAlias) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/GetAlias) 

# GetCertificateSigningRequest
<a name="API_GetCertificateSigningRequest"></a>

Creates a certificate signing request (CSR) from a key pair.

## Request Syntax
<a name="API_GetCertificateSigningRequest_RequestSyntax"></a>

```
{
   "CertificateSubject": { 
      "City": "string",
      "CommonName": "string",
      "Country": "string",
      "EmailAddress": "string",
      "Organization": "string",
      "OrganizationUnit": "string",
      "StateOrProvince": "string"
   },
   "KeyIdentifier": "string",
   "SigningAlgorithm": "string"
}
```

## Request Parameters
<a name="API_GetCertificateSigningRequest_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [CertificateSubject](#API_GetCertificateSigningRequest_RequestSyntax) **   <a name="paymentcryptography-GetCertificateSigningRequest-request-CertificateSubject"></a>
The metadata used to create the CSR.  
Type: [CertificateSubjectType](API_CertificateSubjectType.md) object  
Required: Yes

 ** [KeyIdentifier](#API_GetCertificateSigningRequest_RequestSyntax) **   <a name="paymentcryptography-GetCertificateSigningRequest-request-KeyIdentifier"></a>
Asymmetric key used for generating the certificate signing request  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

 ** [SigningAlgorithm](#API_GetCertificateSigningRequest_RequestSyntax) **   <a name="paymentcryptography-GetCertificateSigningRequest-request-SigningAlgorithm"></a>
The cryptographic algorithm used to sign your CSR.  
Type: String  
Valid Values: `SHA224 | SHA256 | SHA384 | SHA512`   
Required: Yes

## Response Syntax
<a name="API_GetCertificateSigningRequest_ResponseSyntax"></a>

```
{
   "CertificateSigningRequest": "string"
}
```

## Response Elements
<a name="API_GetCertificateSigningRequest_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [CertificateSigningRequest](#API_GetCertificateSigningRequest_ResponseSyntax) **   <a name="paymentcryptography-GetCertificateSigningRequest-response-CertificateSigningRequest"></a>
The certificate signing request generated using the key pair associated with the key identifier.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 32768.  
Pattern: `[^\[;\]<>]+` 

## Errors
<a name="API_GetCertificateSigningRequest_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_GetCertificateSigningRequest_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/GetCertificateSigningRequest) 

# GetDefaultKeyReplicationRegions
<a name="API_GetDefaultKeyReplicationRegions"></a>

Retrieves the list of AWS Regions where [Multi-Region key replication](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html) is currently enabled for your AWS account.

This operation returns the current Multi-Region key replication configuration. New keys created in your account will be automatically replicated to these regions unless explicitly overridden during key creation.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [EnableDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_EnableDefaultKeyReplicationRegions.html) 
+  [DisableDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DisableDefaultKeyReplicationRegions.html) 

## Response Syntax
<a name="API_GetDefaultKeyReplicationRegions_ResponseSyntax"></a>

```
{
   "EnabledReplicationRegions": [ "string" ]
}
```

## Response Elements
<a name="API_GetDefaultKeyReplicationRegions_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [EnabledReplicationRegions](#API_GetDefaultKeyReplicationRegions_ResponseSyntax) **   <a name="paymentcryptography-GetDefaultKeyReplicationRegions-response-EnabledReplicationRegions"></a>
The list of regions where default key replication is currently enabled for the account.  
New keys created in this account will automatically be replicated to these regions unless explicitly configured otherwise during key creation.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+` 

## Errors
<a name="API_GetDefaultKeyReplicationRegions_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_GetDefaultKeyReplicationRegions_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/GetDefaultKeyReplicationRegions) 

# GetKey
<a name="API_GetKey"></a>

Gets the key metadata for an AWS Payment Cryptography key, including the immutable and mutable attributes specified when the key was created. Returns key metadata including attributes, state, and timestamps, but does not return the actual cryptographic key material.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [CreateKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html) 
+  [DeleteKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html) 
+  [ListKeys](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListKeys.html) 

## Request Syntax
<a name="API_GetKey_RequestSyntax"></a>

```
{
   "KeyIdentifier": "string"
}
```

## Request Parameters
<a name="API_GetKey_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyIdentifier](#API_GetKey_RequestSyntax) **   <a name="paymentcryptography-GetKey-request-KeyIdentifier"></a>
The `KeyARN` of the AWS Payment Cryptography key.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

## Response Syntax
<a name="API_GetKey_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_GetKey_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_GetKey_ResponseSyntax) **   <a name="paymentcryptography-GetKey-response-Key"></a>
Contains the key metadata, including both immutable and mutable attributes for the key, but does not include actual cryptographic key material.  
Type: [Key](API_Key.md) object

## Errors
<a name="API_GetKey_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_GetKey_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/GetKey) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/GetKey) 

# GetParametersForExport
<a name="API_GetParametersForExport"></a>

Gets the export token and the signing key certificate to initiate a TR-34 key export from AWS Payment Cryptography.

The signing key certificate signs the wrapped key under export within the TR-34 key payload. The export token and signing key certificate must be in place and operational before calling [ExportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ExportKey.html). The export token expires in 30 days. You can use the same export token to export multiple keys from your service account.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [ExportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ExportKey.html) 
+  [GetParametersForImport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html) 

## Request Syntax
<a name="API_GetParametersForExport_RequestSyntax"></a>

```
{
   "KeyMaterialType": "string",
   "SigningKeyAlgorithm": "string"
}
```

## Request Parameters
<a name="API_GetParametersForExport_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyMaterialType](#API_GetParametersForExport_RequestSyntax) **   <a name="paymentcryptography-GetParametersForExport-request-KeyMaterialType"></a>
The key block format type (for example, TR-34 or TR-31) to use during key material export. Export token is only required for a TR-34 key export, `TR34_KEY_BLOCK`. Export token is not required for TR-31 key export.  
Type: String  
Valid Values: `TR34_KEY_BLOCK | TR31_KEY_BLOCK | ROOT_PUBLIC_KEY_CERTIFICATE | TRUSTED_PUBLIC_KEY_CERTIFICATE | KEY_CRYPTOGRAM`   
Required: Yes

 ** [SigningKeyAlgorithm](#API_GetParametersForExport_RequestSyntax) **   <a name="paymentcryptography-GetParametersForExport-request-SigningKeyAlgorithm"></a>
The signing key algorithm to generate a signing key certificate. This certificate signs the wrapped key under export within the TR-34 key block. `RSA_2048` is the only signing key algorithm allowed.  
Type: String  
Valid Values: `TDES_2KEY | TDES_3KEY | AES_128 | AES_192 | AES_256 | HMAC_SHA256 | HMAC_SHA384 | HMAC_SHA512 | HMAC_SHA224 | RSA_2048 | RSA_3072 | RSA_4096 | ECC_NIST_P256 | ECC_NIST_P384 | ECC_NIST_P521`   
Required: Yes

## Response Syntax
<a name="API_GetParametersForExport_ResponseSyntax"></a>

```
{
   "ExportToken": "string",
   "ParametersValidUntilTimestamp": number,
   "SigningKeyAlgorithm": "string",
   "SigningKeyCertificate": "string",
   "SigningKeyCertificateChain": "string"
}
```

## Response Elements
<a name="API_GetParametersForExport_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [ExportToken](#API_GetParametersForExport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForExport-response-ExportToken"></a>
The export token to initiate key export from AWS Payment Cryptography. The export token expires after 30 days. You can use the same export token to export multiple keys from the same service account.  
Type: String  
Pattern: `(export-token-[0-9a-zA-Z]{16,64})?` 

 ** [ParametersValidUntilTimestamp](#API_GetParametersForExport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForExport-response-ParametersValidUntilTimestamp"></a>
The validity period of the export token.  
Type: Timestamp

 ** [SigningKeyAlgorithm](#API_GetParametersForExport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForExport-response-SigningKeyAlgorithm"></a>
The algorithm of the signing key certificate for use in TR-34 key block generation. `RSA_2048` is the only signing key algorithm allowed.  
Type: String  
Valid Values: `TDES_2KEY | TDES_3KEY | AES_128 | AES_192 | AES_256 | HMAC_SHA256 | HMAC_SHA384 | HMAC_SHA512 | HMAC_SHA224 | RSA_2048 | RSA_3072 | RSA_4096 | ECC_NIST_P256 | ECC_NIST_P384 | ECC_NIST_P521` 

 ** [SigningKeyCertificate](#API_GetParametersForExport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForExport-response-SigningKeyCertificate"></a>
The signing key certificate in PEM format (base64 encoded) of the public key for signature within the TR-34 key block. The certificate expires after 30 days.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 32768.  
Pattern: `[^\[;\]<>]+` 

 ** [SigningKeyCertificateChain](#API_GetParametersForExport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForExport-response-SigningKeyCertificateChain"></a>
The root certificate authority (CA) that signed the signing key certificate in PEM format (base64 encoded).  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 32768.  
Pattern: `[^\[;\]<>]+` 

## Errors
<a name="API_GetParametersForExport_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_GetParametersForExport_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/GetParametersForExport) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/GetParametersForExport) 

# GetParametersForImport
<a name="API_GetParametersForImport"></a>

Gets the import token and the wrapping key certificate in PEM format (base64 encoded) to initiate a TR-34 WrappedKeyBlock or a RSA WrappedKeyCryptogram import into AWS Payment Cryptography.

The wrapping key certificate wraps the key under import. The import token and wrapping key certificate must be in place and operational before calling [ImportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html). The import token expires in 30 days. You can use the same import token to import multiple keys into your service account.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [GetParametersForExport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForExport.html) 
+  [ImportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html) 

## Request Syntax
<a name="API_GetParametersForImport_RequestSyntax"></a>

```
{
   "KeyMaterialType": "string",
   "WrappingKeyAlgorithm": "string"
}
```

## Request Parameters
<a name="API_GetParametersForImport_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyMaterialType](#API_GetParametersForImport_RequestSyntax) **   <a name="paymentcryptography-GetParametersForImport-request-KeyMaterialType"></a>
The method to use for key material import. Import token is only required for TR-34 WrappedKeyBlock (`TR34_KEY_BLOCK`) and RSA WrappedKeyCryptogram (`KEY_CRYPTOGRAM`).  
Import token is not required for TR-31, root public key cerificate or trusted public key certificate.  
Type: String  
Valid Values: `TR34_KEY_BLOCK | TR31_KEY_BLOCK | ROOT_PUBLIC_KEY_CERTIFICATE | TRUSTED_PUBLIC_KEY_CERTIFICATE | KEY_CRYPTOGRAM`   
Required: Yes

 ** [WrappingKeyAlgorithm](#API_GetParametersForImport_RequestSyntax) **   <a name="paymentcryptography-GetParametersForImport-request-WrappingKeyAlgorithm"></a>
The wrapping key algorithm to generate a wrapping key certificate. This certificate wraps the key under import.  
At this time, `RSA_2048` is the allowed algorithm for TR-34 WrappedKeyBlock import. Additionally, `RSA_2048`, `RSA_3072`, `RSA_4096` are the allowed algorithms for RSA WrappedKeyCryptogram import.  
Type: String  
Valid Values: `TDES_2KEY | TDES_3KEY | AES_128 | AES_192 | AES_256 | HMAC_SHA256 | HMAC_SHA384 | HMAC_SHA512 | HMAC_SHA224 | RSA_2048 | RSA_3072 | RSA_4096 | ECC_NIST_P256 | ECC_NIST_P384 | ECC_NIST_P521`   
Required: Yes

## Response Syntax
<a name="API_GetParametersForImport_ResponseSyntax"></a>

```
{
   "ImportToken": "string",
   "ParametersValidUntilTimestamp": number,
   "WrappingKeyAlgorithm": "string",
   "WrappingKeyCertificate": "string",
   "WrappingKeyCertificateChain": "string"
}
```

## Response Elements
<a name="API_GetParametersForImport_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [ImportToken](#API_GetParametersForImport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForImport-response-ImportToken"></a>
The import token to initiate key import into AWS Payment Cryptography. The import token expires after 30 days. You can use the same import token to import multiple keys to the same service account.  
Type: String  
Pattern: `(import-token-[0-9a-zA-Z]{16,64})?` 

 ** [ParametersValidUntilTimestamp](#API_GetParametersForImport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForImport-response-ParametersValidUntilTimestamp"></a>
The validity period of the import token.  
Type: Timestamp

 ** [WrappingKeyAlgorithm](#API_GetParametersForImport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForImport-response-WrappingKeyAlgorithm"></a>
The algorithm of the wrapping key for use within TR-34 WrappedKeyBlock or RSA WrappedKeyCryptogram.  
Type: String  
Valid Values: `TDES_2KEY | TDES_3KEY | AES_128 | AES_192 | AES_256 | HMAC_SHA256 | HMAC_SHA384 | HMAC_SHA512 | HMAC_SHA224 | RSA_2048 | RSA_3072 | RSA_4096 | ECC_NIST_P256 | ECC_NIST_P384 | ECC_NIST_P521` 

 ** [WrappingKeyCertificate](#API_GetParametersForImport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForImport-response-WrappingKeyCertificate"></a>
The wrapping key certificate in PEM format (base64 encoded) of the wrapping key for use within the TR-34 key block. The certificate expires in 30 days.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 32768.  
Pattern: `[^\[;\]<>]+` 

 ** [WrappingKeyCertificateChain](#API_GetParametersForImport_ResponseSyntax) **   <a name="paymentcryptography-GetParametersForImport-response-WrappingKeyCertificateChain"></a>
The AWS Payment Cryptography root certificate authority (CA) that signed the wrapping key certificate in PEM format (base64 encoded).  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 32768.  
Pattern: `[^\[;\]<>]+` 

## Errors
<a name="API_GetParametersForImport_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_GetParametersForImport_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/GetParametersForImport) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/GetParametersForImport) 

# GetPublicKeyCertificate
<a name="API_GetPublicKeyCertificate"></a>

Gets the public key certificate of the asymmetric key pair that exists within AWS Payment Cryptography.

Unlike the private key of an asymmetric key, which never leaves AWS Payment Cryptography unencrypted, callers with `GetPublicKeyCertificate` permission can download the public key certificate of the asymmetric key. You can share the public key certificate to allow others to encrypt messages and verify signatures outside of AWS Payment Cryptography

 **Cross-account use:** This operation can't be used across different AWS accounts.

## Request Syntax
<a name="API_GetPublicKeyCertificate_RequestSyntax"></a>

```
{
   "KeyIdentifier": "string"
}
```

## Request Parameters
<a name="API_GetPublicKeyCertificate_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyIdentifier](#API_GetPublicKeyCertificate_RequestSyntax) **   <a name="paymentcryptography-GetPublicKeyCertificate-request-KeyIdentifier"></a>
The `KeyARN` of the asymmetric key pair.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

## Response Syntax
<a name="API_GetPublicKeyCertificate_ResponseSyntax"></a>

```
{
   "KeyCertificate": "string",
   "KeyCertificateChain": "string"
}
```

## Response Elements
<a name="API_GetPublicKeyCertificate_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [KeyCertificate](#API_GetPublicKeyCertificate_ResponseSyntax) **   <a name="paymentcryptography-GetPublicKeyCertificate-response-KeyCertificate"></a>
The public key component of the asymmetric key pair in a certificate PEM format (base64 encoded). It is signed by the root certificate authority (CA). The certificate expires in 90 days.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 32768.  
Pattern: `[^\[;\]<>]+` 

 ** [KeyCertificateChain](#API_GetPublicKeyCertificate_ResponseSyntax) **   <a name="paymentcryptography-GetPublicKeyCertificate-response-KeyCertificateChain"></a>
The root certificate authority (CA) that signed the public key certificate in PEM format (base64 encoded) of the asymmetric key pair.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 32768.  
Pattern: `[^\[;\]<>]+` 

## Errors
<a name="API_GetPublicKeyCertificate_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_GetPublicKeyCertificate_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/GetPublicKeyCertificate) 

# ImportKey
<a name="API_ImportKey"></a>

Imports symmetric keys and public key certificates in PEM format (base64 encoded) into AWS Payment Cryptography.

 AWS Payment Cryptography simplifies key exchange by replacing the existing paper-based approach with a modern electronic approach. With `ImportKey` you can import symmetric keys using either symmetric and asymmetric key exchange mechanisms.

For symmetric key exchange, AWS Payment Cryptography uses the ANSI X9 TR-31 norm in accordance with PCI PIN guidelines. And for asymmetric key exchange, AWS Payment Cryptography supports ANSI X9 TR-34 norm, RSA unwrap, and ECDH (Elliptic Curve Diffie-Hellman) key exchange mechanisms. Asymmetric key exchange methods are typically used to establish bi-directional trust between the two parties exhanging keys and are used for initial key exchange such as Key Encryption Key (KEK) or Zone Master Key (ZMK). After which you can import working keys using symmetric method to perform various cryptographic operations within AWS Payment Cryptography.

PCI requires specific minimum key strength of wrapping keys used to protect the keys being exchanged electronically. These requirements can change when PCI standards are revised. The rules specify that wrapping keys used for transport must be at least as strong as the key being protected. For more information on recommended key strength of wrapping keys and key exchange mechanism, see [Importing and exporting keys](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-importexport.html) in the * AWS Payment Cryptography User Guide*.

You can also import a *root public key certificate*, used to sign other public key certificates, or a *trusted public key certificate* under an already established root public key certificate.

 **To import a public root key certificate** 

Using this operation, you can import the public component (in PEM cerificate format) of your private root key. You can use the imported public root key certificate for digital signatures, for example signing wrapping key or signing key in TR-34, within your AWS Payment Cryptography account.

Set the following parameters:
+  `KeyMaterial`: `RootCertificatePublicKey` 
+  `KeyClass`: `PUBLIC_KEY` 
+  `KeyModesOfUse`: `Verify` 
+  `KeyUsage`: `TR31_S0_ASYMMETRIC_KEY_FOR_DIGITAL_SIGNATURE` 
+  `PublicKeyCertificate`: The public key certificate in PEM format (base64 encoded) of the private root key under import.

 **To import a trusted public key certificate** 

The root public key certificate must be in place and operational before you import a trusted public key certificate. Set the following parameters:
+  `KeyMaterial`: `TrustedCertificatePublicKey` 
+  `CertificateAuthorityPublicKeyIdentifier`: `KeyArn` of the `RootCertificatePublicKey`.
+  `KeyModesOfUse` and `KeyUsage`: Corresponding to the cryptographic operations such as wrap, sign, or encrypt that you will allow the trusted public key certificate to perform.
+  `PublicKeyCertificate`: The trusted public key certificate in PEM format (base64 encoded) under import.

 **To import initial keys (KEK or ZMK or similar) using TR-34** 

Using this operation, you can import initial key using TR-34 asymmetric key exchange. In TR-34 terminology, the sending party of the key is called Key Distribution Host (KDH) and the receiving party of the key is called Key Receiving Device (KRD). During the key import process, KDH is the user who initiates the key import and KRD is AWS Payment Cryptography who receives the key.

To initiate TR-34 key import, the KDH must obtain an import token by calling [GetParametersForImport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html). This operation generates an encryption keypair for the purpose of key import, signs the key and returns back the wrapping key certificate (also known as KRD wrapping certificate) and the root certificate chain. The KDH must trust and install the KRD wrapping certificate on its HSM and use it to encrypt (wrap) the KDH key during TR-34 WrappedKeyBlock generation. The import token and associated KRD wrapping certificate expires after 30 days.

Next the KDH generates a key pair for the purpose of signing the encrypted KDH key and provides the public certificate of the signing key to AWS Payment Cryptography. The KDH will also need to import the root certificate chain of the KDH signing certificate by calling `ImportKey` for `RootCertificatePublicKey`. For more information on TR-34 key import, see section [Importing symmetric keys](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-import.html) in the * AWS Payment Cryptography User Guide*.

Set the following parameters:
+  `KeyMaterial`: Use `Tr34KeyBlock` parameters.
+  `CertificateAuthorityPublicKeyIdentifier`: The `KeyARN` of the certificate chain that signed the KDH signing key certificate.
+  `ImportToken`: Obtained from KRD by calling [GetParametersForImport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html).
+  `WrappedKeyBlock`: The TR-34 wrapped key material from KDH. It contains the KDH key under import, wrapped with KRD wrapping certificate and signed by KDH signing private key. This TR-34 key block is typically generated by the KDH Hardware Security Module (HSM) outside of AWS Payment Cryptography.
+  `SigningKeyCertificate`: The public key certificate in PEM format (base64 encoded) of the KDH signing key generated under the root certificate (CertificateAuthorityPublicKeyIdentifier) imported in AWS Payment Cryptography.

 **To import initial keys (KEK or ZMK or similar) using RSA Wrap and Unwrap** 

Using this operation, you can import initial key using asymmetric RSA wrap and unwrap key exchange method. To initiate import, call [GetParametersForImport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html) with `KeyMaterial` set to `KEY_CRYPTOGRAM` to generate an import token. This operation also generates an encryption keypair for the purpose of key import, signs the key and returns back the wrapping key certificate in PEM format (base64 encoded) and its root certificate chain. The import token and associated KRD wrapping certificate expires after 30 days. 

You must trust and install the wrapping certificate and its certificate chain on the sending HSM and use it to wrap the key under export for WrappedKeyCryptogram generation. Next call `ImportKey` with `KeyMaterial` set to `KEY_CRYPTOGRAM` and provide the `ImportToken` and `KeyAttributes` for the key under import.

 **To import working keys using TR-31** 

 AWS Payment Cryptography uses TR-31 symmetric key exchange norm to import working keys. A KEK must be established within AWS Payment Cryptography by using TR-34 key import or by using [CreateKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html). To initiate a TR-31 key import, set the following parameters:
+  `KeyMaterial`: Use `Tr31KeyBlock` parameters.
+  `WrappedKeyBlock`: The TR-31 wrapped key material. It contains the key under import, encrypted using KEK. The TR-31 key block is typically generated by a HSM outside of AWS Payment Cryptography. 
+  `WrappingKeyIdentifier`: The `KeyArn` of the KEK that AWS Payment Cryptography uses to decrypt or unwrap the key under import.

 **To import working keys using ECDH** 

You can also use ECDH key agreement to import working keys as a TR-31 keyblock, where the wrapping key is an ECDH derived key.

To initiate a TR-31 key import using ECDH, both sides must create an ECC key pair with key usage K3 and exchange public key certificates. In AWS Payment Cryptography, you can do this by calling `CreateKey` and then `GetPublicKeyCertificate` to retrieve its public key certificate. Next, you can then generate a TR-31 WrappedKeyBlock using your own ECC key pair, the public certificate of the service's ECC key pair, and the key derivation parameters including key derivation function, hash algorithm, derivation data, and key algorithm. If you have not already done so, you must import the CA chain that issued the receiving public key certificate by calling `ImportKey` with input `RootCertificatePublicKey` for root CA or `TrustedPublicKey` for intermediate CA. To complete the TR-31 key import, you can use the following parameters. It is important that the ECDH key derivation parameters you use should match those used during import to derive the same shared wrapping key within AWS Payment Cryptography.
+  `KeyMaterial`: Use `DiffieHellmanTr31KeyBlock` parameters.
+  `PrivateKeyIdentifier`: The `KeyArn` of the ECC key pair created within AWS Payment Cryptography to derive a shared KEK.
+  `PublicKeyCertificate`: The public key certificate of the receiving ECC key pair in PEM format (base64 encoded) to derive a shared KEK.
+  `CertificateAuthorityPublicKeyIdentifier`: The `keyARN` of the CA that signed the public key certificate of the receiving ECC key pair.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [ExportKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ExportKey.html) 
+  [GetParametersForImport](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html) 

## Request Syntax
<a name="API_ImportKey_RequestSyntax"></a>

```
{
   "Enabled": boolean,
   "KeyCheckValueAlgorithm": "string",
   "KeyMaterial": { ... },
   "ReplicationRegions": [ "string" ],
   "Tags": [ 
      { 
         "Key": "string",
         "Value": "string"
      }
   ]
}
```

## Request Parameters
<a name="API_ImportKey_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [Enabled](#API_ImportKey_RequestSyntax) **   <a name="paymentcryptography-ImportKey-request-Enabled"></a>
Specifies whether import key is enabled.  
Type: Boolean  
Required: No

 ** [KeyCheckValueAlgorithm](#API_ImportKey_RequestSyntax) **   <a name="paymentcryptography-ImportKey-request-KeyCheckValueAlgorithm"></a>
The algorithm that AWS Payment Cryptography uses to calculate the key check value (KCV). It is used to validate the key integrity.  
For TDES keys, the KCV is computed by encrypting 8 bytes, each with value of zero, with the key to be checked and retaining the 3 highest order bytes of the encrypted result. For AES keys, the KCV is computed using a CMAC algorithm where the input data is 16 bytes of zero and retaining the 3 highest order bytes of the encrypted result.  
Type: String  
Valid Values: `CMAC | ANSI_X9_24 | HMAC | SHA_1`   
Required: No

 ** [KeyMaterial](#API_ImportKey_RequestSyntax) **   <a name="paymentcryptography-ImportKey-request-KeyMaterial"></a>
The key or public key certificate type to use during key material import, for example TR-34 or RootCertificatePublicKey.  
Type: [ImportKeyMaterial](API_ImportKeyMaterial.md) object  
 **Note: **This object is a Union. Only one member of this object can be specified or returned.  
Required: Yes

 ** [ReplicationRegions](#API_ImportKey_RequestSyntax) **   <a name="paymentcryptography-ImportKey-request-ReplicationRegions"></a>
A list of AWS Regions for key replication operations.  
Each region in the list must be a valid AWS Region identifier where AWS Payment Cryptography is available. This list is used to specify which regions should be added to or removed from a key's replication configuration.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+`   
Required: No

 ** [Tags](#API_ImportKey_RequestSyntax) **   <a name="paymentcryptography-ImportKey-request-Tags"></a>
Assigns one or more tags to the AWS Payment Cryptography key. Use this parameter to tag a key when it is imported. To tag an existing AWS Payment Cryptography key, use the [TagResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_TagResource.html) operation.  
Each tag consists of a tag key and a tag value. Both the tag key and the tag value are required, but the tag value can be an empty (null) string. You can't have more than one tag on an AWS Payment Cryptography key with the same tag key. If you specify an existing tag key with a different tag value, AWS Payment Cryptography replaces the current tag value with the specified one.  
Don't include personal, confidential or sensitive information in this field. This field may be displayed in plaintext in AWS CloudTrail logs and other output.
Tagging or untagging an AWS Payment Cryptography key can allow or deny permission to the key.
Type: Array of [Tag](API_Tag.md) objects  
Array Members: Minimum number of 0 items. Maximum number of 200 items.  
Required: No

## Response Syntax
<a name="API_ImportKey_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_ImportKey_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_ImportKey_ResponseSyntax) **   <a name="paymentcryptography-ImportKey-response-Key"></a>
The `KeyARN` of the key material imported within AWS Payment Cryptography.  
Type: [Key](API_Key.md) object

## Errors
<a name="API_ImportKey_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_ImportKey_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/ImportKey) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/ImportKey) 

# ListAliases
<a name="API_ListAliases"></a>

Lists the aliases for all keys in the caller's AWS account and AWS Region. You can filter the aliases by `keyARN`. For more information, see [Using aliases](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-managealias.html) in the * AWS Payment Cryptography User Guide*.

This is a paginated operation, which means that each response might contain only a subset of all the aliases. When the response contains only a subset of aliases, it includes a `NextToken` value. Use this value in a subsequent `ListAliases` request to get more aliases. When you receive a response with no NextToken (or an empty or null value), that means there are no more aliases to get.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [CreateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html) 
+  [DeleteAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html) 
+  [GetAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetAlias.html) 
+  [UpdateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html) 

## Request Syntax
<a name="API_ListAliases_RequestSyntax"></a>

```
{
   "KeyArn": "string",
   "MaxResults": number,
   "NextToken": "string"
}
```

## Request Parameters
<a name="API_ListAliases_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyArn](#API_ListAliases_RequestSyntax) **   <a name="paymentcryptography-ListAliases-request-KeyArn"></a>
The `keyARN` for which you want to list all aliases.  
Type: String  
Length Constraints: Minimum length of 70. Maximum length of 150.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:key/[0-9a-zA-Z]{16,64}`   
Required: No

 ** [MaxResults](#API_ListAliases_RequestSyntax) **   <a name="paymentcryptography-ListAliases-request-MaxResults"></a>
Use this parameter to specify the maximum number of items to return. When this value is present, AWS Payment Cryptography does not return more than the specified number of items, but it might return fewer.  
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.  
Type: Integer  
Valid Range: Minimum value of 1. Maximum value of 100.  
Required: No

 ** [NextToken](#API_ListAliases_RequestSyntax) **   <a name="paymentcryptography-ListAliases-request-NextToken"></a>
Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of `NextToken` from the truncated response you just received.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 8192.  
Required: No

## Response Syntax
<a name="API_ListAliases_ResponseSyntax"></a>

```
{
   "Aliases": [ 
      { 
         "AliasName": "string",
         "KeyArn": "string"
      }
   ],
   "NextToken": "string"
}
```

## Response Elements
<a name="API_ListAliases_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Aliases](#API_ListAliases_ResponseSyntax) **   <a name="paymentcryptography-ListAliases-response-Aliases"></a>
The list of aliases. Each alias describes the `KeyArn` contained within.  
Type: Array of [Alias](API_Alias.md) objects

 ** [NextToken](#API_ListAliases_ResponseSyntax) **   <a name="paymentcryptography-ListAliases-response-NextToken"></a>
The token for the next set of results, or an empty or null value if there are no more results.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 8192.

## Errors
<a name="API_ListAliases_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_ListAliases_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/ListAliases) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/ListAliases) 

# ListKeys
<a name="API_ListKeys"></a>

Lists the keys in the caller's AWS account and AWS Region. You can filter the list of keys.

This is a paginated operation, which means that each response might contain only a subset of all the keys. When the response contains only a subset of keys, it includes a `NextToken` value. Use this value in a subsequent `ListKeys` request to get more keys. When you receive a response with no NextToken (or an empty or null value), that means there are no more keys to get.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [CreateKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html) 
+  [DeleteKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html) 
+  [GetKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetKey.html) 

## Request Syntax
<a name="API_ListKeys_RequestSyntax"></a>

```
{
   "KeyState": "string",
   "MaxResults": number,
   "NextToken": "string"
}
```

## Request Parameters
<a name="API_ListKeys_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyState](#API_ListKeys_RequestSyntax) **   <a name="paymentcryptography-ListKeys-request-KeyState"></a>
The key state of the keys you want to list.  
Type: String  
Valid Values: `CREATE_IN_PROGRESS | CREATE_COMPLETE | DELETE_PENDING | DELETE_COMPLETE`   
Required: No

 ** [MaxResults](#API_ListKeys_RequestSyntax) **   <a name="paymentcryptography-ListKeys-request-MaxResults"></a>
Use this parameter to specify the maximum number of items to return. When this value is present, AWS Payment Cryptography does not return more than the specified number of items, but it might return fewer.  
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.  
Type: Integer  
Valid Range: Minimum value of 1. Maximum value of 100.  
Required: No

 ** [NextToken](#API_ListKeys_RequestSyntax) **   <a name="paymentcryptography-ListKeys-request-NextToken"></a>
Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of `NextToken` from the truncated response you just received.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 8192.  
Required: No

## Response Syntax
<a name="API_ListKeys_ResponseSyntax"></a>

```
{
   "Keys": [ 
      { 
         "Enabled": boolean,
         "Exportable": boolean,
         "KeyArn": "string",
         "KeyAttributes": { 
            "KeyAlgorithm": "string",
            "KeyClass": "string",
            "KeyModesOfUse": { 
               "Decrypt": boolean,
               "DeriveKey": boolean,
               "Encrypt": boolean,
               "Generate": boolean,
               "NoRestrictions": boolean,
               "Sign": boolean,
               "Unwrap": boolean,
               "Verify": boolean,
               "Wrap": boolean
            },
            "KeyUsage": "string"
         },
         "KeyCheckValue": "string",
         "KeyState": "string",
         "MultiRegionKeyType": "string",
         "PrimaryRegion": "string"
      }
   ],
   "NextToken": "string"
}
```

## Response Elements
<a name="API_ListKeys_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Keys](#API_ListKeys_ResponseSyntax) **   <a name="paymentcryptography-ListKeys-response-Keys"></a>
The list of keys created within the caller's AWS account and AWS Region.  
Type: Array of [KeySummary](API_KeySummary.md) objects

 ** [NextToken](#API_ListKeys_ResponseSyntax) **   <a name="paymentcryptography-ListKeys-response-NextToken"></a>
The token for the next set of results, or an empty or null value if there are no more results.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 8192.

## Errors
<a name="API_ListKeys_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_ListKeys_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/ListKeys) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/ListKeys) 

# ListTagsForResource
<a name="API_ListTagsForResource"></a>

Lists the tags for an AWS resource.

This is a paginated operation, which means that each response might contain only a subset of all the tags. When the response contains only a subset of tags, it includes a `NextToken` value. Use this value in a subsequent `ListTagsForResource` request to get more tags. When you receive a response with no NextToken (or an empty or null value), that means there are no more tags to get.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [TagResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_TagResource.html) 
+  [UntagResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UntagResource.html) 

## Request Syntax
<a name="API_ListTagsForResource_RequestSyntax"></a>

```
{
   "MaxResults": number,
   "NextToken": "string",
   "ResourceArn": "string"
}
```

## Request Parameters
<a name="API_ListTagsForResource_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [MaxResults](#API_ListTagsForResource_RequestSyntax) **   <a name="paymentcryptography-ListTagsForResource-request-MaxResults"></a>
Use this parameter to specify the maximum number of items to return. When this value is present, AWS Payment Cryptography does not return more than the specified number of items, but it might return fewer.  
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.  
Type: Integer  
Valid Range: Minimum value of 1. Maximum value of 100.  
Required: No

 ** [NextToken](#API_ListTagsForResource_RequestSyntax) **   <a name="paymentcryptography-ListTagsForResource-request-NextToken"></a>
Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of `NextToken` from the truncated response you just received.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 8192.  
Required: No

 ** [ResourceArn](#API_ListTagsForResource_RequestSyntax) **   <a name="paymentcryptography-ListTagsForResource-request-ResourceArn"></a>
The `KeyARN` of the key whose tags you are getting.  
Type: String  
Length Constraints: Minimum length of 70. Maximum length of 150.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:key/[0-9a-zA-Z]{16,64}`   
Required: Yes

## Response Syntax
<a name="API_ListTagsForResource_ResponseSyntax"></a>

```
{
   "NextToken": "string",
   "Tags": [ 
      { 
         "Key": "string",
         "Value": "string"
      }
   ]
}
```

## Response Elements
<a name="API_ListTagsForResource_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [NextToken](#API_ListTagsForResource_ResponseSyntax) **   <a name="paymentcryptography-ListTagsForResource-response-NextToken"></a>
The token for the next set of results, or an empty or null value if there are no more results.  
Type: String  
Length Constraints: Minimum length of 1. Maximum length of 8192.

 ** [Tags](#API_ListTagsForResource_ResponseSyntax) **   <a name="paymentcryptography-ListTagsForResource-response-Tags"></a>
The list of tags associated with a `ResourceArn`. Each tag will list the key-value pair contained within that tag.  
Type: Array of [Tag](API_Tag.md) objects  
Array Members: Minimum number of 0 items. Maximum number of 200 items.

## Errors
<a name="API_ListTagsForResource_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_ListTagsForResource_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/ListTagsForResource) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/ListTagsForResource) 

# RemoveKeyReplicationRegions
<a name="API_RemoveKeyReplicationRegions"></a>

Removes Replication Regions from an existing AWS Payment Cryptography key, disabling the key's availability for cryptographic operations in the specified AWS Regions.

When you remove Replication Regions, the key material is securely deleted from those regions and can no longer be used for cryptographic operations there. This operation is irreversible for the specified AWS Regions. For more information, see [Multi-Region key replication](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html).

**Important**  
Ensure that no active cryptographic operations or applications depend on the key in the regions you're removing before performing this operation.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [AddKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_AddKeyReplicationRegions.html) 
+  [DisableDefaultKeyReplicationRegions](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DisableDefaultKeyReplicationRegions.html) 

## Request Syntax
<a name="API_RemoveKeyReplicationRegions_RequestSyntax"></a>

```
{
   "KeyIdentifier": "string",
   "ReplicationRegions": [ "string" ]
}
```

## Request Parameters
<a name="API_RemoveKeyReplicationRegions_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyIdentifier](#API_RemoveKeyReplicationRegions_RequestSyntax) **   <a name="paymentcryptography-RemoveKeyReplicationRegions-request-KeyIdentifier"></a>
The key identifier (ARN or alias) of the key from which to remove replication regions.  
This key must exist and have replication enabled in the specified regions.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

 ** [ReplicationRegions](#API_RemoveKeyReplicationRegions_RequestSyntax) **   <a name="paymentcryptography-RemoveKeyReplicationRegions-request-ReplicationRegions"></a>
The list of AWS Regions to remove from the key's replication configuration.  
The key will no longer be available for cryptographic operations in these regions after removal. Ensure no active operations depend on the key in these regions before removal.  
Type: Array of strings  
Pattern: `[a-z]{2}-[a-z]{1,16}-[0-9]+`   
Required: Yes

## Response Syntax
<a name="API_RemoveKeyReplicationRegions_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_RemoveKeyReplicationRegions_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_RemoveKeyReplicationRegions_ResponseSyntax) **   <a name="paymentcryptography-RemoveKeyReplicationRegions-response-Key"></a>
The updated key metadata after removing the replication regions.  
This reflects the current state of the key and its updated replication configuration.  
Type: [Key](API_Key.md) object

## Errors
<a name="API_RemoveKeyReplicationRegions_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_RemoveKeyReplicationRegions_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/RemoveKeyReplicationRegions) 

# RestoreKey
<a name="API_RestoreKey"></a>

Cancels a scheduled key deletion during the waiting period. Use this operation to restore a `Key` that is scheduled for deletion.

During the waiting period, the `KeyState` is `DELETE_PENDING` and `deletePendingTimestamp` contains the date and time after which the `Key` will be deleted. After `Key` is restored, the `KeyState` is `CREATE_COMPLETE`, and the value for `deletePendingTimestamp` is removed.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [DeleteKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html) 
+  [StartKeyUsage](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StartKeyUsage.html) 
+  [StopKeyUsage](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StopKeyUsage.html) 

## Request Syntax
<a name="API_RestoreKey_RequestSyntax"></a>

```
{
   "KeyIdentifier": "string"
}
```

## Request Parameters
<a name="API_RestoreKey_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyIdentifier](#API_RestoreKey_RequestSyntax) **   <a name="paymentcryptography-RestoreKey-request-KeyIdentifier"></a>
The `KeyARN` of the key to be restored within AWS Payment Cryptography.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

## Response Syntax
<a name="API_RestoreKey_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_RestoreKey_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_RestoreKey_ResponseSyntax) **   <a name="paymentcryptography-RestoreKey-response-Key"></a>
The key material of the restored key. The `KeyState` will change to `CREATE_COMPLETE` and value for `DeletePendingTimestamp` gets removed.   
Type: [Key](API_Key.md) object

## Errors
<a name="API_RestoreKey_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_RestoreKey_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/RestoreKey) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/RestoreKey) 

# StartKeyUsage
<a name="API_StartKeyUsage"></a>

Enables an AWS Payment Cryptography key, which makes it active for cryptographic operations within AWS Payment Cryptography

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [StopKeyUsage](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StopKeyUsage.html) 

## Request Syntax
<a name="API_StartKeyUsage_RequestSyntax"></a>

```
{
   "KeyIdentifier": "string"
}
```

## Request Parameters
<a name="API_StartKeyUsage_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyIdentifier](#API_StartKeyUsage_RequestSyntax) **   <a name="paymentcryptography-StartKeyUsage-request-KeyIdentifier"></a>
The `KeyArn` of the key.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

## Response Syntax
<a name="API_StartKeyUsage_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_StartKeyUsage_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_StartKeyUsage_ResponseSyntax) **   <a name="paymentcryptography-StartKeyUsage-response-Key"></a>
The `KeyARN` of the AWS Payment Cryptography key activated for use.  
Type: [Key](API_Key.md) object

## Errors
<a name="API_StartKeyUsage_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_StartKeyUsage_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/StartKeyUsage) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/StartKeyUsage) 

# StopKeyUsage
<a name="API_StopKeyUsage"></a>

Disables an AWS Payment Cryptography key, which makes it inactive within AWS Payment Cryptography.

You can use this operation instead of [DeleteKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html) to deactivate a key. You can enable the key in the future by calling [StartKeyUsage](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StartKeyUsage.html).

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [DeleteKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html) 
+  [StartKeyUsage](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StartKeyUsage.html) 

## Request Syntax
<a name="API_StopKeyUsage_RequestSyntax"></a>

```
{
   "KeyIdentifier": "string"
}
```

## Request Parameters
<a name="API_StopKeyUsage_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [KeyIdentifier](#API_StopKeyUsage_RequestSyntax) **   <a name="paymentcryptography-StopKeyUsage-request-KeyIdentifier"></a>
The `KeyArn` of the key.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 322.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:(key/[0-9a-zA-Z]{16,64}|alias/[a-zA-Z0-9/_-]+)$|^alias/[a-zA-Z0-9/_-]+`   
Required: Yes

## Response Syntax
<a name="API_StopKeyUsage_ResponseSyntax"></a>

```
{
   "Key": { 
      "CreateTimestamp": number,
      "DeletePendingTimestamp": number,
      "DeleteTimestamp": number,
      "DeriveKeyUsage": "string",
      "Enabled": boolean,
      "Exportable": boolean,
      "KeyArn": "string",
      "KeyAttributes": { 
         "KeyAlgorithm": "string",
         "KeyClass": "string",
         "KeyModesOfUse": { 
            "Decrypt": boolean,
            "DeriveKey": boolean,
            "Encrypt": boolean,
            "Generate": boolean,
            "NoRestrictions": boolean,
            "Sign": boolean,
            "Unwrap": boolean,
            "Verify": boolean,
            "Wrap": boolean
         },
         "KeyUsage": "string"
      },
      "KeyCheckValue": "string",
      "KeyCheckValueAlgorithm": "string",
      "KeyOrigin": "string",
      "KeyState": "string",
      "MultiRegionKeyType": "string",
      "PrimaryRegion": "string",
      "ReplicationStatus": { 
         "string" : { 
            "Status": "string",
            "StatusMessage": "string"
         }
      },
      "UsageStartTimestamp": number,
      "UsageStopTimestamp": number,
      "UsingDefaultReplicationRegions": boolean
   }
}
```

## Response Elements
<a name="API_StopKeyUsage_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Key](#API_StopKeyUsage_ResponseSyntax) **   <a name="paymentcryptography-StopKeyUsage-response-Key"></a>
The `KeyARN` of the key.  
Type: [Key](API_Key.md) object

## Errors
<a name="API_StopKeyUsage_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_StopKeyUsage_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/StopKeyUsage) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/StopKeyUsage) 

# TagResource
<a name="API_TagResource"></a>

Adds or edits tags on an AWS Payment Cryptography key.

**Note**  
Tagging or untagging an AWS Payment Cryptography key can allow or deny permission to the key.

Each tag consists of a tag key and a tag value, both of which are case-sensitive strings. The tag value can be an empty (null) string. To add a tag, specify a new tag key and a tag value. To edit a tag, specify an existing tag key and a new tag value. You can also add tags to an AWS Payment Cryptography key when you create it with [CreateKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html).

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [ListTagsForResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListTagsForResource.html) 
+  [UntagResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UntagResource.html) 

## Request Syntax
<a name="API_TagResource_RequestSyntax"></a>

```
{
   "ResourceArn": "string",
   "Tags": [ 
      { 
         "Key": "string",
         "Value": "string"
      }
   ]
}
```

## Request Parameters
<a name="API_TagResource_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [ResourceArn](#API_TagResource_RequestSyntax) **   <a name="paymentcryptography-TagResource-request-ResourceArn"></a>
The `KeyARN` of the key whose tags are being updated.  
Type: String  
Length Constraints: Minimum length of 70. Maximum length of 150.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:key/[0-9a-zA-Z]{16,64}`   
Required: Yes

 ** [Tags](#API_TagResource_RequestSyntax) **   <a name="paymentcryptography-TagResource-request-Tags"></a>
One or more tags. Each tag consists of a tag key and a tag value. The tag value can be an empty (null) string. You can't have more than one tag on an AWS Payment Cryptography key with the same tag key. If you specify an existing tag key with a different tag value, AWS Payment Cryptography replaces the current tag value with the new one.  
Don't include personal, confidential or sensitive information in this field. This field may be displayed in plaintext in AWS CloudTrail logs and other output.
To use this parameter, you must have [TagResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_TagResource.html) permission in an IAM policy.  
Don't include personal, confidential or sensitive information in this field. This field may be displayed in plaintext in AWS CloudTrail logs and other output.
Type: Array of [Tag](API_Tag.md) objects  
Array Members: Minimum number of 0 items. Maximum number of 200 items.  
Required: Yes

## Response Elements
<a name="API_TagResource_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.

## Errors
<a name="API_TagResource_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceQuotaExceededException **   
This request would cause a service quota to be exceeded.  
You have reached the maximum number of keys, aliases, or other resources allowed in your account. Review your current usage and consider deleting unused resources or requesting a quota increase.  
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_TagResource_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/TagResource) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/TagResource) 

# UntagResource
<a name="API_UntagResource"></a>

Deletes a tag from an AWS Payment Cryptography key.

**Note**  
Tagging or untagging an AWS Payment Cryptography key can allow or deny permission to the key.

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [ListTagsForResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListTagsForResource.html) 
+  [TagResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_TagResource.html) 

## Request Syntax
<a name="API_UntagResource_RequestSyntax"></a>

```
{
   "ResourceArn": "string",
   "TagKeys": [ "string" ]
}
```

## Request Parameters
<a name="API_UntagResource_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [ResourceArn](#API_UntagResource_RequestSyntax) **   <a name="paymentcryptography-UntagResource-request-ResourceArn"></a>
The `KeyARN` of the key whose tags are being removed.  
Type: String  
Length Constraints: Minimum length of 70. Maximum length of 150.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:key/[0-9a-zA-Z]{16,64}`   
Required: Yes

 ** [TagKeys](#API_UntagResource_RequestSyntax) **   <a name="paymentcryptography-UntagResource-request-TagKeys"></a>
One or more tag keys. Don't include the tag values.  
If the AWS Payment Cryptography key doesn't have the specified tag key, AWS Payment Cryptography doesn't throw an exception or return a response. To confirm that the operation succeeded, use the [ListTagsForResource](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListTagsForResource.html) operation.  
Type: Array of strings  
Array Members: Minimum number of 0 items. Maximum number of 200 items.  
Length Constraints: Minimum length of 1. Maximum length of 128.  
Required: Yes

## Response Elements
<a name="API_UntagResource_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.

## Errors
<a name="API_UntagResource_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_UntagResource_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/UntagResource) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/UntagResource) 

# UpdateAlias
<a name="API_UpdateAlias"></a>

Associates an existing AWS Payment Cryptography alias with a different key. Each alias is associated with only one AWS Payment Cryptography key at a time, although a key can have multiple aliases. The alias and the AWS Payment Cryptography key must be in the same AWS account and AWS Region 

 **Cross-account use:** This operation can't be used across different AWS accounts.

 **Related operations:** 
+  [CreateAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html) 
+  [DeleteAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html) 
+  [GetAlias](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetAlias.html) 
+  [ListAliases](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html) 

## Request Syntax
<a name="API_UpdateAlias_RequestSyntax"></a>

```
{
   "AliasName": "string",
   "KeyArn": "string"
}
```

## Request Parameters
<a name="API_UpdateAlias_RequestParameters"></a>

The request accepts the following data in JSON format.

 ** [AliasName](#API_UpdateAlias_RequestSyntax) **   <a name="paymentcryptography-UpdateAlias-request-AliasName"></a>
The alias whose associated key is changing.  
Type: String  
Length Constraints: Minimum length of 7. Maximum length of 256.  
Pattern: `alias/[a-zA-Z0-9/_-]+`   
Required: Yes

 ** [KeyArn](#API_UpdateAlias_RequestSyntax) **   <a name="paymentcryptography-UpdateAlias-request-KeyArn"></a>
The `KeyARN` for the key that you are updating or removing from the alias.  
Type: String  
Length Constraints: Minimum length of 70. Maximum length of 150.  
Pattern: `arn:aws:payment-cryptography:[a-z]{2}-[a-z]{1,16}-[0-9]+:[0-9]{12}:key/[0-9a-zA-Z]{16,64}`   
Required: No

## Response Syntax
<a name="API_UpdateAlias_ResponseSyntax"></a>

```
{
   "Alias": { 
      "AliasName": "string",
      "KeyArn": "string"
   }
}
```

## Response Elements
<a name="API_UpdateAlias_ResponseElements"></a>

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

 ** [Alias](#API_UpdateAlias_ResponseSyntax) **   <a name="paymentcryptography-UpdateAlias-response-Alias"></a>
The alias name.  
Type: [Alias](API_Alias.md) object

## Errors
<a name="API_UpdateAlias_Errors"></a>

 ** AccessDeniedException **   
You do not have sufficient access to perform this action.  
This exception is thrown when the caller lacks the necessary IAM permissions to perform the requested operation. Verify that your IAM policy includes the required permissions for the specific AWS Payment Cryptography action you're attempting.  
HTTP Status Code: 400

 ** ConflictException **   
This request can cause an inconsistent state for the resource.  
The requested operation conflicts with the current state of the resource. For example, attempting to delete a key that is currently being used, or trying to create a resource that already exists.  
HTTP Status Code: 400

 ** InternalServerException **   
The request processing has failed because of an unknown error, exception, or failure.  
This indicates a server-side error within the AWS Payment Cryptography service. If this error persists, contact support for assistance.  
HTTP Status Code: 500

 ** ResourceNotFoundException **   
The request was denied due to resource not found.  
The specified key, alias, or other resource does not exist in your account or region. Verify that the resource identifier is correct and that the resource exists in the expected region.    
 ** ResourceId **   
The identifier of the resource that was not found.  
This field contains the specific resource identifier (such as a key ARN or alias name) that could not be located.
HTTP Status Code: 400

 ** ServiceUnavailableException **   
The service cannot complete the request.  
The AWS Payment Cryptography service is temporarily unavailable. This is typically a temporary condition - retry your request after a brief delay.  
HTTP Status Code: 500

 ** ThrottlingException **   
The request was denied due to request throttling.  
You have exceeded the rate limits for AWS Payment Cryptography API calls. Implement exponential backoff and retry logic in your application to handle throttling gracefully.  
HTTP Status Code: 400

 ** ValidationException **   
The request was denied due to an invalid request error.  
One or more parameters in your request are invalid. Check the parameter values, formats, and constraints specified in the API documentation.  
HTTP Status Code: 400

## See Also
<a name="API_UpdateAlias_SeeAlso"></a>

For more information about using this API in one of the language-specific AWS SDKs, see the following:
+  [AWS Command Line Interface V2](https://docs.aws.amazon.com/goto/cli2/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for .NET V4](https://docs.aws.amazon.com/goto/DotNetSDKV4/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for C\$1\$1](https://docs.aws.amazon.com/goto/SdkForCpp/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for Go v2](https://docs.aws.amazon.com/goto/SdkForGoV2/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for Java V2](https://docs.aws.amazon.com/goto/SdkForJavaV2/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for JavaScript V3](https://docs.aws.amazon.com/goto/SdkForJavaScriptV3/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for Kotlin](https://docs.aws.amazon.com/goto/SdkForKotlin/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for PHP V3](https://docs.aws.amazon.com/goto/SdkForPHPV3/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for Python](https://docs.aws.amazon.com/goto/boto3/payment-cryptography-2021-09-14/UpdateAlias) 
+  [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/payment-cryptography-2021-09-14/UpdateAlias) 