Skip to main content

25 posts tagged with "iFrame"

View All Tags

iFrame, API v1

  • API v1
  • iFrame

API v1​

BLI 11938 - Improve error messages for vaulted clients attempting to use a vaultless token scheme

  • Previously, vaulted clients were receiving an unknown 9999 error when attempting to use a vaultless token scheme.
  • Now, when a client calls Tokenize with a vaulted TokenEx ID and a vaultless token scheme, a "Token Scheme invalid for profile" error is returned.

iFrame​

BLI 9942 - Token Scheme no longer required in 'CVV Only' mode

  • The TokenScheme parameter is no longer required in the Iframe configuration in CvvOnly mode.

BLI 11739 - Provide validation event prior to blur event

  • New enableValidateOnKeyUp configuration property added. Accepts a Boolean value.
  • This parameter is only supported when PCI is set to true.

BLI 11938 - Improve error messages for vaulted clients attempting to use a vaultless token scheme

  • Previously, vaulted clients were receiving an unknown 9999 error when attempting to use a vaultless token scheme.
  • Now, when a client calls Tokenize with a vaulted TokenEx ID and a vaultless token scheme, users will receive a "Token Scheme invalid for profile" error.

The sha384 hash for the current iFrame JavaScript library in Test is included in the SRI example below:

<script src="https://test-htp.tokenex.com/iframe/Iframe-v3.24.min.js" integrity="sha384-aO+2fnqWgbT92yAhWP/Ho7u/SgTcVGAve7o9St7V0odVVnZNR/Jm5l+Ue+TN374f" crossorigin="anonymous"></script>

iFrame, TGAPI v2

  • iFrame
  • TGAPI v2

iFrame​

BLI 11436 - Parameter added indicating presence of CVV

Added cvvIncluded response parameter to the Tokenize function, which returns true/false to indicate if the card CVV was captured and associated with the token.

Subresource Integrity (SRI) Reference:
<script src="https://htp.tokenex.com/iframe/iframe-v3.23.min.js" integrity="sha384-H95lbmlLUJOldKx1bJsT1IKpTERu3yoHVLAtg4o4ImtVjx6JDQ2OeOYbRNZwEQa1" crossorigin="anonymous"></script>

Transparent Gateway API v2​

BLI 11785 - Reference number header added to Proxy Tokenization

Proxy Tokenization now includes a reference number in the 1tx-reference-number` header of the inbound API request proxied to our client. The reference number is generated and added in the header post authentication and authorization of the inbound API request.