908855 - [tracker] developer onboarding for new / 2nd operator biller in marketplace payments

Status: RESOLVED INVALID

(Marketplace Graveyard :: Payments/Refunds, defect)

Description

[Caitlin Galimidi [:c8o]]

Attachment: 2ndProcessor_Devs.JPG

Developer onboarding API from provider
- "mozexporter.api"
- developer sign up
- tie back to marketplace
- validation of bank details (Legit account / right acct #)
Price point selection
Product Sku to new processor
Set content ratings
Developer chooses provider
Sign terms of agreement annually 
- what happens when TOS currently expires? Do app sales get shut down or settlements
Inform current devs of new opportunity / pay provider in latam regions

Comment 1

[Bram Pitoyo [:bram]]

A couple of remarks:
* An operator may not validate. Should we mandate validation or make it optional?
* Would adding a second biller modify existing price points? To my understanding, it would only add a country.
* In the same vein, would a second biller have different content rating standard that would modify existing rating? It makes sense that rating is handled by each country’s content rating body [1]
* Is it possible for one country to be handled by multiple billers (Bango, AMX, etc.)? We know that multiple carriers-acting-as-billers is possible

Two things that we might want to consider:
1. Instituting our own rating system like Apple or Google [2][3]
2. Getting every carrier and biller partner to agree on the same price tier level

Doing both #1 & #2 will greatly simplify the hoops that developers will have to go through to get their app listed.

As a reminder, our research had uncovered that most developers are chiefly concerned in getting their app listed in as many countries/operators, buyable using as many payment methods, and displayed to as many potential Marketplace users as possible. The shorter and simpler this process is, the more successful app submissions we’ll get at the end of the day. To do this, we’ll need to get partners to agree on the same terms regarding price levels, payment methods, country availability and content ratings – all factors intertwined.


Sources
1. http://en.wikipedia.org/wiki/Video_game_content_rating_system#Comparison
2. http://en.wikipedia.org/wiki/Mobile_software_content_rating_system
3. https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/8_AddingNewApps/AddingNewApps.html#//apple_ref/doc/uid/TP40011225-CH13-SW47
https://support.google.com/googleplay/answer/1075738

Comment 2

[Bram Pitoyo [:bram]]

Attachment: DevHub - multiple payment processors and accounts - 01

This mockup visualizes our current UI that’s been tweaked to accommodate multiple payment processors and the creation of multiple accounts with different processors.

Let’s take it from the top:

1. Under the “your accounts” section is a list of seller’s account. Every account is given a shorthand name and is editable when the processor allows it. Every payment processor is distinguished with an icon, because it’s very likely that sellers will want to sign up with many payment processors using the same bank account.

2. Under the “add new payment accounts” section are several icons that, when clicked, will display the payment processor’s sign-up form. Every sign-up form may be different from each other. To the right of each icon is a list of country that each payment processor governs. Countries can overlap.

3. Lastly, on the very bottom of the page, you’ll see that Colombia and Poland cannot be enabled, because it “Requires an Amazon Payments account”. Since the seller hasn’t signed up with Amazon Payments, the countries that Amazon covers cannot be enabled.

Comment 3

[Andy McKay]

This is being tracked under bug 963203.