795143 - post-process Bango payment

Status: RESOLVED FIXED

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

Description

[Kumar McMillan [:kumar]]

after receiving a successful Bango payment via URL redirect, do the following
- verify the Bango request (using their token API, details TBD)
- notify the app that initiated the payment (this is similar to how in-app payments used to work, code is re-usable)

Comment 1

[Kumar McMillan [:kumar]]

I split out the notifications into bug 798059

Comment 2

[Gregory Szorc [:gps]]

Per initial comment, action on this bug requires details of the Bango token API. Requesting more info from Kumar, who presumably knows where to get the details from.

Given comment #1, I /think/ this bug can also be changed to "verify Bango payment request."

Comment 3

[Kumar McMillan [:kumar]]

Hi Gregory. The Relay API explains how to verify tokens http://bango.custhelp.com/app/answers/detail/a_id/1500/

This may not be the exact way to do it though. We are waiting on Bango for details; it looks like we will generate a different token with the Billing API then they will use that to verify that Mozilla initiated the relay.

Comment 4

[Kumar McMillan [:kumar]]

(In reply to Kumar McMillan [:kumar] from comment #3)
> Hi Gregory. The Relay API explains how to verify tokens
> http://bango.custhelp.com/app/answers/detail/a_id/1500/

For more context, this is not the exact API we will use to do our relay. Bango has mentioned that we will have a way to generate a server side token to initiate our custom relay flow more securely. We still don't know which API we will use for generating that token though.

Comment 5

[Jason Smith [:jsmith]]

Not on-device - removing nom.

Comment 6

[Kumar McMillan [:kumar]]

Keir says this is ready to go.

Sample GET redirect that we need to process on our server:
 
http://moz/pay/?success=true&ResponseCode=OK&ResponseMessage=Success&BangoUserId=XXXXX&MerchantTransactionId=MozExternalTransId&BangoTransactionId=0&TransactionMethods=GBR_VODAFONE,Vodafone,MPAY_VFUK,&BillingConfigurationId=1570&MozSignature=XXXXXX&P=test%3D1%26test%3D2

These are custom fields we can pass via the Billing Config api:

REQUEST_SIGNATURE
APP_LOGO_IMG_URL
REDIRECT_URL_ONSUCCESS
REDIRECT_URL_ONERROR

Comment 7

[Kumar McMillan [:kumar]]

The Solitude endpoint has landed for this https://github.com/mozilla/solitude/commit/218868c1e9ce8f5bb761a7274b2370b1b3832421

Comment 8

[Kumar McMillan [:kumar]]

webpay side landed: https://github.com/mozilla/webpay/commit/04551b2b4b1961d4129aba5854b89fabf9fc7220

This allows a secure app purchase and install!