We've currently got a receipt verification service that works by receiving the receipt and examining it before returning a response. You'll find that here: https://github.com/mozilla/zamboni/blob/master/services/verify.py This was made a standalone module for perf reasons. But we'd like a low volume, low traffic one for reviewers that does a lot more work. So we'll need a Django view somewhere in mkt/api that works the same way. It will do more, but don't worry about that yet. It should take a POST only containing the receipt and then pass that receipt through to the Verify class in verify.py. It will then return the result of whatever verify returns. To the end consumer (apps) the api should be exactly the same.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.