Confirmed users
2,959
edits
B2G/QA/WebAPI Test Plan/WebPayment: Difference between revisions
B2G/QA/WebAPI Test Plan/WebPayment (view source)
Revision as of 01:03, 2 September 2012
, 2 September 2012→Open Questions
| Line 77: | Line 77: | ||
* Does the trustworthy UI provide any context of where the HTML 5 content served inside the UI is from? In other words, how do I know the content I've received is safe or not? Is the URL of the content shown in the trustworthy UI to mitigate this? | * Does the trustworthy UI provide any context of where the HTML 5 content served inside the UI is from? In other words, how do I know the content I've received is safe or not? Is the URL of the content shown in the trustworthy UI to mitigate this? | ||
* How exactly does the identity pieces affect the in-app payments flow? I've noticed it's stated it's the responsibility of the "payment provider" - from the context of mozPay, is that a black box then? | * How exactly does the identity pieces affect the in-app payments flow? I've noticed it's stated it's the responsibility of the "payment provider" - from the context of mozPay, is that a black box then? | ||
* What's the purpose of productdata? How does it affect the in-app purchase? | * What's the purpose of productdata? How does it affect the in-app purchase? | ||
* How exactly does the application server send the 200 OK with the order ID back to the payment provider? | * How exactly does the application server send the 200 OK with the order ID back to the payment provider? | ||