Confirmed users
2,959
edits
B2G/QA/WebAPI Test Plan/WebPayment: Difference between revisions
Jump to navigation
Jump to search
B2G/QA/WebAPI Test Plan/WebPayment (view source)
Revision as of 00:51, 2 September 2012
, 2 September 2012→Open Questions
| Line 74: | Line 74: | ||
* 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 come postback and chargeback URLs are specified in the JWT request and Mozilla Marketplace? What's the difference? | * How come postback and chargeback URLs are specified in the JWT request and Mozilla Marketplace? What's the difference? Is the one on marketplace the default callback URLs if a callback URL isn't specified? | ||
* 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? | ||