Lets set "Worldwide" to USD and credit card in the developer hub. That will mean that any region not explicitly overridden with currencies or carrier billing will fall back to USD.
I think there's an added complexity in that there's two region checks going on. First that zamboni and fireplace have a set list of regions and secondly that there is a list of regions with prices. Based on that I thought it should work like this if the following was set: https://www.dropbox.com/s/9oy2jtdou6ln9vr/Screenshot%202015-01-09%2014.35.42.png?dl=0 If I'm coming from Canada: * there is no region for Canada in zamboni, so set as rest of world * there is no price tier for Canada, the developer has not specifically excluded Canada because zamboni doesn't know about it (see bug 1058257). * show rest of world price If I'm coming from Poland: * there is a region for Poland in zamboni, so set as Poland * there is a price tier for Poland * show price for Poland If I'm coming from Columbia: * there is a region for Columbia in zamboni, so set as Columbia * there is a price tier for Columbia, but the developer turned it off * app is not available If I'm coming from Brazil: * there is a region for Brazil in zamboni, so set as Brazil * there is no price tier for Brazil, the developer has not explicitly excluded Brazil * show rest of world price
Stuart, I've got a pull request that's a WIP: https://github.com/mozilla/zamboni/pull/2834 But mostly looking for feedback on comment 1, does that sound about right?
Talked on vidyo about the various aspects of this. We talked over one specific case here which isn't currently there. If I'm coming from a region that falls under the rest-of-world banner. * Worldwide is not enabled. * app is not available
https://github.com/mozilla/zamboni/pull/2834 Hopefully the comments in comment 1 and comment 3 make sense. Turning on the price tiers for -dev, we'll check that's ok before turning on for stage.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Worldwide turned on in -dev: https://metaplace.paas.allizom.org/tiers/?server=dev&provider=reference®ion=
This is on stage and now in Canada I can get to the Bango screen and the app is priced correctly.
(In reply to Andy McKay [:andym] from comment #8) > This is on stage and now in Canada I can get to the Bango screen and the app > is priced correctly. App in Canada purchased. Think this is good to go out next week.
Verified in FF38(Win7) in mp stage. For rest of the world and for regions with no price tier the shown currency on the price button is $. For a country with existing price tier i.e. Poland, South Africa the correct currency is displayed on price button but on the payment confirmation page the currency is displayed in Euros. Is this intended? Screenshot: http://screencast.com/t/Xh52bXZPxbhA Also I haven't fully understood the Canada use case. If there is no region set for Canada how can I simulate a payment from Canada?
Canada was an example of a country that is not recognised within the Marketplace, so is set by the Marketplace as "Rest of World". Going to :debug and setting your region to "Rest of World" will have the same effect.
You need to log in before you can comment on or make changes to this bug.