`io="keep" attribute breaks button clickability + evto.io ERR_INVALID_REDIRECT on payment links
Answered
We are using io="keep" on our Pay My Balance button to bypass the broken evto.io shortlink redirect, but the attribute is making the button unclickable in email clients. We need two things:
- A fix for the evto.io ERR_INVALID_REDIRECT error so shortlinks work properly
- Confirmation of the correct syntax for io="keep" so it doesn't break button clickability
We need payment links to be both clickable AND not broken by the shortlink redirect. Please advise on the correct implementation.
The same question You can't vote. Please authorize!
We are having our web team take a look and will let you know what they advise.
We are having our web team take a look and will let you know what they advise.
Hi Brittany,
I wanted to flag that waiting another 24 hours for a response on this isn't going to work for us — we have real customers waiting on contracts right now and need to get this resolved as quickly as possible today.
Here is where we are technically:
Our custom-styled contract page is working beautifully except for one remaining issue. The signature pad works, sign_contract() validates correctly and returns true — but we cannot get the contract to submit to your backend without triggering payment validation errors ("You must enter an amount to pay" / "You must enter an account number").
We need answers to two specific questions from your dev team:
Question 1: After sign_contract() returns true, what is the correct programmatic method to submit #signature_form to your backend without triggering the page-level payment validation handler? We have tried jQuery('#signature_form').submit(), document.getElementById('io-sign-btn').click(), and direct AJAX — all trigger payment validation.
Question 2: What version of jSignature does IO bundle, and is there a supported method to change the pen color after initialization?
We really appreciate everything you've done on this so far and just need to get this across the finish line. Any help you can get us today would mean a lot.
Thank you so much,
Gilbert Bounce LLC
Hi Brittany,
I wanted to flag that waiting another 24 hours for a response on this isn't going to work for us — we have real customers waiting on contracts right now and need to get this resolved as quickly as possible today.
Here is where we are technically:
Our custom-styled contract page is working beautifully except for one remaining issue. The signature pad works, sign_contract() validates correctly and returns true — but we cannot get the contract to submit to your backend without triggering payment validation errors ("You must enter an amount to pay" / "You must enter an account number").
We need answers to two specific questions from your dev team:
Question 1: After sign_contract() returns true, what is the correct programmatic method to submit #signature_form to your backend without triggering the page-level payment validation handler? We have tried jQuery('#signature_form').submit(), document.getElementById('io-sign-btn').click(), and direct AJAX — all trigger payment validation.
Question 2: What version of jSignature does IO bundle, and is there a supported method to change the pen color after initialization?
We really appreciate everything you've done on this so far and just need to get this across the finish line. Any help you can get us today would mean a lot.
Thank you so much,
Gilbert Bounce LLC
Subject: Contract Page Issue - Resolved on Our End
Hi Brittany,
Just wanted to give you a quick update — we were able to resolve the custom contract page issue on our end. No further action needed on your side for this one.
Thank you for your help and patience while we worked through it!
Best,
Gilbert Bounce LLC
Subject: Contract Page Issue - Resolved on Our End
Hi Brittany,
Just wanted to give you a quick update — we were able to resolve the custom contract page issue on our end. No further action needed on your side for this one.
Thank you for your help and patience while we worked through it!
Best,
Gilbert Bounce LLC
Thank you for the update. Please let us know if you need anything else.
Thank you for the update. Please let us know if you need anything else.
Replies have been locked on this page!