986614 - Set user on contribution object for purchase of in app object after post-purchase postback

Status: RESOLVED FIXED

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

Description

[Jared Lockhart [:jlockhart]]

When we receive a postback from webpay to zamboni after a successful purchase of an in app object, we have to update the contribution object to include the user info that was received in webpay after the user authenticated.

https://github.com/mozilla/zamboni/blob/master/mkt/purchase/webpay.py#L123-L125

User can be determined from the postback JWT here:

https://developer.mozilla.org/en-US/Marketplace/Monetization/In-app_payments#Processing_chargebacks_on_the_server

Comment 1

[Jared Lockhart [:jlockhart]]

Allowing users for inapp purchases:

1) Create anonymous contribution at JWT creation in zamboni
    - Done

2) User logs in to persona in webpay during purchase
Webpay stores email address when user logs in
Ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1027275

3) Webpay passes email address to zamboni during post purchase postback
Ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1027279
maybe as response.webpayEmail in the postback JWT https://github.com/mozilla/webpay/blob/master/webpay/pay/tasks.py#L278

4) Zamboni sets user during postback
    - Lazily create UserProfile
        - Ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1027283
        - example: https://github.com/mozilla/zamboni/blob/master/mkt/users/views.py#L156
    - Set user foreign key on contribution
        - Ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=986614
        
        
        
Notes:
    - By pass the solitude buyer idea altogether