jasehead

Square payments may be an option for Australian stores - Square includes access to Afterpay which is a popular buy-now-pay-later option.

Just reporting back after my first big sales month (June) - I haven't noticed any duplicate payments using PayPal Commerce 1.9.5 but there have still been some duplicate orders being made by customers. The most recent customer said that she had trouble with PayPal accepting her credit card. Can you tell me why I am seeing this in Cubecart's Order Transaction Log: Payer Status: verified Recipient account didn't match specified PayPal account.

From early this month I noticed some outbound emails (from my cubecart store) were being rejected by my host, so not reaching customers. Fortunately, only the Order Cancelled emails are the ones that were tripping SpamAssassin. The three issues (and comments from host support) were: HEXHASH_WORD=2.996 - this will relate to the order number format HTML_IMAGE_ONLY_16=1.048 - I can't see from the logs if there are HTML images included or not PHP_SCRIPT=2.499 - this is the method the email has been sent I changed the store email setting from PHP mail() function to SMTP with SSL (couldn't do this originally due to other limitations), so that fixed the PHP_SCRIPT part. The spam score is now low enough to pass through, but I'd like to reduce it further to avoid future issues. I'm expecting the HTML_IMAGE_ONLY_16 might be the store logo included in the emails? (img src etc.) I don't understand and can not find any explanation of what HEXHASH_WORD means in the context of the Order Cancelled email. Based on the comments from support, I assumed that was the # at the start of the order number eg. #240611-192745-7425; however, the cancelled emails only use the order number without the # at all, eg. 240611-192745-7425. Was support right about the order number format being the trigger? What should I look for and change to reduce the HEXHASH_WORD score assigned by SpamAssassin?

^ Looks like a spam link has been inserted. DO NOT CLICK

My first busy season is in June, which will stress-test this issue. Hopefully, there can be some workaround in place by then.

Stock on hand is updated on processing. The duplicate orders are for items where we have more than one available, so the customer can return and immediately buy another. Otherwise, the customer would not be able to buy because no stock remaining - we have had customers say that they tried though. PLEASE PLEASE PLEASE just put a workaround in place to stop people from placing a second duplicate order. This is only an issue with PayPal Commerce. (swearing removed)

Another duplicate PayPal order today that had to be refunded. I'd be happy with any workaround that stops a customer from duplicating their order within a few seconds (6 seconds this time). Anything that will stop having to refund orders and just suck up the PayPal fee every time. This is costing money, and the problem was flagged 6 months ago.

Yeah, but this is incidental - just an address finder and shouldn't cause any issues. I'll check for updated code, but low priority. I still had duplicate orders with PP Commerce 1.9.3 after the button fix was implemented, but am on 1.9.5 now. Haven't had any duplicates recently only because turnover has dropped in the slow season. I'd expect more from mid-May when things pick up again. Hopefully, there's a fix by then.

No, but only if you have one item. They can purchase again if stock is available. Or they may duplicate the order with missing items and not understand why items are now missing. If they are confused and can proceed with a duplicate order, some customers will click through again. Any workaround would be considered a win if it stops duplicate orders through PayPal and refund losses from PayPal charges.

Or at least an alert to warn against duplicating order/payment.

I'll note here that my store is set to reduce stock on processing, but I've had customers with this same problem even before PayPal Commerce.

Please re-read posts from Dec 15 through to now. I found two comments from Debyink about the confusion process that customers reported. I also note that one of my customers used Microsoft Edge for a duplicate order - so not just a Safari issue.

It's not just a button double-click though. Confusion leads the customer back to the store thinking there is something wrong so they purchase again - need to stop a second order from happening and make it more obvious to the customer that the first order was successful.

No further duplicate tweaks since then?