This project is not covered by Drupal’s security advisory policy.

This module is a fork of commerce_stripe. I use commerce_stripe for a long time in D7 project with some patchs to support 3DS and other features which has never been commited.

It implements Stripe with :

Roadmap

  • Continue cleaning unused commerce_stripe code.
  • Test and fix admin UI payments
  • Make code more generic to be usable by API or another module.
  • Support refund
  • Add manual capture webhook

Why a fork ?

  • Due to SCA https://stripe.com/fr/guides/strong-customer-authentication, i need to improve commerce_stripe and the 3DS implementation which was in progress since many years.
  • At time, commerce_stripe use a very old implementation of Stripe, which is not recommended for SCA (Charges API, tokens etc).
  • Payment intent should be used.
  • There is a lot of cases to deal in commerce_stripe module (stripejs, checkout, elements), cardonfile.
  • There si too much work to do for the time i has to improve the current commerce_stripe module and deal with all cases and implementing the new payement intent solution.
  • I should provide update path and deal with all/new way in one module.
  • Drupal 7 is end of life, i don't want to spend to much time rebuilding something which will die soon.
  • I work with a patched module for too many years.

So

So i decide the fast way to have something working AND helping contributing is to make a fork.
May be this will be integrated in commerce_stripe module, we can discuss it on an issue, but it's not my priority.

References

The issue talking about 3D Secure for commerce_stripe 7.x is #2717383: Add support for 3D Secure.

Supporting organizations: 

Project information

Releases