Closed Bug 883936 Opened 12 years ago Closed 12 years ago

fall back to credit card automatically for Seville

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kumar, Assigned: keir)

Details

Certain price points in Seville do not support carrier billing. Instead of Mozilla using a type filter for this (which is not possible for launch, see bug 882321) Bango will automatically disallow carrier billing and offer a credit card payment. As mentioned on today's call, this can be done at Bango by disabling the configured carrier billing prices for Seville. This is only a temporary change. We need to make type filtering more flexible as stated in bug 882321 For prices that should not support carrier billing, see http://metaplace.paas.allizom.org/tiers/dev/
Assignee: nobody → keir
Priority: -- → P1
the price point you pass us does not meet any price point we have stored so CC should always be shown as a fail-over. Please retest and confirm.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Karina, Can you retest
Flags: needinfo?(karina.filipe)
Steve, I'm testing this feature at exact this moment and so far no pass. I've just restarted the device and checked again. The same message is seen to try again later.
Flags: needinfo?(karina.filipe)
Thanks Karina. Can you provide the exact price points that are not passing? You can reference them all here: http://metaplace.paas.allizom.org/tiers/prod/
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hi Kumar, here are the price points not working (any price point that is supported by CC here in Seville are failing): Tier 20 Tier 30 Tier 40 Tier 50 Tier 60 Tier 70 Tier 80 Tier 90 Tier 100 Tier 120
Based on a IRC conversation with Karina and Kumar, the behaviour described in this bug is how Bango is working already: for price tiers with no carrier billing, credit card is the only payment method offered. The failure Karina was talking about is on bug 884466
great, it sounds like the fallback is working as intended
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.