WAP billing
Lua error in package.lua at line 80: module 'strict' not found. WAP billing is a mechanism for consumers to buy content from WAP Wireless Application Protocol sites that is charged directly to their mobile phone bill. It is an alternative payment mechanism to debit or credit cards and premium SMS for billing.[1][2] Using WAP billing, consumers can buy mobile content without registering for a service or entering a username or password.[3] The user clicks on a link and agrees to make a purchase, after which they can download content.
WAP billing is particularly associated with downloading mobile entertainment content like ringtones, mobile games and wallpapers. Some commentators have suggested it could compete with Premium SMS as a leading payment channel for mobile content.[2][4][5]
Contents
How WAP billing works
WAP billing works with WAP-enabled mobile phones over a GPRS or 3G wireless connection.[6] The customer initiates a WAP session with the content service provider by browsing a WAP page, for example.[4] The WAP site hoster obtains the visitor’s MSISDN without the visitor having to register on a specific WAP gateway or service. This information is provided through integration with the operator's own MSISDN lookup service.
Consumers confirm a purchase by clicking on a ‘confirm purchase’ link on their mobile phone and the WAP billing platform informs the WAP application of the completed purchase transaction. Consumers are redirected to the content they have purchased.[7] The purchases are recorded and billed directly via the mobile phone bill using the MSISDN.[4]
Cross-operator WAP billing
Attempts have been made to create a single, cross -operator WAP billing platform that can support the purchase of products on any mobile network.[5][8][9]
In other markets, like Ireland, WAP Billing is available across O2 and Vodafone mobile operators, via MSIDSN forwarding. WAP billing is only available to mobile aggregators operating in the Irish market on a case by case, business model basis, unlike the UK market.
Benefits of WAP billing
The benefits cited for WAP Billing include the ability to sell to minors who lack a credit card or bank account[10] and an improved customer experience including ‘Single click’ purchases where[9][11] transactions are completed without consumers having to send or receive a text message[12] or remember shortcodes.[4] It has been claimed that WAP Billing also reduces the possibility of fraud when paying for mobile content.[4] Another benefit cited for WAP Billing is the assertion that users experience the same ‘browse and buy’ experience they are used to via their PC on the Internet.
Critic of WAP billing
WAP billing lacks of transparency to the customer. The act of sign a contract, handy out money to a human, reading, understanding and writing or at least typing something and so also indirectly proving that you are legitimate to buy is soften/reduce to a single touch. So even a baby or a dog or cat that occasionally dips on the screen may trigger a purchase. Often customer don't notice that they actually paid for something or bought a subscription.
To silently start billing with a single (misleaded) click is very inviting to for malicious apps or malicious embedded ads that may use clickjacking.
Once triggered it's hard to stop or cancel a payment. Normally there are three entities involved in the claim of the money:
- Your mobile provider,
- a payment gateway provider and finally
- the 3rd party provider that offers it's paid service.
So the service is indirectly paid through your mobile bill. That makes it more complicated to deny the payment to certain 3rd party provider or to claim your money back.
In 2013, the Federal Trade Commission settled with Jesta Digital LLC concerning unauthorized WAP billing charges.[13]
See also
References
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 4.0 4.1 4.2 4.3 4.4 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://www.ftc.gov/news-events/press-releases/2013/08/jesta-digital-settles-ftc-complaint-it-crammed-charges-consumers