Customers being charged for 11 tickets instead of 2

[christopherakess]

Charles Phillips spoke with Kamran during the office hours webinar concerning this issue. I'm posting the requested information.

Order numbers:

1608071458464499153
1608021121579599775
1608021153388099775

Salesforce Org ID: 00DA0000000KMEp

Charles' numbers: 609-341-4715 (office); 609-799-5155 (cell)
My number: 609-341-4787

[CnP.Support]

Good day christopherakess

Our team has finally managed to duplicate this issue. It is the strangest case and this is how it happens.

In an anonymous event only:

1. Select a quantity from any level
2. Go to the payment page
3. AUTOCOMPLETE the credit card information - The next behavior will not happen if not the autocomplete of credit card is not used.
4. In Chrome ONLY the system adds a random value to level 2 only. This update occurs only to "item 2" in the list and only in Chrome when credit card has been autocompleted. We have tested this with Opera, Firefox, Chrome, Vivaldi, Blisk, and Edge with no issues. We have duplicated this in Chrome 51, 52, and 53 Dev.

The above is not consistent either. We have tested this on 10 computers and it has consistently happened in 3 computers and not others. What is strange is on the machines it happens it only happens to level 2 and only in Chrome. in some systems using the same Chrome version it does not happen.

Our team is working on this and trying to determine why it is happening in Chrome and why only to item 2. We will have an update on this as soon as we are confident we understand what the issue is.

Sorry for the inconvenience. So strange indeed.

[christopherakess]

As Charles mentioned during the call, our own testing of the form in Chrome (OS) 52 (on a 14-Q029wm Chromebook) yielded the same results.

[CnP.Support]

Good day christopherakess

Earlier today we upgraded your instance with a fix for this issue. The version installed in your instance is the beta release & not yet released to appExchange. The release has a coupe of new changes which are not part of your event & will not affect you. These features are still under testing.

Please make sure we have access for a month so we update you with new releases prior to the final release.

Please keep us posted on any issues you may experience but the release you have is very close to the final release and we do not expect any issues.

[christopherakess]

I've added access for a whole month for you.

So far, everything looks fine in testing with my HP 14-q029wm Chromebook,

Good day christopherakess

Earlier today we upgraded your instance with a fix for this issue. The version installed in your instance is the beta release & not yet released to appExchange. The release has a coupe of new changes which are not part of your event & will not affect you. These features are still under testing.

Please make sure we have access for a month so we update you with new releases prior to the final release.

Please keep us posted on any issues you may experience but the release you have is very close to the final release and we do not expect any issues.

[CnP.Support]

Good day christopherakess

We have come across this bug in Chrome as reported here: https://bugs.chromium.org/p/chromium...tail?id=406247

The issue is in Chrome and the autofill is simply taking the 2 digit credit card expiration date and assigns it to other 2 digit fields, in this field item 2 of the list and since it is a pull down menu it matches the behavior of the credit card expiration date. Simply the credit card expiration date is being used by Chrome to fill the other 2 digit pull down menu - quantity.

Strange.. we have not managed to prove that this is indeed the case as reported in the bugs in Chromium project.

Our workaround will fix this issue.

[christopherakess]

Thank you for the update.

Good day christopherakess

We have come across this bug in Chrome as reported here: https://bugs.chromium.org/p/chromium...tail?id=406247

The issue is in Chrome and the autofill is simply taking the 2 digit credit card expiration date and assigns it to other 2 digit fields, in this field item 2 of the list and since it is a pull down menu it matches the behavior of the credit card expiration date. Simply the credit card expiration date is being used by Chrome to fill the other 2 digit pull down menu - quantity.

Strange.. we have not managed to prove that this is indeed the case as reported in the bugs in Chromium project.

Our workaround will fix this issue.

[CnP.Support.AM]

Good day @christopherakess

We have upgraded your instance with latest versions of our apps which has been released Today.

It is absolutely important that you re-establish connection between Click & Pledge and Salesforce. With this update C&P Accounts are no longer needed to be added to Salesforce as the connection will automatically add the required information to Salesforce. It is extremely important that you login to the portal & re-establish connection. To establish connection please see the following KB article: http://help.clickandpledge.com/custo...and-salesforce

Release notes:
• API Class Library 4.3000: http://cnp.mn/1S5jL0v
• Previous release notes: http://manual.clickandpledge.com/Sal...ase-Notes.html

• PaaS 9.6006: http://cnp.mn/2czx5yo
• Previous release notes: http://manual.clickandpledge.com/Sal...ase-Notes.html

• Event 4.4005: http://cnp.mn/2czwWuD
• Previous release notes: http://manual.clickandpledge.com/Sal...ase-Notes.html

You may also join our Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

We also love to know what you think about our platform. Please review our apps on AppExchange:

• Payment: https://appexchange.salesforce.com/l...3JGBvEAO&tab=r
• Event: https://appexchange.salesforce.com/l...5vRQ9EAM&tab=r

Please let us know if we can be of any further assistance.