This invention relates to a method of accounting for Internet transactions via mobile wireless. Methods of accounting for Internet transactions via an Internet terminal (e.g., a personal computer) are known from the related art. Methods known previously for use on the Internet involve keeping or loading customer data in the Internet terminal or at the dealer's server. However, this is not feasible when using mobile wireless terminals as Internet terminals.
This invention is based on the following object (problem): Providing a method with which it is possible to rapidly and reliably bill for Internet transactions via mobile wireless.
This object is achieved for the features characterized in the independent patent claims.
By means of WAP (wireless application protocol) it is possible to select goods (information, tickets, CDs, hotel rooms, etc.) over the Internet by using a mobile wireless terminal and optionally reserve them. If the customer actually wants to purchase the goods, he can make a payment transaction from the mobile wireless device.
Methods known previously on the Internet have involved keeping or loading customer data in the terminal or at the dealer's server. The WAP terminal does not have enough capability for the first method, and for the second method, customer data must be entered again for each dealer. This is not feasible with a WAP terminal keyboard.
Sensitive data remains in a secured GSM network with the method according to this invention and is not transmitted over the Internet. Therefore, no additional encryption methods are necessary. In the GSM network, the customer is known from his or her MSISDN (Mobile Subscriber Integrated Services Digital Network) number. Therefore, no additional authentication method is necessary, and at the same time, it is possible to preserve the anonymity of the customer with respect to the provider or seller.
Four parties are involved in performing the payment transaction: customer, dealer, payment gateway and bank network.
The customer (WAP user) has a WAP-capable mobile wireless terminal 1 and has an access to the Internet 9 via the mobile wireless network 11.
The dealer has his standard Internet shop software in a provider server 2, expanded by a WML interface (wireless markup language interface) which allows the shop web pages to be displayed on the WAP-capable mobile wireless terminal 1. Payment gateway 3 holds customer data such as credit card information, debit information, minipayment and address information with respect to the customer's MSISDN in a payment database 4. The payment gateway 3 can determine by query to MSISDN-IP database 5 the MSISDN belonging to a temporary IP address. It also has access to various reference databases 6 for checking the customer data. The payment gateway 3 can forward credit card information and debit transactions to a bank network 7. Minipayment transactions are handled via a minipayment account with a mobile wireless operator-specific minipayment bank 8.
The minipayment account is carried as a subaccount of an actual bank account at a bank. Payment gateway 3 and minipayment account 8 are constantly being synchronized through database balancing. The minipayment account 8 may be paid in advance (prepaid) or it may be regulated by debiting (postpaid). The customer can access the current account status via the Internet 9 at any time and can access ongoing postings to the minipayment account 8. Deductions from minipayment account 8 to dealers' accounts with various banks 10 take place collectively over a period of time (e.g., by day, by week or by month).
Description of Process on the Basis of
The WAP user selects the WML shop page of a dealer's server 2 via his mobile telephone 1. The dealer's WML shop page appears on the display of the mobile telephone 1. The customer selects from available goods, which he would like to purchase, and places them in a virtual shopping cart at the dealer's server. Ultimately, the customer can see all the goods he has collected in his shopping cart. This selection procedure may lead, for example, to a certain music CD, a hotel room, theater tickets to a certain movie, etc. The dealer sees only an IP address issued temporarily to the mobile wireless subscriber, i.e., the customer is anonymous to the dealer. However, the dealer may determine the GSM network operator from the IP address range.
On the shopping cart WML page, the WAP user may review his entries so far and click on “pay.” Then the dealer's server 2 transmits the transaction data (product information, purchase price, total purchase sum, a transaction ID (TA ID), his dealer ID, the payment options he supports and an IP link to the payment gateway) to mobile telephone 2 of the WAP user. At the same time, he also transmits this information directly to payment gateway 3. In doing so, he adds as customer identification the temporary IP address of the customer. The product information may be omitted here.
The WAP user reviews the information in the shopping cart and starts the payment procedure by selecting one of the available payment options. He may also terminate the payment process at this point. If he selects a payment option, the transaction data sent from the dealer (optionally without product information) is sent to payment gateway 3. In the case of larger amounts, input of a payment PIN, which is stored in payment gateway 3, may be required.
Payment gateway 3 synchronizes the two messages and checks them for whether they match. The user IP address, TA ID, amount and dealer ID must be identical. Via the user IP address, the payment gateway 3 determines the MSISDN of the WAP user and searches its customer data with it. It determines whether the data has been stored correctly for the selected payment option. Reference databases 6 are queried. If the result of this check is positive, the dealer and the WAP user each receive a payment confirmation. Payment gateway 3 makes a deduction from the minipayment account 8 online. Credit cards and debit entries are relayed later to the bank network 7 or a system with a connection to the bank network for execution. The payment gateway 3 writes an electronic invoice for the dealer for each transaction conducted. These are collected and sent to a accounting system for further processing.
If a shipping address was requested by the dealer in the transaction data, the WAP user may forward the data stored in payment gateway 3 or may give an address specifically for this payment process. This is then transmitted to the payment gateway together with the transaction data. The payment gateway forwards the special or preconfigured shipping address together with the payment confirmation to the dealer. If no shipping address is necessary, as in the case of movie tickets, for example, the customer remains completely anonymous to the dealer.
Agreeing on payment options such as credit card or debit method may be simplified by the fact that the dealer must always support at least these two methods and the WAP user at least one of them. If more options are possible, it may be advisable for the dealer to inquire about the payment options at the payment gateway before sending the transaction data to the WAP user and only then would the dealer preset the payment options to be supported by the dealer in the transaction data.
The customer administers his own customer data in the payment database 4, e.g., via Internet access from a PC, via the WAP terminal or by written order.
The customer sets up his minipayment account 8 at the minipayment bank of the mobile wireless operator. This account is usually prepaid, unless the customer meets the credit requirements of the mobile wireless operator. The customer may make credit postings to his minipayment account at any time via the Internet and may also monitor the postings.
In cases where security requirements are lower, it is possible to simplify the method by making the authorization query to the payment gateway 3 asymmetrical, i.e., only the customer sends a message to the payment gateway or only the dealer sends a message to the payment gateway to initiate the payment transactions. No synchronization is necessary in these cases.
Number | Date | Country | Kind |
---|---|---|---|
199 46 539 | Sep 1999 | DE | national |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/DE00/03420 | 9/28/2000 | WO | 00 | 7/31/2000 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO01/25979 | 4/12/2001 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5710887 | Chelliah et al. | Jan 1998 | A |
6067529 | Ray et al. | May 2000 | A |
6178331 | Holmes et al. | Jan 2001 | B1 |
6223215 | Hunt et al. | Apr 2001 | B1 |
6366893 | Hannula et al. | Apr 2002 | B2 |
6415156 | Stadelmann | Jul 2002 | B1 |
7089208 | Levchin et al. | Aug 2006 | B1 |
20020065736 | Willner et al. | May 2002 | A1 |
Number | Date | Country |
---|---|---|
199 05 054 | Aug 2000 | DE |
100 22 973 | Feb 2001 | DE |
199 38 201 | Feb 2001 | DE |
0 848 361 | Jun 1998 | EP |
0 917 327 | May 1999 | EP |
0 917 327 | May 1999 | EP |
1 107 196 | Jun 2001 | EP |
WO 9613814 | May 1996 | WO |
WO 9741539 | Nov 1997 | WO |
WO 9745814 | Dec 1997 | WO |
WO 9811519 | Mar 1998 | WO |
WO 9847116 | Oct 1998 | WO |
WO 9931610 | Jun 1999 | WO |
WO 9933034 | Jul 1999 | WO |
WO 9945684 | Sep 1999 | WO |
WO 9948312 | Sep 1999 | WO |