Closed Bug 834410 Opened 10 years ago Closed 10 years ago

Support simulated success/error in JWT for developer testing of in-app payments

Categories

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

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED
2013-02-07

People

(Reporter: kumar, Assigned: kumar)

References

Details

(Whiteboard: p=3)

To enable developers to test their in-app payment implementation let's adjust webpay to support the following simulations.

This JWT will open a fake webpay flow with some sort of "Continue to simulate payment" button. That button click will send a real postback to the app server.

{
  ...
  "request" : {
    "name" : "Unlock Level 10",
    ...
    "simulate": {
      "result": "postback"
    },
  }
}

Likewise, this JWT will simulate an error:

{
  "request" : {
    ...
    "simulate": {
      "result": "chargeback",
      "reason": "Insufficient funds"
    },
  }
} 

Chargeback reasons can be left undefined for now.

For all simulations, we should display verbose errors so that developers can get as much information as possible. Before, we only showed errors if the server was configured with VERBOSE_LOGGING = True


See discussion: https://groups.google.com/d/msg/mozilla.dev.webapps/p2HeofBHGKY/yPVjhyRYojYJ
Priority: -- → P1
Assignee: nobody → kumar.mcmillan
Target Milestone: --- → 2013-01-31
Summary: Support simulated payment success/error in JWT for developer testing → Support simulated success/error in JWT for developer testing of in-app payments
Version: 1.0 → 1.1
Whiteboard: p=3
Blocks: 836983
Target Milestone: 2013-01-31 → 2013-02-07
The webpay side has landed https://github.com/mozilla/webpay/commit/9cd70aa11d45349db134cd40017956de679e33c9
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Blocks: 842703
Blocks: 836997
Blocks: 844299
You need to log in before you can comment on or make changes to this bug.