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

Disputes: inaccurate dispute notification when the dispute is in inquiry state after Klarna "return" process #7885

Closed
dpaun1985 opened this issue Dec 12, 2023 · 15 comments
Assignees
Labels
category: core WC Payments core related issues, where it’s obvious. component: disputes Issues related to Disputes focus: disputes priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug.

Comments

@dpaun1985
Copy link
Contributor

Describe the bug

When a inquiry is created, the merchant receives a notification email that the disputed charge and the dispute fee will be deducted from their account.
Inquiries are similar to disputes, with three key distinctions: no funds are withdrawn unless the inquiry is elevated to a dispute, they remain refundable until disputed , and have a different set of statuses.

This was reported by a merchant that uses Klarna. In their Klarna app, when they return a product, they have a button ”I’ve made a return” that creates an inquiry. At this step, the merchant is not charged for the dispute, and they can refund the order.
However, the merchant receives the email notification that a dispute was created, and they will be charged with the dispute fee.

7401002-zd-a8c

p1702293773268309-slack-C7U3Y3VMY

@dpaun1985 dpaun1985 added the type: bug The issue is a confirmed bug. label Dec 12, 2023
@RadoslavGeorgiev RadoslavGeorgiev added component: disputes Issues related to Disputes category: core WC Payments core related issues, where it’s obvious. labels Dec 12, 2023
@RadoslavGeorgiev
Copy link
Contributor

This issue impacts Disputes, so assigning to Helix (based on team responsibilities Pc2DNy-3z-p2) @Automattic/helix.

Assigning as part of Gamma Triage process PcreKM-yM-p2.

@nicdwilson
Copy link

Just to clarify the following:

This was reported by a merchant that uses Klarna. In their Klarna app, when they return a product, they have a button ”I’ve made a return” that creates an inquiry. At this step, the merchant is not charged for the dispute, and they can refund the order.

This is not correct. It was reported by a merchant using Klarna, correct, but the return process is triggered by the customer within the Klarna payments app. The intention is that Klarna and the merchant are alerted to the return. This distinction is important to understand, because the merchant does not trigger the inquiry - the customer triggers the inquiry.

The merchant therefore has no control over the flood of non-dispute disputes. In 7401002-zd-a8c, the business model relies on returns and a smooth return flow.

@Jinksi
Copy link
Member

Jinksi commented Dec 19, 2023

If I'm understanding this correctly, we are misrepresenting a standard Klarna returns process as a dispute.

@souravdebnath1986 what are your thoughts on the priority of this issue?

@haszari haszari changed the title Disputes: Merchant receive a dispute notification when the dispute is in inquiry state Disputes: inaccurate dispute notification when the dispute is in inquiry state after Klarna "return" process Dec 20, 2023
@haszari haszari added the priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability label Dec 20, 2023
@haszari
Copy link
Contributor

haszari commented Dec 20, 2023

Marked as medium priority for now. Klarna is a subset of transactions, but if the dispute flow & notifications are incorrect, we will need to fix, as the issue will continue to affect Klarna merchants.

@haszari
Copy link
Contributor

haszari commented Dec 20, 2023

@souravdebnath1986 can you advise on priority? This might be high, depending on how incorrect our UI is for this scenario (Klarna returns). And how common the scenario is.

Also we'll need to clarify how to reproduce this and the exact pain point / inaccurate UI. @nicdwilson @dpaun1985 can you add steps for how to reproduce this, or screenshots of the relevant UI so the incorrect UI is clear?

@souravdebnath1986
Copy link

souravdebnath1986 commented Dec 20, 2023

Yes, this could be high. We probably have to revisit how Inquiries are represented in our UX. Inquiries are not a notification of a chargeback/dispute. They are a request for information for all card schemes inclusive of Klarna.

This is the difference between Klarna (closed loop scheme) and other card schemes -

For Klarna, inquiries are triggered when the customer reaches out to Klarna with a complaint. Klarna notifies the merchant. Merchant has to reach out to the customer on their own and attempt to resolve the inquiry. No defense submission to Klarna is required irrespective of whether the merchant agrees or doesn't with the complaint. If they don't agree to the inquiry, it will result in a formal dispute from Klarna at which point the merchant can submit defense documents. Process explained here

For other card schemes, if the merchant doesn't agree with the complaint, they should do a defense submission else it will result in a chargeback which can be unwinnable because of non-response to the inquiry. If they agree with the complaint, they should issue a full refund. Partial refunds can still result in a chargeback.

In the case above, the customer reached out to Klarna to request for return of an order. Klarna reached out to the merchant with an inquiry. The merchant has 21 days to resolve the inquiry with the customer which is upto the merchant i.e satisfy the customer by convincing them to not return or issue a refund etc. Klarna at the end of 21 days will check with the customer if they are satisfied, if so close the inquiry and if not close the inquiry > raise a formal dispute.

@souravdebnath1986 souravdebnath1986 added priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. and removed priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability labels Dec 20, 2023
@haszari
Copy link
Contributor

haszari commented Jan 8, 2024

To move this forward we need to reproduce the scenario. If we can't reproduce in test mode, we could also try a production store (if practical) or reach out to Stripe to get detailed info about how Klarna returns are represented on Stripe platform.

@haszari
Copy link
Contributor

haszari commented Feb 8, 2024

See also similar issue for SEPA disputes, which has more reports (tickets) linked: #3909

@zoupkat
Copy link

zoupkat commented Feb 10, 2024

Another 2:

  • 7693856-zen
  • 7698973-zen

@brucealdridge brucealdridge self-assigned this Mar 4, 2024
@brucealdridge
Copy link
Contributor

Reproduction

I've spent some time trying to reproduce this issue. Klarna has a bunch of test accounts to simulate disputes and returns (which it sounds like is the case here.
I was unable to a disputed order status on my test store. @csmcneill was able to get orders into disputed status on a production account in test mode.

Using the [email protected] test account, the order was initially an Inquiry which immediately turned into a dispute.
image

In the original case reported, it was only an Inquiry.
image

So this problem that merchants are having is not yet reproducible.

@brucealdridge
Copy link
Contributor

I've created a server issue to update the email copy for inquires which should help resolve this issue.

@grig-23
Copy link

grig-23 commented Mar 9, 2024

7854828-zen

The merchant is quite frustrated since they are not able to process refunds and they have 2k+ of pending disputes.

Earlier messages here indicate that refunds should in fact be possible as this isn't an actual dispute.

The merchant mentioned this:

The customer only pressed the "start a review" button on Klarna app

Although earlier they indicated a different button:

”I’ve made a return,”

Is there a process of refunding these orders that are falsely indicated as disputed or should the merchant follow a standard refund process? Should they still reach out to the customer?

Edit: the merchant mentioned that only full refunds are possible but not partial refunds:

Thanks, i can only issue a full refund. But for example if a customer starts a return but only returns partly i cannot refund only one product.

Is there a workaround for a partial refund?

@brucealdridge
Copy link
Contributor

@grig-23

We cannot currently test the returns flow, this is a limitation of test accounts. I have managed to test a return on a live account in test mode using test credentials. However the return showed up as a full dispute rather than an inquiry that they should.

Is there a process of refunding these orders that are falsely indicated as disputed or should the merchant follow a standard refund process? Should they still reach out to the customer?
Edit: the merchant mentioned that only full refunds are possible but not partial refunds:

Both full and partial refunds should be available when a merchant has an inquiry. Here is how this works.

Screen.Recording.2024-03-11.at.3.12.09.PM.mov

@brucealdridge
Copy link
Contributor

When a inquiry is created, the merchant receives a notification email that the disputed charge and the dispute fee will be deducted from their account.

The original issue mentioned here is now solved. There are now separate notification emails for inquiries.

If there are other issues with disputes and klarna please open a new issue.

@sverleis
Copy link

sverleis commented Apr 9, 2024

8014625-zd-a8c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: core WC Payments core related issues, where it’s obvious. component: disputes Issues related to Disputes focus: disputes priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug.
Projects
None yet
Development

No branches or pull requests

10 participants