Problem/Motivation
I received a note from Stripe a few months back detailing that Revolut Pay would automatically be turned on around January 2026. I've been periodically looking at the setup since. Today - I notice that Revolut Pay has indeed been turned on for one of our live sites...
If a transaction is attempted (I did this on test) - we end up with:
Drupal\commerce_payment\Exception\PaymentGatewayException: The selected stripe payment method type(stripe_revolut_pay) is not currently supported. in Drupal\commerce_stripe\Plugin\Commerce\PaymentGateway\StripePaymentElement->createPaymentMethodFromStripePaymentMethod()
Which is fair enough.
Steps to reproduce
Go through checkout and notice that Revolut Pay appears as one of the options in the Payment Element.
Proposed resolution
Login into your Stripe account and disable the Payment method until the method is fully supported...
Comments
Comment #2
jonathanshawI didn't see the email, but it had been turned on for me, and recently, so thanks @newaytech.
I've created an issue to support Revolut: #3571494: Add a Revolut payment method.
Comment #3
anybodyYes we ran into the same error for other payment methods... beneath implementing them, we should maybe add an issue to better handle unsupported payment methods, or even better, only allow supported ones to be selected by customers (and let site owners know)
Comment #4
tomtech commented@anybody,
Unfortunately, when creating the payment intent, stripe only allows:
1. Auto
2. Site send over a specific list
We trie sending over the specific list, but this causes an exception with Stripe, if something in the list is NOT enabled on the stripe account.
This leaves us with Auto.
The best fix is to round out and complete all the payment methods. :) We are getting there, but never fast enough.
Otherwise, it is up to each site to not enable payment methods in their Stripe account that we don't support yet in the module. This would normally happen during development/site building, but with Stripe now magically enabling payment methods on accounts, that makes this a more complex site maintenance task.
Comment #5
anybodyThanks @tomtech yes, indeed I imagined reasons like that.
Absolutely!
See the subissues here: #3408951: Refactor Stripe payment element for additional payment method types Many of them are already RTBC :) Hope they're fine.
That final sentence brought me to the idea that commerce_stripe could "simply" list which payment methods are supported. When ever a new method is added, it could be added to the list or maybe it can even be done dynamically through
CommercePaymentMethodTypefiltered bystripe_*or sth. like that if not to dirty.But yes, let's get them done with priority! :)
Thank you!!
Comment #6
jonathanshawI have a concern that if we did do what is suggested in #5 then Stripe might always show all the available ones, rather than use its intelligent logic to show the best options. Would need careful testing.
Comment #7
anybody@jonathanshaw what I meant was just showing a list of what the module currently supports, so that the user can actually enable / disable the unsupported payment methods at stripe. Currently he can't know if he's not a developer?