Confirmed users
324
edits
WebAPI/Direct Billing: Difference between revisions
→Access Control
| Line 18: | Line 18: | ||
Because there are too many sensitive APIs in here, only trusted web content can access this API. Access will be whitelisted by domain. No other web content will have access to this API. | Because there are too many sensitive APIs in here, only trusted web content can access this API. Access will be whitelisted by domain. No other web content will have access to this API. | ||
When thinking of a way to allow open access to these APIs, these are some problems we ran into: | |||
* Arbitrary web content cannot a send silent SMS because it could charge users money | |||
* If we whitelist short codes (which are free of charge) per operator/region then there is potential for abuse: web content could maliciously hit a short code which would cost the payment provider money | |||
* mcc/mnc expose the user's location and network which is a privacy concern | |||
* iccIDs can be used for fingerprinting | |||
* It may not be possible to prompt the user to grant access in a meaningful way | |||
* Standard app permissions do not apply because payments is a service offered to the users *of* apps. The app itself is not the one that needs permission. | |||
== API == | == API == | ||