Statement Descriptor Changes Resulting In Chargebacks

  • Resolved codeconnectptyltd

    (@codeconnectptyltd)


    1 year, 9 months ago

    Hello Team,

    since your plugin has removed the ability to set the actual statement descriptor and only allows the statement_descriptor_suffix to be tagged on the end, our business has begun suffering chargebacks.

    We have a legal entity under which our stripe account trades and that legal entity has multiple business trading names.

    Setting the suffix removes enough of the static statement descriptor that the legal entity cannot be identified.

    According to the Stripe API documentation, card charges can set the statement_descriptor on a PaymentIntent dynamically providing it’s combined with a statement_descriptor_suffix .

    I understand that you are doing this by adding the statement_descriptor_suffix  but you’re not allowing us to set the statement_descriptor dynamically and it’s only taking that from the stripe account’s static statement descriptor.

    For card charges, providing a dynamic statement descriptor requires the statement_descriptor_suffix value. For non-card charges, if you set a value only for statement_descriptor on a PaymentIntent, Stripe uses it in place of the account statement descriptor (static descriptor).

    https://docs.stripe.com/get-started/account/statement-descriptors#dynamic

    Allowing us to set both would solve the issue.

    This change has cost us significantly due to chargebacks.

    Looking forward to high quality support on this issue.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Shameem – a11n

    (@shameemreza)

    1 year, 9 months ago

    Hi @codeconnectptyltd

    I understand that the inability to set the statement descriptor dynamically has led to chargebacks for your business, and we apologize for the inconvenience this has caused.

    As per the Stripe API documentation, the statement descriptor can indeed be set dynamically along with a statement_descriptor_suffix. However, our plugin currently only supports the statement_descriptor_suffix, which is appended to the account’s static statement descriptor.

    Since this is something that needs to be handled by the coding or developer, I would suggest you add your ideas as a feature request, which is where developers go to look for future plugin features and improvements. However, I noticed that you’ve already added a comment on the earlier closed report here.

    If you need a faster resolution, we recommend asking development questions on the #developers channel of the WooCommerce Community Slack. Many of our developers hang out there and will be able to offer insights into your question. You can also seek help from the following:

    I wish I could help more, but hopefully, this gets you going in the right direction to get the job done.

    Thread Starter codeconnectptyltd

    (@codeconnectptyltd)

    1 year, 9 months ago

    I am a developer. Which hooks can I use to set this myself for certain?

    Can the hook below help? It’s not really documented as to exactly what the functionality is.

    wc_stripe_description

    Zee

    (@doublezed2)

    1 year, 9 months ago

    Hello codeconnectptyltd,

    Thank you for your reply.

    Your question is about coding and modifying the plugin’s default functionality.
    As per forum guidelines, I cannot assist you with this request.

    I understand you are a web developer, but still I recommend you consult with fellow developers at Woo Community Slack or the Woo Community Facebook group.

    I hope this helps. 🙂

    Best regards.

    Thread Starter codeconnectptyltd

    (@codeconnectptyltd)

    1 year, 9 months ago

    I am so disgusted by the change. This change has cost our business thousands of dollars so far and the best you lot can do is shrug your shoulders.

    Since this change I am constantly fighting chargebacks and disputed transactions at $25 per dispute not to mention the lost revenue that takes months to come back.

    Other sites of our running older versions of the plugin continue to be able to set the statement descriptor as desired and do not face any chargebacks!

    I’m looking for another implementation and will be moving all of my clients and our own sites away from this plugin like the plague…

    1 star reviews incoming!

    Zee

    (@doublezed2)

    1 year, 9 months ago

    Hello codeconnectptyltd,

    Thank you for your reply.

    I understand how frustrating and costly this change has been for your business, and the impact it’s had.

    Please note that this change was implemented by Stripe. As of January 2, 2024, the use of the statement_descriptor parameter for PaymentIntents for card charges is no longer supported. This is a Stripe policy change that we must adhere to, and it affects all users, not just those using the latest version of the plugin.

    You may check this Github issue for more details.

    I realize this is not the response you were hoping for, but we’re here to support you in any way we can. If you have any further questions or need assistance with something else, please don’t hesitate to reach out.

    Best regards.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Statement Descriptor Changes Resulting In Chargebacks’ is closed to new replies.