Turbify was recently required to make some changes to maintain PCI compliance. One of these changes updated the checkout flow to include an additional JavaScript call required to tokenize the credit card number prior to submission.
If your cart has a custom event listener on any button that would normally submit credit card details, your scripts will need to account for this additional step.
Fairly extensive knowledge of JavaScript is needed to make these changes, and you may require the services of a developer. If you need to find a new developer, please visit the Merchant Solutions Developer Network. In the meantime, here are some steps you can perform to get your checkout operational until you can get a a developer to help you:
- Identify the potential problem script by going through each script in your checkout one-by-one. The responsible script will usually be found in one of the Checkout & Registration Manger > Global Settings > Checkout Wrapper > Checkout Regions fields, or in Checkout & Registration Manager > Page Configuration > Order Confirmation > Advanced Settings > HTML Head Section.
- Copy a single script and paste it into a text document.
Important: Make sure you also make note of where the script is located. - Delete the script from its current location.
- Return to the Store Manager and Publish Order Settings.
- After you publish your order settings, place a test order to see if your checkout is working.
- If you can't place an order, paste the script you copied in step 2 back into its original location.
- Repeat steps 1-6 until you find the one that prevents you from checking out.
- Contact your developer and provide them a copy of the problematic script and where you found it.
Your developer will then work to make that script function with the new updates.
