Closed (fixed)
Project:
Commerce Stripe
Version:
8.x-1.x-dev
Component:
Payment Element
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
29 Sep 2023 at 07:33 UTC
Updated:
17 Oct 2023 at 06:04 UTC
Jump to comment: Most recent
Comments
Comment #2
jsacksick commentedNo, you shouldn't do that.
Comment #3
jsacksick commentedTake a look at this: https://stripe.com/docs/payments/payment-intents/migration/charges
This is the reason why the current gateway uses the payment intent ID as the remote ID.
Comment #4
vmarchukAs discussed with @jsacksick, the above code has been added to support legacy payments (with stored charge ID) and to support new payments that use PaymentIntent ID as the remote ID.
The old issue is here https://www.drupal.org/project/commerce_stripe/issues/3185801.
So after implementing https://www.drupal.org/project/commerce_stripe/issues/3390551 we only need to use code with PaymentIntent ID.
Comment #7
vmarchukCommitted!