Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Stripe SCA] Backoffice orders: Can't capture second stripe payment #9214

Closed
drummer83 opened this issue May 24, 2022 · 1 comment
Closed
Labels
bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround.

Comments

@drummer83
Copy link
Contributor

Description

As a consequence of #5574, orders with a stripe transaction fee end up with a balance due. However trying to pay this with a second stripe payment fails (for unknown reason to me). The failing payments do not even show up in Stripe's backend.
Also the payment cannot be deleted from the payments list (see flash message in the screen capture).

Note: Splitting a stripe payment into 2 or more pieces by adjusting the amount to be paid by the first payment, seems to work fine.

Expected Behavior

Additional backoffice payments with stripe should be possible at all times.

Actual Behaviour

The second payment to cover the balance due with stripe is failing.

Steps to Reproduce

As shop owner :

  1. Set up a stripe payment method with a payment fee.
  2. Create a backoffice order using that payment method - observe the 'balance due' as a consequence of [Admin][Order] "Balance due" state after payments with a transaction fee #5574.
  3. Try to capture a second stripe payment with the amount of the 'balance due' - observe the payment being listed as failed in the payments list.
  4. Try to void the failed payment - observe the flash message at the top of the screen.

Animated Gif/Screenshot

Peek 2022-05-24 13-28

Workaround

Use a cash payment method.

Severity

bug-s3: a feature is broken but there is a workaround

Your Environment

  • Version used: 100.0.2 (64-Bit)
  • Browser name and version: 4.1.31
  • Operating System and version (desktop or mobile): Desktop Ubuntu 20.04 LTS

Possible Fix

@drummer83 drummer83 added the bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround. label May 24, 2022
@drummer83
Copy link
Contributor Author

Hmmm, I just did this on v4.2.38 and it worked fine.
Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround.
Projects
None yet
Development

No branches or pull requests

1 participant