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

Stripe: Look into adding support for 3DS

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.5.0
    • Fix Version/s: 4.7.0-b1
    • Component/s: Gateways
    • Labels:
      None

      Description

      Look into adding support for Stripe 3DS. It sounds like Stripe is coming online in India, and that law there may require 3DS. Also, 3DS is becoming a requirement for EU countries later this year. https://stripe.com/docs/payments/3d-secure

      There are no Sub-Tasks for this issue.

        Activity

        Hide
        admin Paul Phillips added a comment -

        Related to CORE-1085?

        Show
        admin Paul Phillips added a comment - Related to CORE-1085 ?
        Hide
        jonathan Jonathan Reissmueller added a comment -

        Okay so I've been looking into this. Stripe.js creates tokens by using 'Elements'. This is a js library that generates field such as cc number field using iframes. After cc info is entered the element can be sent to create a token and receive it in response.

        The data entered in this iframe is inaccessible; stripe.js does not allow you to fetch it. Instead you need to fetch the token using the API through php. In this way you can retrieve info such as the last 4 and the expiration date of the card that was entered.

        I talked with Tyson about maintaining the current cc form and just populating it with data from the stripe form, but this is not possible since the fields are inaccessible. Instead we need to handle populating those fields in the back end. That being said we may still want to keep and hide the fields in case it is useful for gateways other than stripe. We also need to have a way of avoiding card validation on our end since we don't have the full card number.

        So maybe to lay it out more clearly we need to:

        1. Create a way for the current merchant gateway to replace the admin_clients_account_ccinfo.pdt html, either partially or entirely
        2. Create a way for the current merchant gateway to provide details such as card last4 and expiration date to the accounts model
        3. Allow a null card number to be submitted to the accounts model
        4. Possibly make these dependent on the gateway implementing a new interface
        Show
        jonathan Jonathan Reissmueller added a comment - Okay so I've been looking into this. Stripe.js creates tokens by using 'Elements'. This is a js library that generates field such as cc number field using iframes. After cc info is entered the element can be sent to create a token and receive it in response. The data entered in this iframe is inaccessible; stripe.js does not allow you to fetch it. Instead you need to fetch the token using the API through php. In this way you can retrieve info such as the last 4 and the expiration date of the card that was entered. I talked with Tyson about maintaining the current cc form and just populating it with data from the stripe form, but this is not possible since the fields are inaccessible. Instead we need to handle populating those fields in the back end. That being said we may still want to keep and hide the fields in case it is useful for gateways other than stripe. We also need to have a way of avoiding card validation on our end since we don't have the full card number. So maybe to lay it out more clearly we need to: Create a way for the current merchant gateway to replace the admin_clients_account_ccinfo.pdt html, either partially or entirely Create a way for the current merchant gateway to provide details such as card last4 and expiration date to the accounts model Allow a null card number to be submitted to the accounts model Possibly make these dependent on the gateway implementing a new interface

          People

          • Assignee:
            Unassigned
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              5/Sep/19

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 weeks, 4 days, 19 minutes
              2w 4d 19m

                Agile