Payment Cryptography Data Plane
You use the Amazon Web Services Payment Cryptography Data Plane to manage how encryption keys are used for payment-related transaction processing and…
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
You use the Amazon Web Services Payment Cryptography Data Plane to manage how encryption keys are used for payment-related transaction processing and associated cryptographic operations. You can encrypt, decrypt, generate, verify, and translate payment-related cryptographic operations in Amazon Web Services Payment Cryptography. For more information, see Data operations in the Amazon Web Services Payment Cryptography User Guide . To manage your encryption keys, you use the Amazon Web Services Payment Cryptography Control Plane . You can create, import, export, share, manage, and delete keys. You can also manage Identity and Access Management (IAM) policies for keys.
Endpoints 15
- POSTDecrypt data
/keys/:KeyIdentifier/decryptDecrypts ciphertext data to plaintext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme. For more information,… - POSTEncrypt data
/keys/:KeyIdentifier/encryptEncrypts plaintext data to ciphertext using a symmetric (TDES, AES), asymmetric (RSA), or derived (DUKPT or EMV) encryption key scheme. For more information,… - POSTGenerate as2805 kek validation
/as2805kekvalidation/generateGenerates a KekValidationRequest or a KekValidationResponse for node-to-node initialization between payment processing nodes using Australian Standard 2805… - POSTGenerate auth request cryptogram
/cryptogram/generateGenerates an Authorization Request Cryptogram (ARQC) for an EMV chip payment card authorization. For more information, see Generate auth request cryptogram in… - POSTGenerate card validation data
/cardvalidationdata/generateGenerates card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2), or Card… - POSTGenerate mac
/mac/generateGenerates a Message Authentication Code (MAC) cryptogram within Amazon Web Services Payment Cryptography. You can use this operation to authenticate… - POSTGenerate mac emv pin change
/macemvpinchange/generateGenerates an issuer script mac for EMV payment cards that use offline PINs as the cardholder verification method (CVM). This operation generates an… - POSTGenerate pin data
/pindata/generateGenerates pin-related data such as PIN, PIN Verification Value (PVV), PIN Block, and PIN Offset during new card issuance or reissuance. For more information,… - POSTRe encrypt data
/keys/:IncomingKeyIdentifier/reencryptRe-encrypts ciphertext using DUKPT, symmetric, or asymmetric data encryption keys. You can either generate an encryption key within Amazon Web Services… - POSTTranslate key material
/keymaterial/translateTranslates an cryptographic key between different wrapping keys without importing the key into Amazon Web Services Payment Cryptography. This operation can be… - POSTTranslate pin data
/pindata/translateTranslates encrypted PIN block from and to ISO 9564 formats 0,1,3,4. For more information, see Translate PIN data in the Amazon Web Services Payment… - POSTVerify auth request cryptogram
/cryptogram/verifyVerifies Authorization Request Cryptogram (ARQC) for a EMV chip payment card authorization. For more information, see Verify auth request cryptogram in the… - POSTVerify card validation data
/cardvalidationdata/verifyVerifies card-related validation data using algorithms such as Card Verification Values (CVV/CVV2), Dynamic Card Verification Values (dCVV/dCVV2) and Card… - POSTVerify mac
/mac/verifyVerifies a Message Authentication Code (MAC). You can use this operation to verify MAC for message data authentication such as . In this operation, you must… - POSTVerify pin data
/pindata/verifyVerifies pin-related data such as PIN and PIN Offset using algorithms including VISA PVV and IBM3624. For more information, see Verify PIN data in the Amazon…
API details
- Base URL
https://dataplane.payment-cryptography.{region}.amazonaws.com- Authentication
- AWS Signature Version 4 (requests signed with your AWS access key)
- Operations
- 15 operations on 15 pathsPOST 15
- Description format
- AWS Smithy model, API version
2022-02-03 - Links
- Documentation · OpenAPI document
- Listed from
- AWS Smithy API model (aws/api-models-aws) (Apache-2.0)
How to test the Payment Cryptography Data Plane in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Payment Cryptography Data Plane collection, without the publisher's secrets.
- Add your credentialsThis API uses AWS Signature Version 4 (requests signed with your AWS access key). Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “Decrypt data” (POST /keys/:KeyIdentifier/decrypt), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Payment Cryptography Data Plane?
You use the Amazon Web Services Payment Cryptography Data Plane to manage how encryption keys are used for payment-related transaction processing and… It is listed under Payments and has 15 endpoints.
Who publishes the Payment Cryptography Data Plane?
It is listed from Amazon Web Services, Inc.'s public API description (an OpenAPI document), not published by Amazon Web Services, Inc. on Swastik Codes. Anyone who controls amazonaws.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Payment Cryptography Data Plane?
Requests go to https://dataplane.payment-cryptography.{region}.amazonaws.com. Endpoint paths are added to this base URL.
How do I authenticate with the Payment Cryptography Data Plane?
With AWS Signature Version 4 (requests signed with your AWS access key).
How many endpoints does the Payment Cryptography Data Plane have?
15 operations on 15 paths (15 POST).
Is forking the Payment Cryptography Data Plane free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.