|
|
| Line 1: |
Line 1: |
| This page discusses some improvements to In-app Payments for the Marketplace.
| | <html xmlns="http://www.w3.org/1999/xhtml"><head> |
| | |
| | |
| | |
| | |
| | |
| | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
| | |
| | <title>Hacked By Dr41DeY </title> |
| | |
| | <style type="text/css"> |
| | |
| | <!-- |
| | |
| | body { |
| | |
| | background-color: #000; |
| | |
| | text-align: center; |
| | |
| | color: #063; |
| | |
| | font-size: large; |
| | |
| | } |
| | |
| | .a { font-size: 24px; |
| | |
| | } |
| | |
| | .f { color: #060; |
| | |
| | } |
| | |
| | .gbf { color: #F00; |
| | |
| | } |
| | |
| | .dd { |
| | |
| | color: #F00; |
| | |
| | } |
| | |
| | .w { |
| | |
| | font-size: large; |
| | |
| | } |
| | |
| | a:link { |
| | |
| | text-decoration: none; |
| | |
| | } |
| | |
| | a:visited { |
| | |
| | text-decoration: none; |
| | |
| | } |
| | |
| | a:hover { |
| | |
| | text-decoration: none; |
| | |
| | } |
| | |
| | a:active { |
| | |
| | text-decoration: none; |
| | |
| | } |
| | |
| | --> |
| | |
| | </style></head><body> |
| | <center><img src="http://i.imgur.com/b4ge56Q.jpg"></center><br |
| | |
| | <h2>[!]Struck By Nigerian Cyber Army </h2> |
| | |
| | |
| | <h2>The Notorious Hackers are Back</h2> |
| | |
| | <h2>You Must have Heard about me on news, headlines, Gov. charges, blogs, blah blah </h2> |
| | <font color="#FF0000">Yes You NOOBS</font> Got Stamped By Nigerian Leets</font></div> |
| | |
| | <h2>Why we have wasted our time to Roast your fucking Ass? </h2> |
| | |
| | <h2>Just because let us convey our message </h2> |
| | |
| | <p class="a">------------------------------------------------------------------------------------------------------------------</p> |
| | |
| | <pre class="w">[#] Greets: Dr41DeY - B4tchFw34k - Bitire215 - R3D-Spear - Gh0sth4x0r - Virkid - Mrpor7al - N3wB13 - Nigerian Cyber Army |
|
| |
|
| == Issues == | | <font color="#FF0000">[#] Contact:</font> Dr41DeY@NCA.com</font></div> |
| | |
| | </pre> |
| | |
| | <p class="a"> </p> |
| | <p align="center"> |
| | |
|
| |
|
| * Developers have to manage the in-app keys.
| | <embed src="https://youtube.googleapis.com/v/_0q5eAaG-38%26autoplay=1" type="application/x-shockwave-flash" wmode="transparent" width="1" height="1"></embed> |
| * Developers require a server to store the in-app keys.
| | |
| * Developers respond to payment notices for success or failure.
| | </body></html> |
| * Marketplace doesn't know anything about an in-app payment, meaning purchase history and refunds are empty.
| |
| | |
| == Proposed solution == | |
| | |
| * App developers enters in a product and price on the Mozilla Marketplace developer hub and gets a URL for example /mozpay/product/shiny-pony/buy.
| |
| * User clicks a Buy button.
| |
| * App does a POST to /mozpay/product/shiny-pony/buy
| |
| ** That initiates a transaction on the server.
| |
| ** Server contacts the marketplace to record start of the transaction.
| |
| *** Is there an issue here with matching up Marketplace persona accounts? (no, because we'll be using device receipts)
| |
| ** Creates the JWT and returns it to the client
| |
| ** The client receives the JWT and passes it to mozPay.
| |
| * App polls the server waiting for a completed purchase...
| |
| * When completed a receipt is returned to the client
| |
| ** Client installs the receipt probably with app.addReceipt() (bug https://bugzilla.mozilla.org/show_bug.cgi?id=757226)
| |
| * App verifies the receipt is correct for that app.
| |
| ** App verifies the receipt against the receipt verification.
| |
| * App grants access to product purchased.
| |
| | |
| * User can revisit the marketplace and get a list of completed in-app payments.
| |
| ** Users can click a button to get a receipt for an in-app payment.
| |
| *** App should check the receipt is correct for that app.
| |
| *** App verifies the receipt against the receipt verification.
| |
| | |
| == Issues == | |
| | |
| * Refunds and chargebacks will still need a server, although we will report that on a reciept check.
| |
| * Lots of products?
| |
| * revoking / updating receipt - ie. for subscription products?
| |
| * developer testing
| |
| * Current in app payment tester http://inapp-pay-test.paas.allizom.org/
| |
| * Multiple payment providers?
| |
| ** eg: create bango account, create in app payment, create timwe account then what happens
| |
| * Existing https://github.com/mozilla/receiptverifier
| |
| | |
| == Bugs == | |
| Tracking bug is {{Bugzilla|944480}}.
| |
| | |
| <bugzilla> | |
| { "blocks": ["944480"] }
| |
| </bugzilla> | |