If you receive a successful/expected response from this endpoint, you should
never encounter an encryption/decryption error on the endpoints that require it.
If implementing your own e2ee client, it is advised to make sure your calls pass on
this endpoint before calling the "real" ones.
Creating the value manually, using CLI tools:
$DOMAIN='https://api.paytrace.com/v3' # Adjust to sandbox as needed
CIPHERTEXT=$(openssl pkeyutl -encrypt -inkey <(curl -s "$DOMAIN"/e2ee/public-key.pem | jq -r .data) CIPHERTEXT=$(openssl pkeyutl \
-encrypt \
-inkey <(curl -s "$DOMAIN"/e2ee/public-key.pem | jq -r .data) \
-pkeyopt rsa_padding_mode:oaep \
-pubin -in <(echo -n "$INPUT") | base64 | tr -d'\n')
Testing the value manually, using CLI tools: At this point, you can
manually inspect the value (
), or put it into your HTTP client
of choice, or use the Try It Out button as part of this documentation.
If all is well, you should see a True response
(if not, you will see an error).
Common errors
Ensure you are using the correct padding (RSA-OAEP) and
correct encoding (base64, NOT base64 url encoded).