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] BO Order refunds broken #12843

Open
filipefurtad0 opened this issue Sep 4, 2024 · 3 comments
Open

[Stripe] BO Order refunds broken #12843

filipefurtad0 opened this issue Sep 4, 2024 · 3 comments
Assignees
Labels
bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround.

Comments

@filipefurtad0
Copy link
Contributor

Description

Can't refund an order paid with Stripe.

There is still some circumstances to be cleared, as there are cases in which refunding works. However this has been reported in production and reproduced in staging. Bugsnag here:

Staging-AU:
https://app.bugsnag.com/yaycode/openfoodnetwork-aus/errors/65634115ca43a90008dd181c?event_id=66d88bed00f873b34b940000&i=sk&m=nw

Staging-FR:
https://app.bugsnag.com/open-food-france/coopcircuits/errors/66d88481265ea77fdaae1585?event_id=66d8848100f88e9bf1790000&i=sk&m=nw

Expected Behavior

On the Payment section of the order, clicking the Void button should display a success message. The payment state should change to balance due.

Actual Behaviour

On the Payment section of the order, clicking the Void button displays the message "Can't update payment"; clicking a second time indicates that the payment has already been refunded. The payment states remain unchanged.

Steps to Reproduce

  1. Create an order paid with Stripe.
  2. On the BO, edit the order and visit the Payments section.
  3. Click on "Void", next to Stripe payment entry.
  4. See the first error message (pic 1)
  5. Click a second time. See the second error message (pic 2).

Animated Gif/Screenshot

Pic 1

image

Pic 2
image

Workaround

No workaround.

Severity

S2? or S1? I looked on bugsnag and could not find evidence that this is occurring frequently. In fact, I found this to be affecting only ine user on CA - which of course, does not mean that it cannot affect others:

image

Your Environment

  • Version used: v4.6.2
  • Browser name and version: Firefox
  • Operating System and version (desktop or mobile): Ubuntu 22.04

Possible Fix

@filipefurtad0 filipefurtad0 added the bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround. label Sep 4, 2024
@RachL
Copy link
Contributor

RachL commented Sep 4, 2024

here is an order that reproduces the problem on staging FR: https://staging.coopcircuits.fr/admin/orders/R568554400/payments

Def not s1 as it's not a lot of occurrences, but I think we should not let this as s3 and investigate

@rioug rioug self-assigned this Sep 23, 2024
@rioug
Copy link
Collaborator

rioug commented Sep 23, 2024

I couldn't reproduce the error, see my order on staging AU : https://staging.openfoodnetwork.org.au/admin/orders/R203268788/payments

@RachL unfortunately staging FR has been refresh so I can' t look at your order. Any chance you could try to reproduce the bug again ?

@RachL
Copy link
Contributor

RachL commented Sep 25, 2024

@rioug I haven't managed to reproduce on staging FR yet but this order on staging AU does reproduce it: https://staging.openfoodnetwork.org.au/admin/orders/R313654502/edit

Otherwise if it easy to fetch production data locally, order R082352013 is reproducing the problem in CA prod

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround.
Projects
Status: In Progress ⚙
Development

No branches or pull requests

3 participants