sasquatchms

Purchased Pro!

Oh I didn’t even see that you offered a pro version.

Each time I update the plugin this would get overwritten. Instead, can you provide a snippet of code for me to use in my functions.php file of my child theme?

I used to have W3 and WC configured just right so that AJAX worked great. However I had to uninstall W3 to troubleshoot an issue, and now I also cannot seem to get it running right again after reinstalling. No AJAX functionality works anymore on my site.

Hi thanks for confirming about the API!

I have not had time to test the saved card feature. I actually don’t use saved cards on my site so I may not be the best person to test that.

Thanks for clarifying! Very cool.

Oh okay, cool, so I can remove the functions code since you are adding it by default? Thanks for the heads up!

How does the change affect refunds?

I am running an unmodified version of the plugin, by the way.

Empressed, this is a Stripe “best practice” which improves fraud protection. This is an important feature, I would recommend leaving it in tact, and instead configuring your Stripe account to match your business/branding.

Cheers

3. Added receipt_email in charge creation for fraud tracking.

Thanks!

I have this exact problem, what is the solution?

Screenshot

Fantastic, thank you!

Hey there again,

I reached out to Stripe with a request to look at a couple transactions and the metadata passed by this plugin and to let me know if everything that CAN be passed IS being passed, and in the correct way. This was the response:

“Thanks for reaching out for confirmation concerning your anti-fraud metadata, it’s good to be thorough! I looked through the metadata you have connected to those two charges you mentioned above, and they look great! Especially the customers IP address, which is an integral part of our fraud prevention system. The only thing you might be missing would be to make sure that when your customer supplies their email address, that you are associating that email address parameter with the receipt_email parameter, as this will show us that this was where a receipt would be sent if you were to send a receipt to a customer, which is also a big piece when we run the information through our system.”

So, according to this response, your plugin is passing the info in the correct way, with the one exception of the email address in the metadata. It should be passed as ‘receipt_email’ instead of ‘billing_email’.

FYI I tested and it works. Cheers!

Thanks much for all your efforts!