Class: Aws::PaymentCryptographyData::Client
- Inherits:
-
Seahorse::Client::Base
- Object
- Seahorse::Client::Base
- Aws::PaymentCryptographyData::Client
- Includes:
- ClientStubs
- Defined in:
- lib/aws-sdk-paymentcryptographydata/client.rb
Overview
An API client for PaymentCryptographyData. To construct a client, you need to configure a :region and :credentials.
client = Aws::PaymentCryptographyData::Client.new(
region: region_name,
credentials: credentials,
# ...
)
For details on configuring region and credentials see the [developer guide](/sdk-for-ruby/v3/developer-guide/setup-config.html).
See #initialize for a full list of supported configuration options.
Class Attribute Summary collapse
- .identifier ⇒ Object readonly private
API Operations collapse
-
#decrypt_data(params = {}) ⇒ Types::DecryptDataOutput
Decrypts ciphertext data to plaintext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme.
-
#encrypt_data(params = {}) ⇒ Types::EncryptDataOutput
Encrypts plaintext data to ciphertext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme.
-
#generate_as_2805_kek_validation(params = {}) ⇒ Types::GenerateAs2805KekValidationOutput
Establishes node-to-node initialization between payment processing nodes such as an acquirer, issuer or payment network using Australian Standard 2805 (AS2805).
-
#generate_card_validation_data(params = {}) ⇒ Types::GenerateCardValidationDataOutput
Generates card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2), or Card Security Codes (CSC).
-
#generate_mac(params = {}) ⇒ Types::GenerateMacOutput
Generates a Message Authentication Code (MAC) cryptogram within Amazon Web Services Payment Cryptography.
-
#generate_mac_emv_pin_change(params = {}) ⇒ Types::GenerateMacEmvPinChangeOutput
Generates an issuer script mac for EMV payment cards that use offline PINs as the cardholder verification method (CVM).
-
#generate_pin_data(params = {}) ⇒ Types::GeneratePinDataOutput
Generates pin-related data such as PIN, PIN Verification Value (PVV), PIN Block, and PIN Offset during new card issuance or reissuance.
-
#re_encrypt_data(params = {}) ⇒ Types::ReEncryptDataOutput
Re-encrypt ciphertext using DUKPT or Symmetric data encryption keys.
-
#translate_key_material(params = {}) ⇒ Types::TranslateKeyMaterialOutput
Translates an cryptographic key between different wrapping keys without importing the key into Amazon Web Services Payment Cryptography.
-
#translate_pin_data(params = {}) ⇒ Types::TranslatePinDataOutput
Translates encrypted PIN block from and to ISO 9564 formats 0,1,3,4.
-
#verify_auth_request_cryptogram(params = {}) ⇒ Types::VerifyAuthRequestCryptogramOutput
Verifies Authorization Request Cryptogram (ARQC) for a EMV chip payment card authorization.
-
#verify_card_validation_data(params = {}) ⇒ Types::VerifyCardValidationDataOutput
Verifies card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2) and Card Security Codes (CSC).
-
#verify_mac(params = {}) ⇒ Types::VerifyMacOutput
Verifies a Message Authentication Code (MAC).
-
#verify_pin_data(params = {}) ⇒ Types::VerifyPinDataOutput
Verifies pin-related data such as PIN and PIN Offset using algorithms including VISA PVV and IBM3624.
Class Method Summary collapse
- .errors_module ⇒ Object private
Instance Method Summary collapse
- #build_request(operation_name, params = {}) ⇒ Object private
-
#initialize(options) ⇒ Client
constructor
A new instance of Client.
- #waiter_names ⇒ Object deprecated private Deprecated.
Constructor Details
#initialize(options) ⇒ Client
Returns a new instance of Client.
473 474 475 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 473 def initialize(*args) super end |
Class Attribute Details
.identifier ⇒ Object (readonly)
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
2451 2452 2453 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 2451 def identifier @identifier end |
Class Method Details
.errors_module ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
2454 2455 2456 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 2454 def errors_module Errors end |
Instance Method Details
#build_request(operation_name, params = {}) ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 2424 def build_request(operation_name, params = {}) handlers = @handlers.for(operation_name) tracer = config.telemetry_provider.tracer_provider.tracer( Aws::Telemetry.module_to_tracer_name('Aws::PaymentCryptographyData') ) context = Seahorse::Client::RequestContext.new( operation_name: operation_name, operation: config.api.operation(operation_name), client: self, params: params, config: config, tracer: tracer ) context[:gem_name] = 'aws-sdk-paymentcryptographydata' context[:gem_version] = '1.49.0' Seahorse::Client::Request.new(handlers, context) end |
#decrypt_data(params = {}) ⇒ Types::DecryptDataOutput
Decrypts ciphertext data to plaintext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme. For more information, see [Decrypt data][1] in the *Amazon Web Services Payment Cryptography User Guide*.
You can use an decryption key generated within Amazon Web Services Payment Cryptography, or you can import your own decryption key by calling [ImportKey][2]. For this operation, the key must have KeyModesOfUse set to Decrypt. In asymmetric decryption, Amazon Web Services Payment Cryptography decrypts the ciphertext using the private component of the asymmetric encryption key pair. For data encryption outside of Amazon Web Services Payment Cryptography, you can export the public component of the asymmetric key pair by calling [GetPublicCertificate][3].
This operation also supports dynamic keys, allowing you to pass a dynamic decryption key as a TR-31 WrappedKeyBlock. This can be used when key material is frequently rotated, such as during every card transaction, and there is need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. To decrypt using dynamic keys, the keyARN is the Key Encryption Key (KEK) of the TR-31 wrapped decryption key material. The incoming wrapped key shall have a key purpose of D0 with a mode of use of B or D. For more information, see [Using Dynamic Keys][4] in the *Amazon Web Services Payment Cryptography User Guide*.
For symmetric and DUKPT decryption, Amazon Web Services Payment Cryptography supports TDES and AES algorithms. For EMV decryption, Amazon Web Services Payment Cryptography supports TDES algorithms. For asymmetric decryption, Amazon Web Services Payment Cryptography supports RSA.
When you use TDES or TDES DUKPT, the ciphertext data length must be a multiple of 8 bytes. For AES or AES DUKPT, the ciphertext data length must be a multiple of 16 bytes. For RSA, it sould be equal to the key size unless padding is enabled.
For information about valid keys for this operation, see
- Understanding key attributes][5
-
and [Key types for specific data
operations][6] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
EncryptData
- GetPublicCertificate][3
- ImportKey][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/decrypt-data.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/use-cases-acquirers-dynamickeys.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [6]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
621 622 623 624 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 621 def decrypt_data(params = {}, = {}) req = build_request(:decrypt_data, params) req.send_request() end |
#encrypt_data(params = {}) ⇒ Types::EncryptDataOutput
Encrypts plaintext data to ciphertext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme. For more information, see [Encrypt data][1] in the *Amazon Web Services Payment Cryptography User Guide*.
You can generate an encryption key within Amazon Web Services Payment Cryptography by calling [CreateKey][2]. You can import your own encryption key by calling [ImportKey][3].
For this operation, the key must have KeyModesOfUse set to Encrypt. In asymmetric encryption, plaintext is encrypted using public component. You can import the public component of an asymmetric key pair created outside Amazon Web Services Payment Cryptography by calling [ImportKey][3].
This operation also supports dynamic keys, allowing you to pass a dynamic encryption key as a TR-31 WrappedKeyBlock. This can be used when key material is frequently rotated, such as during every card transaction, and there is need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. To encrypt using dynamic keys, the keyARN is the Key Encryption Key (KEK) of the TR-31 wrapped encryption key material. The incoming wrapped key shall have a key purpose of D0 with a mode of use of B or D. For more information, see [Using Dynamic Keys][4] in the *Amazon Web Services Payment Cryptography User Guide*.
For symmetric and DUKPT encryption, Amazon Web Services Payment Cryptography supports TDES and AES algorithms. For EMV encryption, Amazon Web Services Payment Cryptography supports TDES algorithms.For asymmetric encryption, Amazon Web Services Payment Cryptography supports RSA.
When you use TDES or TDES DUKPT, the plaintext data length must be a multiple of 8 bytes. For AES or AES DUKPT, the plaintext data length must be a multiple of 16 bytes. For RSA, it sould be equal to the key size unless padding is enabled.
To encrypt using DUKPT, you must already have a BDK (Base Derivation Key) key in your account with KeyModesOfUse set to DeriveKey, or you can generate a new DUKPT key by calling [CreateKey][2]. To encrypt using EMV, you must already have an IMK (Issuer Master Key) key in your account with KeyModesOfUse set to DeriveKey.
For information about valid keys for this operation, see
- Understanding key attributes][5
-
and [Key types for specific data
operations][6] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
DecryptData
- GetPublicCertificate][7
- ImportKey][3
-
ReEncryptData
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/encrypt-data.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/use-cases-acquirers-dynamickeys.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [6]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html [7]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html
789 790 791 792 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 789 def encrypt_data(params = {}, = {}) req = build_request(:encrypt_data, params) req.send_request() end |
#generate_as_2805_kek_validation(params = {}) ⇒ Types::GenerateAs2805KekValidationOutput
Establishes node-to-node initialization between payment processing nodes such as an acquirer, issuer or payment network using Australian Standard 2805 (AS2805).
During node-to-node initialization, both communicating nodes must validate that they possess the correct Key Encrypting Keys (KEKs) before proceeding with session key exchange. In AS2805, the sending KEK (KEKs) of one node corresponds to the receiving KEK (KEKr) of its partner node. Each node uses its KEK to encrypt and decrypt session keys exchanged between the nodes. A KEK can be created or imported into Amazon Web Services Payment Cryptography using either the
- CreateKey][1
-
or [ImportKey][2] operations.
The node initiating communication can use GenerateAS2805KekValidation to generate a combined KEK validation request and KEK validation response to send to the partnering node for validation. When invoked, the API internally generates a random sending key encrypted under KEKs and provides a receiving key encrypted under KEKr as response. The initiating node sends the response returned by this API to its partner for validation.
For information about valid keys for this operation, see
- Understanding key attributes][3
-
and [Key types for specific data
operations][4] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
875 876 877 878 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 875 def generate_as_2805_kek_validation(params = {}, = {}) req = build_request(:generate_as_2805_kek_validation, params) req.send_request() end |
#generate_card_validation_data(params = {}) ⇒ Types::GenerateCardValidationDataOutput
Generates card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2), or Card Security Codes (CSC). For more information, see
- Generate card data][1
-
in the *Amazon Web Services Payment
Cryptography User Guide*.
This operation generates a CVV or CSC value that is printed on a payment credit or debit card during card production. The CVV or CSC, PAN (Primary Account Number) and expiration date of the card are required to check its validity during transaction processing. To begin this operation, a CVK (Card Verification Key) encryption key is required. You can use [CreateKey][2] or [ImportKey][3] to establish a CVK within Amazon Web Services Payment Cryptography. The KeyModesOfUse should be set to Generate and Verify for a CVK encryption key.
For information about valid keys for this operation, see
- Understanding key attributes][4
-
and [Key types for specific data
operations][5] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- ImportKey][3
-
VerifyCardValidationData
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/generate-card-data.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
991 992 993 994 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 991 def generate_card_validation_data(params = {}, = {}) req = build_request(:generate_card_validation_data, params) req.send_request() end |
#generate_mac(params = {}) ⇒ Types::GenerateMacOutput
Generates a Message Authentication Code (MAC) cryptogram within Amazon Web Services Payment Cryptography.
You can use this operation to authenticate card-related data by using known data values to generate MAC for data validation between the sending and receiving parties. This operation uses message data, a secret encryption key and MAC algorithm to generate a unique MAC value for transmission. The receiving party of the MAC must use the same message data, secret encryption key and MAC algorithm to reproduce another MAC value for comparision.
You can use this operation to generate a DUPKT, CMAC, HMAC or EMV MAC by setting generation attributes and algorithm to the associated values. The MAC generation encryption key must have valid values for KeyUsage such as TR31_M7_HMAC_KEY for HMAC generation, and the key must have KeyModesOfUse set to Generate.
For information about valid keys for this operation, see
- Understanding key attributes][1
-
and [Key types for specific data
operations][2] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
VerifyMac
^
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
1098 1099 1100 1101 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 1098 def generate_mac(params = {}, = {}) req = build_request(:generate_mac, params) req.send_request() end |
#generate_mac_emv_pin_change(params = {}) ⇒ Types::GenerateMacEmvPinChangeOutput
Generates an issuer script mac for EMV payment cards that use offline PINs as the cardholder verification method (CVM).
This operation generates an authenticated issuer script response by appending the incoming message data (APDU command) with the target encrypted PIN block in ISO2 format. The command structure and method to send the issuer script update to the card is not defined by this operation and is typically determined by the applicable payment card scheme.
The primary inputs to this operation include the incoming new encrypted pinblock, PIN encryption key (PEK), issuer master key (IMK), primary account number (PAN), and the payment card derivation method.
The operation uses two issuer master keys - secure messaging for confidentiality (IMK-SMC) and secure messaging for integrity (IMK-SMI). The SMC key is used to internally derive a key to secure the pin, while SMI key is used to internally derive a key to authenticate the script reponse as per the [EMV 4.4 - Book 2 - Security and Key Management][1] specification.
This operation supports Amex, EMV2000, EMVCommon, Mastercard and Visa derivation methods, each requiring specific input parameters. Users must follow the specific derivation method and input parameters defined by the respective payment card scheme.
<note markdown=“1”> Use GenerateMac operation when sending a script update to an EMV card that does not involve PIN change. When assigning IAM permissions, it is important to understand that EncryptData using EMV keys and GenerateMac perform similar functions to this command.
</note>
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
EncryptData
-
GenerateMac
1265 1266 1267 1268 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 1265 def generate_mac_emv_pin_change(params = {}, = {}) req = build_request(:generate_mac_emv_pin_change, params) req.send_request() end |
#generate_pin_data(params = {}) ⇒ Types::GeneratePinDataOutput
Generates pin-related data such as PIN, PIN Verification Value (PVV), PIN Block, and PIN Offset during new card issuance or reissuance. For more information, see [Generate PIN data][1] in the *Amazon Web Services Payment Cryptography User Guide*.
PIN data is never transmitted in clear to or from Amazon Web Services Payment Cryptography. This operation generates PIN, PVV, or PIN Offset and then encrypts it using Pin Encryption Key (PEK) to create an EncryptedPinBlock for transmission from Amazon Web Services Payment Cryptography. This operation uses a separate Pin Verification Key (PVK) for VISA PVV generation.
Using ECDH key exchange, you can receive cardholder selectable PINs into Amazon Web Services Payment Cryptography. The ECDH derived key protects the incoming PIN block. You can also use it for reveal PIN, wherein the generated PIN block is protected by the ECDH derived key before transmission from Amazon Web Services Payment Cryptography. For more information on establishing ECDH derived keys, see the
- Generating keys][2
-
in the *Amazon Web Services Payment Cryptography
User Guide*.
For information about valid keys for this operation, see
- Understanding key attributes][3
-
and [Key types for specific data
operations][4] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
GenerateCardValidationData
-
TranslatePinData
-
VerifyPinData
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/generate-pin-data.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/create-keys.html [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
1432 1433 1434 1435 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 1432 def generate_pin_data(params = {}, = {}) req = build_request(:generate_pin_data, params) req.send_request() end |
#re_encrypt_data(params = {}) ⇒ Types::ReEncryptDataOutput
Re-encrypt ciphertext using DUKPT or Symmetric data encryption keys.
You can either generate an encryption key within Amazon Web Services Payment Cryptography by calling [CreateKey][1] or import your own encryption key by calling [ImportKey][2]. The KeyArn for use with this operation must be in a compatible key state with KeyModesOfUse set to Encrypt.
This operation also supports dynamic keys, allowing you to pass a dynamic encryption key as a TR-31 WrappedKeyBlock. This can be used when key material is frequently rotated, such as during every card transaction, and there is need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. To re-encrypt using dynamic keys, the keyARN is the Key Encryption Key (KEK) of the TR-31 wrapped encryption key material. The incoming wrapped key shall have a key purpose of D0 with a mode of use of B or D. For more information, see [Using Dynamic Keys][3] in the *Amazon Web Services Payment Cryptography User Guide*.
For symmetric and DUKPT encryption, Amazon Web Services Payment Cryptography supports TDES and AES algorithms. To encrypt using DUKPT, a DUKPT key must already exist within your account with KeyModesOfUse set to DeriveKey or a new DUKPT can be generated by calling [CreateKey][1].
For information about valid keys for this operation, see
- Understanding key attributes][4
-
and [Key types for specific data
operations][5] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
DecryptData
-
EncryptData
- GetPublicCertificate][6
- ImportKey][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/use-cases-acquirers-dynamickeys.html [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html [6]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html
1600 1601 1602 1603 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 1600 def re_encrypt_data(params = {}, = {}) req = build_request(:re_encrypt_data, params) req.send_request() end |
#translate_key_material(params = {}) ⇒ Types::TranslateKeyMaterialOutput
Translates an cryptographic key between different wrapping keys without importing the key into Amazon Web Services Payment Cryptography.
This operation can be used when key material is frequently rotated, such as during every card transaction, and there is a need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. It translates short-lived transaction keys such as
- PEK][1
-
generated for each transaction and wrapped with an [ECDH][2]
derived wrapping key to another [KEK][3] wrapping key.
Before using this operation, you must first request the public key certificate of the ECC key pair generated within Amazon Web Services Payment Cryptography to establish an ECDH key agreement. In TranslateKeyData, the service uses its own ECC key pair, public certificate of receiving ECC key pair, and the key derivation parameters to generate a derived key. The service uses this derived key to unwrap the incoming transaction key received as a TR31WrappedKeyBlock and re-wrap using a user provided KEK to generate an outgoing Tr31WrappedKeyBlock.
For information about valid keys for this operation, see
- Understanding key attributes][4
-
and [Key types for specific data
operations][5] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- CreateKey][6
- GetPublicCertificate][7
- ImportKey][8
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.pek [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.ecdh [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/terminology.html#terms.kek [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html [6]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [7]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetPublicKeyCertificate.html [8]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html
1704 1705 1706 1707 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 1704 def translate_key_material(params = {}, = {}) req = build_request(:translate_key_material, params) req.send_request() end |
#translate_pin_data(params = {}) ⇒ Types::TranslatePinDataOutput
Translates encrypted PIN block from and to ISO 9564 formats 0,1,3,4. For more information, see [Translate PIN data][1] in the *Amazon Web Services Payment Cryptography User Guide*.
PIN block translation involves changing a PIN block from one encryption key to another and optionally change its format. PIN block translation occurs entirely within the HSM boundary and PIN data never enters or leaves Amazon Web Services Payment Cryptography in clear text. The encryption key transformation can be from PEK (Pin Encryption Key) to BDK (Base Derivation Key) for DUKPT or from BDK for DUKPT to PEK.
Amazon Web Services Payment Cryptography also supports use of dynamic keys and ECDH (Elliptic Curve Diffie-Hellman) based key exchange for this operation.
Dynamic keys allow you to pass a PEK as a TR-31 WrappedKeyBlock. They can be used when key material is frequently rotated, such as during every card transaction, and there is need to avoid importing short-lived keys into Amazon Web Services Payment Cryptography. To translate PIN block using dynamic keys, the keyARN is the Key Encryption Key (KEK) of the TR-31 wrapped PEK. The incoming wrapped key shall have a key purpose of P0 with a mode of use of B or D. For more information, see [Using Dynamic Keys][2] in the *Amazon Web Services Payment Cryptography User Guide*.
Using ECDH key exchange, you can receive cardholder selectable PINs into Amazon Web Services Payment Cryptography. The ECDH derived key protects the incoming PIN block, which is translated to a PEK encrypted PIN block for use within the service. You can also use ECDH for reveal PIN, wherein the service translates the PIN block from PEK to a ECDH derived encryption key. For more information on establishing ECDH derived keys, see the [Creating keys][3] in the *Amazon Web Services Payment Cryptography User Guide*.
The allowed combinations of PIN block format translations are guided by PCI. It is important to note that not all encrypted PIN block formats (example, format 1) require PAN (Primary Account Number) as input. And as such, PIN block format that requires PAN (example, formats 0,3,4) cannot be translated to a format (format 1) that does not require a PAN for generation.
For information about valid keys for this operation, see
- Understanding key attributes][4
-
and [Key types for specific data
operations][5] in the *Amazon Web Services Payment Cryptography User Guide*.
<note markdown=“1”> Amazon Web Services Payment Cryptography currently supports ISO PIN block 4 translation for PIN block built using legacy PAN length. That is, PAN is the right most 12 digits excluding the check digits.
</note>
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
GeneratePinData
-
VerifyPinData
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/translate-pin-data.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/use-cases-acquirers-dynamickeys.html [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/create-keys.html [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
1922 1923 1924 1925 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 1922 def translate_pin_data(params = {}, = {}) req = build_request(:translate_pin_data, params) req.send_request() end |
#verify_auth_request_cryptogram(params = {}) ⇒ Types::VerifyAuthRequestCryptogramOutput
Verifies Authorization Request Cryptogram (ARQC) for a EMV chip payment card authorization. For more information, see [Verify auth request cryptogram][1] in the *Amazon Web Services Payment Cryptography User Guide*.
ARQC generation is done outside of Amazon Web Services Payment Cryptography and is typically generated on a point of sale terminal for an EMV chip card to obtain payment authorization during transaction time. For ARQC verification, you must first import the ARQC generated outside of Amazon Web Services Payment Cryptography by calling [ImportKey][2]. This operation uses the imported ARQC and an major encryption key (DUKPT) created by calling [CreateKey][3] to either provide a boolean ARQC verification result or provide an APRC (Authorization Response Cryptogram) response using Method 1 or Method
-
The
ARPC_METHOD_1usesAuthResponseCodeto generate ARPC and
ARPC_METHOD_2 uses CardStatusUpdate to generate ARPC.
For information about valid keys for this operation, see
- Understanding key attributes][4
-
and [Key types for specific data
operations][5] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
VerifyCardValidationData
-
VerifyPinData
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/data-operations.verifyauthrequestcryptogram.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [4]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
2057 2058 2059 2060 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 2057 def verify_auth_request_cryptogram(params = {}, = {}) req = build_request(:verify_auth_request_cryptogram, params) req.send_request() end |
#verify_card_validation_data(params = {}) ⇒ Types::VerifyCardValidationDataOutput
Verifies card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2) and Card Security Codes (CSC). For more information, see
- Verify card data][1
-
in the *Amazon Web Services Payment Cryptography
User Guide*.
This operation validates the CVV or CSC codes that is printed on a payment credit or debit card during card payment transaction. The input values are typically provided as part of an inbound transaction to an issuer or supporting platform partner. Amazon Web Services Payment Cryptography uses CVV or CSC, PAN (Primary Account Number) and expiration date of the card to check its validity during transaction processing. In this operation, the CVK (Card Verification Key) encryption key for use with card data verification is same as the one in used for GenerateCardValidationData.
For information about valid keys for this operation, see
- Understanding key attributes][2
-
and [Key types for specific data
operations][3] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
GenerateCardValidationData
-
VerifyAuthRequestCryptogram
-
VerifyPinData
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/verify-card-data.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
2177 2178 2179 2180 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 2177 def verify_card_validation_data(params = {}, = {}) req = build_request(:verify_card_validation_data, params) req.send_request() end |
#verify_mac(params = {}) ⇒ Types::VerifyMacOutput
Verifies a Message Authentication Code (MAC).
You can use this operation to verify MAC for message data authentication such as . In this operation, you must use the same message data, secret encryption key and MAC algorithm that was used to generate MAC. You can use this operation to verify a DUPKT, CMAC, HMAC or EMV MAC by setting generation attributes and algorithm to the associated values.
For information about valid keys for this operation, see
- Understanding key attributes][1
-
and [Key types for specific data
operations][2] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
GenerateMac
^
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
2279 2280 2281 2282 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 2279 def verify_mac(params = {}, = {}) req = build_request(:verify_mac, params) req.send_request() end |
#verify_pin_data(params = {}) ⇒ Types::VerifyPinDataOutput
Verifies pin-related data such as PIN and PIN Offset using algorithms including VISA PVV and IBM3624. For more information, see [Verify PIN data][1] in the *Amazon Web Services Payment Cryptography User Guide*.
This operation verifies PIN data for user payment card. A card holder PIN data is never transmitted in clear to or from Amazon Web Services Payment Cryptography. This operation uses PIN Verification Key (PVK) for PIN or PIN Offset generation and then encrypts it using PIN Encryption Key (PEK) to create an EncryptedPinBlock for transmission from Amazon Web Services Payment Cryptography.
For information about valid keys for this operation, see
- Understanding key attributes][2
-
and [Key types for specific data
operations][3] in the *Amazon Web Services Payment Cryptography User Guide*.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
-
GeneratePinData
-
TranslatePinData
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/verify-pin-data.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/crypto-ops-validkeys-ops.html
2415 2416 2417 2418 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 2415 def verify_pin_data(params = {}, = {}) req = build_request(:verify_pin_data, params) req.send_request() end |
#waiter_names ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
2444 2445 2446 |
# File 'lib/aws-sdk-paymentcryptographydata/client.rb', line 2444 def waiter_names [] end |