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

[IPP] Transactions below minimal amount error message missing #13110

Open
2 tasks
samiuelson opened this issue Dec 11, 2024 · 5 comments
Open
2 tasks

[IPP] Transactions below minimal amount error message missing #13110

samiuelson opened this issue Dec 11, 2024 · 5 comments
Assignees
Labels
feature: mobile payments Related to mobile payments / card present payments / Woo Payments. priority: medium Planned tasks usually belonging to ongoing projects

Comments

@samiuelson
Copy link
Collaborator

samiuelson commented Dec 11, 2024

Problem

  • In case of payment amount below minimal allowed amount (e.g. $0.20) payment fails but we don't get a dedicated error message. Instead we show generic "Sorry, this payment couldn't be processed"

Goal - investigate if this is a backend or app issue.

  • In case of payment amount below minimal allowed amount (e.g. $0.20) payment fails the first time. However, it succeeds during the second attempt.

Goal - investigate if this is correct

Context

The issue was discovered when testing failed payment state in POS: #13057 (comment)

@dangermattic
Copy link
Collaborator

dangermattic commented Dec 11, 2024

🚫 Please add a type label (e.g. type: enhancement) and a feature label (e.g. feature: stats) to this issue.

@samiuelson samiuelson added feature: mobile payments Related to mobile payments / card present payments / Woo Payments. priority: medium Planned tasks usually belonging to ongoing projects labels Dec 11, 2024
@kidinov kidinov self-assigned this Dec 26, 2024
@kidinov
Copy link
Contributor

kidinov commented Dec 26, 2024

So far, my findings:

  • For some reason, the error now comes from the "capture" state while we map our errors in the processing step. So we expect this error on the step before it comes actually
  • Currently the error comes from our backend (not the SDK), and it doesn't contain any proper way of determining the type of it. Only a message
{"error":"wcpay_capture_error","message":"Payment capture failed to complete with the following message: Minimum required amount was not reached."}
  • On iOS, it looks like the SDK returns properly typed errors, including this one. But I still don't understand why it works there

@kidinov
Copy link
Contributor

kidinov commented Dec 26, 2024

I tried to install 17.3-rc-1 from FEB 2024 - the same issue is there

The same on 15.7 and 12.4

But, on iOS, the error comes before the card is applied, so it looks like it's a processing step in their case

@kidinov
Copy link
Contributor

kidinov commented Dec 26, 2024

Ok, so on iOS it works just because they use hardcoded value on the client. So, the change probably comes from Stripe. I asked them

p1735228071598689-slack-C01G168NFC2

@kidinov
Copy link
Contributor

kidinov commented Jan 6, 2025

pdfdoF-67u-p2 results of the research

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: mobile payments Related to mobile payments / card present payments / Woo Payments. priority: medium Planned tasks usually belonging to ongoing projects
Projects
None yet
Development

No branches or pull requests

3 participants