• Resolved Tomasz Dziuda

    (@dziudek)


    Hi,

    Today I have discovered that my clients website is making a lot of unnecessary API requests (to r.stripe.com endpoint) on:

    * product pages
    * cart pages
    * checkout pages

    Especially it is strange for product pages and cart pages, because we have stripe checkout available only on the checkout page not on product pages.

    As I have seen here: https://wordpress.org/support/topic/excessive-get-and-post-requests-on-non-checkout-pages/

    Adding:

    
    add_filter( ‘wc_stripe_load_scripts_on_product_page_when_prbs_disabled’, ‘__return_false’ );
    add_filter( ‘wc_stripe_load_scripts_on_cart_page_when_prbs_disabled’, ‘__return_false’ );
    

    Should help with this, but I have 2 questions:

    1) What means when_prbs_disabled? Especially what is prbs?
    2) It is necessary to make some additional configuration changes in the Stripe account? I have read somewhere that these requests can be connected with fraud detection. I want to avoid situation when lack of these requests will cause problems for normal customers, but of course I want to get rid off these requests, because in my opinion such tracking on the mentioned pages is unnecessary.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Doug – a11n

    (@dougaitken)

    Automattic Happiness Engineer

    Hi @dziudek

    prbs – Express Payment buttons, or Payment Request Buttons.

    There is some context in this GitHub Issue here – https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2192

    I have read somewhere that these requests can be connected with fraud detection.

    Indeed, the second comment on that linked GitHub Issue explains that a bit.

    I hope this helps, have a great day!

    Thanks,

    Thread Starter Tomasz Dziuda

    (@dziudek)

    @dougaitken – thank you for your reply.

    Can you extend your answer to:

    > 2) It is necessary to make some additional configuration changes in the Stripe account? I have read somewhere that these requests can be connected with fraud detection. I want to avoid situation when lack of these requests will cause problems for normal customers, but of course I want to get rid off these requests, because in my opinion such tracking on the mentioned pages is unnecessary.

    I just want to be sure that disabling this “feature”:

    – won’t cause any negative impact to “normal” customers
    – won’t require any additional changes on the Stripe account

    The mentioned answer in my opinion only explains why these requests are made, but not mention if it is necessary and how to properly disable it.

    Thread Starter Tomasz Dziuda

    (@dziudek)

    Hi @dougaitken – any news in this topic?

    I really want to disable this “feature”, but as it can cause some hard to detect side effect I want to consult it with plugin support 🙂

    Plugin Support Pepe (woo-hc)

    (@anastas10s)

    Hi there @dziudek 👋

    I really want to disable this “feature”, but as it can cause some hard to detect side effect I want to consult it with plugin support 🙂

    Thanks for reaching back. Per the response published in the other forum thread, there were only three requests registered; nothing excessive.

    Are you noticing any performance issues on said client website? Could you provide some further information on it, if so, please?

    Otherwise, kindly note that the main reason for loading stripe.js on product, cart and checkout pages is better fraud detection, see https://stripe.com/docs/js/including.

    Since the plugin’s source code is published on GitHub, that enables you to experiment with it. Provided the experimentation is done in a controlled environment and with an understanding that it is outside the scope of support.

    I trust that points you in the right direction, but if you have more questions, let us know. We’re happy to help.

    Thread Starter Tomasz Dziuda

    (@dziudek)

    @anastas10s – I do not know how you have check it, but I see 11 requests when filtering by “stripe” phrase and 15 requests when I have checked all Fetch requests (it can be even more if you are using some additional fingerprinting methods like pixel images).

    Please see: https://ibb.co/mR9Ptzf

    Are you noticing any performance issues on said client website? Could you provide some further information on it, if so, please?

    Any additional request affects perfomance, so I want to remove as much unnecessary requests as possible.

    Your fraud detection mechanism seems to be very offensive.

    And I still did not get an answer to this question, which is crucial in this topic:

    2) It is necessary to make some additional configuration changes in the Stripe account? I have read somewhere that these requests can be connected with fraud detection. I want to avoid situation when lack of these requests will cause problems for normal customers, but of course I want to get rid off these requests, because in my opinion such tracking on the mentioned pages is unnecessary.

    I want to know if removing these scripts from all pages excepting checkout can affect our customers – I did not get any clear answer from your support.

    Hello,

    Your fraud detection mechanism seems to be very offensive.

    I recommend to check out the Stripe ToS, they are clear about privacy and anti-fraud mechanisms.

    Any additional request affects perfomance, so I want to remove as much unnecessary requests as possible.

    Checking if a transaction could be fraudulent is always necessary, the more secure your checkout page is, the better. If the site is pretty slow, and you would like to speed it up, I’d recommend to check out this documentation:
    https://woocommerce.com/document/troubleshooting-a-slow-site/

    2) It is necessary to make some additional configuration changes in the Stripe account? I have read somewhere that these requests can be connected with fraud detection. I want to avoid situation when lack of these requests will cause problems for normal customers, but of course I want to get rid off these requests, because in my opinion such tracking on the mentioned pages is unnecessary.

    Stripe is a platform that have really strict anti-fraud policies, it is for security reasons. Disabling or minimizing this process is not recommended for your business.

    Finally, please consider that not taking care of all the security levels when making a transaction could end up in receiving more payment disputes, friendly fraud payments, or unwanted refund requests.

    I hope this provides clarity. Let us know if there are any questions.

    Thread Starter Tomasz Dziuda

    (@dziudek)

    Stripe is a platform that have really strict anti-fraud policies, it is for security reasons. Disabling or minimizing this process is not recommended for your business.

    Finally, please consider that not taking care of all the security levels when making a transaction could end up in receiving more payment disputes, friendly fraud payments, or unwanted refund requests.

    Ok, that’s a strong argument – thank you for explaining this case. So I won’t change the default behaviours in this case.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Unnecessary Stripe API requests on website’ is closed to new replies.