-
**Describe the bug**
Scenario:
- 2 customers, and only 1 item that they both have in their cart
- They start checking out at the same time
- I do a stock level check before creating the payment in…
-
### Describe the bug
confirmation_token is a parameter that can set when creating a payment intent but is not exposed as part of the createPaymentIntent struct
Stripe API documentation: https://do…
-
### Describe the solution you'd like
It would be awesome if you could update [this example](https://github.com/woocommerce/woocommerce/blob/trunk/plugins/woocommerce/src/StoreApi/docs/checkout.md#p…
-
**Is your feature request related to a problem? Please describe.**
We have an app for iOS & Android built using ionic & capacitor. Although after integration, the payment sheet works and I get option…
-
Hello
Thank you for your project! It is being used in my company and is very useful.
Apparently acccording to Stripe, the Charges API is old, and some countries are requiring the updated API bec…
-
### Problem
We must only attempt to create and confirm an intent for orders with a pending/failed status.
We could check that `$order->needs_payment()` before processing a payment for this.
T…
-
We have been discussing whether we should prepare the card reader for payment immediately after the user enters the checkout screen or if we should add a CTA instead. We decided to start with the fast…
-
**Describe the bug**
A user reported a case where the payment in Stripe went through after SCA authentication initially failed which marked the order as failed. Then, there's another note that says…
-
### Description
Previously, the server would confirm the PaymentIntent, allowing additional request parameters to be added through the EVENT_BEFORE_CONFIRM_PAYMENT_INTENT event. Our code injected the…
-
The `authorization failed` and `authorization expired` statuses, along with any SCA status can only be checked using the `payment_intent` object, which is not expandable when using the charge API. We …