• Resolved sasquatchms

    (@sasquatchms)


    Hello again, I was going through Stripe’s documentation on fraud prevention and found this: https://support.stripe.com/questions/avoiding-fraud-and-disputes

    Specifically:

    “To fully utilize our fraud detection tools, Stripe users should:

    1 – When creating charges, send customers’ names and e-mail addresses. These can be captured directly from a form with Stripe.js or included in Customer-creation API calls. If you don’t use Stripe.js or Customer objects, you can include e-mails in the description field on charges.”

    In the next version of your plugin can you include the customer e-mail address in the description field of the charges so Stripe can use that data for anti-fraud purposes? Maybe go a step further and create a Stripe customer record for each transaction using customer-creation API calls?

    I also noticed the customer name is being passed with a dash (“-“) between first and last name. For example John-Doe instead of John Doe. I am concerned this may cause issues with Stripe’s anti-fraud methods, can you verify and fix if needed?

    Thanks, keep up the good work!!

    https://www.ads-software.com/plugins/stripe-woocommerce-addon/

Viewing 15 replies - 16 through 30 (of 30 total)
  • Thread Starter sasquatchms

    (@sasquatchms)

    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’.

    Plugin Author nazrulhassanmca

    (@nazrulhassanmca)

    Hi I did saw the message 41 minutes after you posted but i was away so here is what you like to be added https://awesomescreenshot.com/02d4y4ib63 from https://stripe.com/docs/api#create_charge

    now billing_email is an woocommerce parameter that the woocommerce order receipts are sent to so that will continue to go in metadata as billing email as that is dynamic value from woocoommerce

    However i will add another parameter receipt_email that will also carry billing email from woocommerce

    I will update the code and let you know on this

    Plugin Author nazrulhassanmca

    (@nazrulhassanmca)

    You need to go in plug in file and one line below line no 326 on plugin version 1.0.2

    ‘receipt_email’ => $wc_order->billing_email,

    and thats it it will take that to charges

    then you will receive in charges like this one https://awesomescreenshot.com/04d4y4jz1c ( link expires in a month)

    Plugin Author nazrulhassanmca

    (@nazrulhassanmca)

    This will be included in all next releases

    Thread Starter sasquatchms

    (@sasquatchms)

    Fantastic, thank you!

    Thread Starter sasquatchms

    (@sasquatchms)

    3. Added receipt_email in charge creation for fraud tracking.

    Thanks!

    Hello

    Please can you help. We just updated this plugin and now all customers are receiving a receipt of payment directly from Stripe – thinking this is something to do with this change… Added receipt_email in charge creation for fraud tracking
    Is there a way to disable this???
    Our customers already receive a receipt and now they are getting a 2nd receipt directly from Stripe – this is not good if your Stripe account is in a different name to the business account.

    Thanks

    Plugin Author nazrulhassanmca

    (@nazrulhassanmca)

    Comment out line no 328 on version 1.0.3

    Do you mean delete line 328???

    How do I do this??? I can see the line numbers when I edit the plugin?

    Plugin Author nazrulhassanmca

    (@nazrulhassanmca)

    i mean comment out line no just place 2 slashes(/) in front of line

    like this //

    OK – but I can’t see any line number, are you able to provide the line of code so I can search for it?

    Plugin Author nazrulhassanmca

    (@nazrulhassanmca)

    search for this words

    ‘receipt_email’ => $wc_order->billing_email,

    i am happy to provide support buy you should be happy to donate

    still if you are not able to do download the plugin file open in a text editor like notepad++ change it and re upload

    Thanks

    Thanks – just donated.

    All working now… not sure if you should keep this feature in future updates as most people will have a receipt system organised. Stripe’s system is very basic and receiving 2 receipts is very confusing for the customer.

    Thanks for your help.

    Plugin Author nazrulhassanmca

    (@nazrulhassanmca)

    Thank you just with release we can put the info in changelog so one who like can use and one who dont like wont use

    Thanks for donation

    Thread Starter sasquatchms

    (@sasquatchms)

    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

Viewing 15 replies - 16 through 30 (of 30 total)
  • The topic ‘Requested features for improved fraud protection’ is closed to new replies.