Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-5176

Stripe Payments: Always request 3ds for client initiated operations

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Sponsored, 5.11.0-b1
    • Component/s: None
    • Labels:
      None

      Description

      If a payment account is created or a payment initiated by a client we should manually request a 3ds verification using the api (https://docs.stripe.com/payments/3d-secure/authentication-flow#manual-three-ds). Add a setting to the gateway with options something like:

      • Allow Stripe to determine when to present a 3DSecure challenge
      • Present 3D Secure challenge whenever a client saves a payment method or processes an unstored payment method
      • Present 3D Secure challenge whenever a client saves a payment method or makes a manual payment

        Activity

        Hide
        admin Paul Phillips added a comment -

        Just as an FYI, to save a card in India, 3DS must be requested https://support.stripe.com/questions/guide-for-saving-cards-in-india So, those with Indian customers will likely want to select the option to Present 3D Secure challenge whenever a client saves a payment method or makes a manual payment.

        Show
        admin Paul Phillips added a comment - Just as an FYI, to save a card in India, 3DS must be requested https://support.stripe.com/questions/guide-for-saving-cards-in-india So, those with Indian customers will likely want to select the option to Present 3D Secure challenge whenever a client saves a payment method or makes a manual payment.

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            jonathan Jonathan Reissmueller
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              27/Nov/24

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours, 32 minutes
              2h 32m

                Agile