IMPORTANT: Today’s update to the UAT (Non-Production) CardConnect Hosted iFrame Tokenizer includes additional validation to ensure that integrated iFrames are coded following standard best practices. Specifically, it is important that all special characters (including curly braces {}
)provided within the iFrame URL parameters are properly URL-encoded, as described in iFrame Styling.
Failure to properly encode the URL string will result in an HTTP 400 Bad Request error.
The deployment of these changes to the production environment has been postponed to allow additional time for integrators to develop and test the necessary changes.
If your business's software or application is directly integrated with any of the CardConnect products, we advise that you test transactions in our UAT environment to confirm that these changes will not impact payment processing within the production environment.
More information on this change to the iFrame Tokenizer can be found here: https://developer.cardconnect.com/hosted-iframe-tokenizer#whats-new
If you notice any issues as you test, please submit the form included in the following link and our support teams will assist you. https://cardconnect.com/uat-support