Closed
Bug 1050718
Opened 11 years ago
Closed 10 years ago
App purchase fails with "UNSUPPORTED_PAY" error
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P1)
Tracking
(Not tracked)
RESOLVED
WONTFIX
2014-08-12
People
(Reporter: julian.mozbugs, Assigned: keir)
Details
Attachments
(3 files)
Steps to reproduce:
1. Load Marketplace-stage on your Android device https://marketplace.allizom.org/
2. Search for a paid app.
3. Start the payment flow.
4. Sign in with a valid account.
5. Enter your PIN and continue.
Expected results:
The user is redirected to the buy page and is able to purchase the app.
Actual results:
"UNSUPPORTED_PAY" error is displayed.
Notes/Issues:
Verified on FF34 (Android 4.2.1). I have the Dev Marketplace add-on installed https://addons.mozilla.org/en-US/firefox/addon/dev-marketplace/.
Movistar/Spain/Roaming
Connectivity: wifi enabled
I have attached logs for this issue.
Reporter | ||
Updated•11 years ago
|
Target Milestone: --- → 2014-08-12
Reporter | ||
Updated•11 years ago
|
Severity: normal → critical
Comment 1•11 years ago
|
||
Is this different from bug 1023535. What app are you purchasing?
This is a Bango error and we can't tell what the cause is.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → keir
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 2•11 years ago
|
||
Logs attached do not list a Bango error. Can you repost logs?
Flags: needinfo?(iulian.timis)
Assignee | ||
Updated•11 years ago
|
Severity: critical → blocker
Reporter | ||
Comment 3•11 years ago
|
||
I have attached the logs. The e-mail that I used to make the payment is m+5@mozilla.org
Flags: needinfo?(iulian.timis)
Updated•11 years ago
|
Flags: needinfo?(keir)
Comment 4•11 years ago
|
||
This app does not have a USD price tier.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Flags: needinfo?(keir)
Resolution: --- → INVALID
Reporter | ||
Comment 5•10 years ago
|
||
I have tried to purchase multiple apps but I got the same UNSUPPORTED_PAY error.
Movistar SIM/Spain Region
Connectivity: WiFi enabled
The apps have the price in EUR.
I have attached ADB logs.
Assignee: keir → iulian.timis
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Reporter | ||
Comment 6•10 years ago
|
||
I have reproduced this issue on FF OS 1.4 (Inari), MP-stage app.
Assignee: iulian.timis → nobody
Comment 7•10 years ago
|
||
Which apps?
Reporter | ||
Comment 8•10 years ago
|
||
All the apps that begin with the name "Test App"
Comment 9•10 years ago
|
||
From what I can tell all these apps have USD prices which should have been sent to Bango. Keir?
Assignee: nobody → keir
Flags: needinfo?(keir)
Priority: -- → P1
Comment 10•10 years ago
|
||
I am hitting this issue on FFOS 1.1, Inari device, Latest Stage app installed. We also tried with a newly created app , with the same results("Test App(newpaid)")
Assignee | ||
Comment 11•10 years ago
|
||
Price List - 1 of 5
Currency EUR
Price 0.10
Price List - 2 of 5
Currency MXN
Price 1.50
Price List - 3 of 5
Currency PLN
Price 0.49
Price List - 4 of 5
Currency HUF
Price 25.00
Price List - 5 of 5
Currency BDT
Price 5.00
The prices list - note EUR price is 0,10, min supported is 0,89
Flags: needinfo?(keir)
Assignee | ||
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → INVALID
Comment 12•10 years ago
|
||
We tried with 0.89 euro apps when reproduced this bug. Also , I think that 0.10 Euro is available for purchase using Spain Movistar SIM.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 13•10 years ago
|
||
Is the issue here that the app is being bought at a price where only carrier billing is being supported?
* In this case the header enrichment is failing, due to being roaming.
* Bango tries to show a credit card page, but fail because the price is not available at credit card, only carrier billing.
* Bango returns the unsupported pay error.
Would a solution be?
* Bango tries to show a credit card page, realises that won't work and falls back to the carrier billing flow and shows the MT Auth flow?
Assignee | ||
Comment 14•10 years ago
|
||
(In reply to Andy McKay [:andym] from comment #13)
> Is the issue here that the app is being bought at a price where only carrier
> billing is being supported?
The app prices are tiered and the expected behaviour is that all tiers should be supported regardless of payment method. The 0,10EUR price point isn't a 'supported' tier (it just happens to work for this carrier).
(In reply to Victor Carciu from comment #12)
> We tried with 0.89 euro apps when reproduced this bug.
Can you supply logs of failing transaction where the app price is 0,89EUR?
Comment 15•10 years ago
|
||
Logs for 0.89EUR : https://pastebin.mozilla.org/6386437
Assignee | ||
Comment 16•10 years ago
|
||
(In reply to Victor Carciu from comment #15)
> Logs for 0.89EUR : https://pastebin.mozilla.org/6386437
Credit card is not supported in ROM - there is an ongoing project to enable credit card globally.
Reporter | ||
Comment 17•10 years ago
|
||
I have tried to purchase an app on my Android device using the Movistar SIM and got the same "UNSUPPORTED_PAY" for an app that costs 0.89 EUR. The smaller price that this issue is not reproducing for, is 1.89 EUR, I was able to purchase an app with that price.
Assignee | ||
Comment 18•10 years ago
|
||
Not sure how to block this for you. It seems many of these errors are caused by incorrect config on stage, or issues on a specific user (like too many credit card declines) and NOT_SUPPORTED is the expected behavior.
Can I suggest that we close this bug and open new bugs with logs for specific instances where you thing the observed behavior is wrong?
Assignee | ||
Comment 19•10 years ago
|
||
Closing this as agreed. Please open new tickets for specific issues with logs.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → INVALID
Comment 20•10 years ago
|
||
Even though we agreed to break this bug into more specific bugs, all the issues reported here are still valid. Moving this to wontfix.
Resolution: INVALID → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•