Cashier-stripe: 3D Secure

[scottybo]

I can't find a mention of this in the docs or any other Github issues.

We're using Cashier (as part of Laravel Spark) to charge our users. Some of our users have 3D Secure enabled on their cards (see: https://stripe.com/docs/sources/three-d-secure) and their payment is failing as it seems that Cashier doesn't handle cards of this type.

Please advise on whether I've made a mistake, ways to fix this, and/or and plans for future support of 3D Secure.

[matejminar]

I am interested in this too.

[otherguy]

Same here!

[djam90]

The 3D Secure process seems a lot more complex than a simple charge, so maybe Cashier doesn't support it... hope it will though, this could potentially lose customers.

[burhanmt]

Same here. Laravel Cashier should have this feature.

[driesvints]

Hmm, I can see this being useful but not sure how this would be implemented. Feel free to send in a PR.

[insology]

Same here, big problems with 3D secure ;)

[rboughani]

Me too, i'm interested in this

[vpratfr]

3D secure seems to be deprecated in favour of the PaymentIntents API. If anyone implements this issue, I guess it would be better to use that instead of the old 3D secure API.

https://stripe.com/docs/payments/payment-intents

[u01jmg3]

Received this email from Stripe yesterday:

In September (14th), the European Union will be introducing rules requiring Strong Customer Authentication (SCA) for many online transactions as part of PSD2 regulation.

Transactions that don’t meet the new SCA requirements may be declined by your customers’ banks.

Stripe has built a new Payments API—PaymentIntents—to get European customers ready for these rule changes. PaymentIntents is designed to recognize when the new SCA rules apply and to trigger any required authentication.

You can learn more in our guide on SCA and read the docs to get started integrating this new SCA-ready payments API.

Get started with PaymentIntents

---

I think the PaymentIntents API is newly out of beta as they state:

ℹ️ PaymentIntents are stable and suitable for use in production. However, not all Stripe products and APIs are fully compatible just yet. We’re working on it!

[ralphmorris]

Has anybody had any joy integrating this with Payment Intents yet?

[driesvints]

@ralphmorris atm I am waiting until they update the migration docs for billing before I take another stab at updating cashier.

[MarGul]

@driesvints Is there any updates on this? The migration guide for Charges are out that (from the small stuff that I could see) Laravel cashier is using?

[driesvints]

@MarGul I noticed Stripe finally published its guide on migrating a billing: https://stripe.com/docs/billing/migration/strong-customer-authentication

So I'll start working on the next version soon.

[pwarnes]

I've been talking with Stripe support about this for a while now, as I've been upgrading my implementation. When I asked about recurring payments, and even something like adding tax to a session using their hosted checkout, the reply is that it simply isn't finished yet :(

Stripe support writes:
There are some features that are not fully built yet, I'm afraid. Subscriptions being one of them. We are releasing new docs on this mid-April with more information around utilising Checkout, subscriptions, and payment intents, including tax.
You can sign up to an email notification here when these docs drop:
https://stripe.com/docs/strong-customer-authentication/payment-intents#sca-updates
Unfortunately, it looks like the missing pieces you need here just aren't yet available.

In the last week I have also noticed significant changes to their documentation with details about the new way of doing things being added.

Personally I have run into enough walls that I've decided to put the project on hold until they finish the feature.

[bilfeldt]

Here are a few relevant quotes from Stripe, provided as information for any readers following this thread. Note that proper implementation of 3D Secure require Payment Intents API which there is a separate Issue for #636

3D Secure Sources API is no longer recommended

Use of Stripe’s legacy 3D Secure Sources API is no longer recommended, and will not support 3D Secure 2. Source

Payment Intents API will be the de facto standard in Stripe

The Payment Intents API also serves as the foundation of other products such as Terminal. In the future, we expect this API to power all payment collection on Stripe. Source

The Payment Intents API is SCA-ready

In September 2019, new European regulation will begin requiring Strong Customer Authentication (SCA) is a new regulatory requirement coming into effect on September 14, 2019 which will impact many European online payments. It requires customers to use two-factor authentication like 3D Secure to verify their purchase. (SCA) for many online payments to European businesses or from European customers. Impacted businesses will need to provide an extra layer of authentication at checkout to help keep their customers safe. The Payment Intents API fully supports SCA—including exemption logic—and ensure that you only ask customers to provide additional authentication when strictly necessary. Source

Further changes needed for subscription in EU

If you are based in Europe and preparing for Strong Customer Authentication (SCA) is a new regulatory requirement coming into effect on September 14, 2019 which will impact many European online payments. It requires customers to use two-factor authentication like 3D Secure to verify their purchase., you will need to make further changes after July 1 in order to perform authentication when saving a card for subsequent off-session payments to qualify for off-session exemptions. This API will be available by July 1. Source

Updates on migration guide

• SCA Migration Guide
• Payment Intents Migration Guide

[driesvints]

The PR for payment intents was merged so v10 will have support for 3D Secure.

[midesweb]

Hi!
Someone can inform the approximate time may take for the release of version 10?
Thanks!

[driesvints]

Probably end of july/begin august.