mac_emv_pin_changes
Creates, updates, deletes, gets or lists a mac_emv_pin_changes resource.
Overview​
| Name | mac_emv_pin_changes |
| Type | Resource |
| Id | aws.payment_cryptography_data.mac_emv_pin_changes |
Fields​
The following fields are returned by SELECT queries:
SELECT not supported for this resource, use SHOW METHODS to view available operations for the resource.
Methods​
The following methods are available for this resource:
| Name | Accessible by | Required Params | Optional Params | Description |
|---|---|---|---|---|
generate_mac_emv_pin_change | exec | region, NewPinPekIdentifier, NewEncryptedPinBlock, PinBlockFormat, SecureMessagingIntegrityKeyIdentifier, SecureMessagingConfidentialityKeyIdentifier, MessageData, DerivationMethodAttributes | 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 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. 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. Cross-account use: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see Resource-based policies. Related operations: EncryptData GenerateMac |
Parameters​
Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.
| Name | Datatype | Description |
|---|---|---|
region | string | AWS region (default: us-east-1) |
Lifecycle Methods​
- generate_mac_emv_pin_change
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 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. 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. Cross-account use: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see Resource-based policies. Related operations: EncryptData GenerateMac
EXEC aws.payment_cryptography_data.mac_emv_pin_changes.generate_mac_emv_pin_change
@region='{{ region }}' --required
@@json=
'{
"NewPinPekIdentifier": "{{ NewPinPekIdentifier }}",
"NewEncryptedPinBlock": "{{ NewEncryptedPinBlock }}",
"PinBlockFormat": "{{ PinBlockFormat }}",
"SecureMessagingIntegrityKeyIdentifier": "{{ SecureMessagingIntegrityKeyIdentifier }}",
"SecureMessagingConfidentialityKeyIdentifier": "{{ SecureMessagingConfidentialityKeyIdentifier }}",
"MessageData": "{{ MessageData }}",
"DerivationMethodAttributes": "{{ DerivationMethodAttributes }}"
}'
;