WO2010125577A1

WO2010125577A1 - Cardless financial transaction

Info

Publication number: WO2010125577A1
Application number: PCT/IN2010/000265
Authority: WO
Inventors: Shrivastav Shourabh
Original assignee: Shrivastav Shourabh
Priority date: 2009-04-27
Filing date: 2010-04-27
Publication date: 2010-11-04
Also published as: WO2010125577A4

Abstract

An embodiment herein provides an authentication server (108) to authenticate in real time a cash withdrawal transaction from a bank account of a remitter (102) at an ATM (114) without using an electronic card. The remitter (102) is subscribed to an authentication service having a user subscription database (202) on the authentication server (108). A transaction code is generated at the authentication server (108) in real time triggered by a request received from the mobile communication device (104) associated with the remitter (102) and communicated to the remitter (102). The remitter (102) communicates the transaction code to the beneficiary (112), and the beneficiary (112) enters the transaction code at the ATM. The transaction is authenticated if a PIN entered by the remitter (102) to log on to a client application (116) at the mobile communication device (104) matches a PIN stored in the user subscription database (202).

Description

CARDLESS FINANCIAL TRANSACTION

BACKGROUND Technical Field [0001] The embodiments herein generally relate to ATM transaction processing, and, more particularly, to cash withdrawal transaction method at various locations involving mobile device as the authentication parameter.

Description of the Related Art [0002] Automated teller machines are well known for providing an individual with access to accounts holding at various financial institutions. In recent years, the availability of ATM's has increased rapidly and is commonplace for an individual to use such machines for the withdrawal of funds from various accounts regardless of the financial institution. In fact, ATM's are often found in mails, supermarkets, and other locations where users can easily have access to their accounts. Payment cards (e.g., a debit card or a credit card) are used in conjunction with ATM's and thus offer convenient access to one's checking and/or savings account.

[0003] Various methods currently exist for transferring currency from one location to another location from one user to another user. For example, a first individual transfers funds to second individual from one location to another location through internet banking (the availability of computer may be a challenge at times when required) would result in the second individual to wait for a while or a day. This again depends on the type of transaction and nature of banking. However, there is no such system where the second individual can access funds from the first individual in absence of the first individual. The second individual can access to funds if he/she has the payment card of the first individual. However, even if a user owns a payment card, one easily fraud by tampering the payment card. ATM are also prone to frauds/identity theft's like card skimming, stealing of PIN number etc over million dollars worth of frauds are reported across the globe annually. Accordingly, there remains a need for securing ATM transactions. SUMMARY

[0004] In view of the foregoing, an embodiment herein provides an authentication server to authenticate in real time a cash withdrawal transaction from a bank account of a remitter. The cash withdrawal transaction is performed at an automatic teller machine (ATM) by a beneficiary without using an electronic card. The remitter is subscribed to an authentication service having a user subscription database on the authentication server. The authentication server is configured to execute an authentication process including processing a request from a mobile communication device associated with the remitter to authorize the cash withdrawal transaction performed by the beneficiary, the request includes a contact number of a mobile communication device associated with the beneficiary, a transaction amount, and a location identifier of the cash withdrawal transaction, verifying that the remitter is subscribed to the authentication service based on an information associated with the mobile communication device associated with the remitter, generating a transaction code if the transaction amount is less than an available balance in the bank account of the remitter, communicating the transaction code to the mobile communication device associated with the remitter, the remitter communicates the transaction code to the beneficiary, and the beneficiary enters the transaction code, the transaction amount, and a contact number associated with the mobile communication device associated with the remitter at the ATM to perform the cash withdrawal transaction, communicating a request to the mobile communication device associated with the remitter, the request includes a request for a PIN associated with a client application of the mobile communication device associated with the remitter, obtaining the PIN from the mobile communication device associated with the remitter to authorize the cash withdrawal transaction, and authenticating the cash withdrawal transaction if the PIN matches with a PIN associated with the remitter stored in the user subscription database.

[0005] The authentication further includes communicating an acknowledgement message to the beneficiary on the cash withdrawal transaction being authenticated. The beneficiary enters a financial institution identifier associated with the bank account of the remitter at the ATM on receiving from the remitter to perform the cash withdrawal transaction if the ATM is an ATM that is not associated with the bank account. The remitter communicates the transaction code, the transaction amount, the contact number associated with the mobile communication device associated with the remitter, and the financial institution identifier associated with the bank account of the remitter to the beneficiary via at least one of an SMS channel, an MMS channel, a GPRS data channel, a CDMA data channel, a Bluetooth channel, an infrared channel, an Interactive Voice Response (IVR), or a 3G network. The beneficiary withdraws cash less than the transaction amount from the bank account of the remitter at the ATM. The location identifier is at least one of a STD code, an ISD code, or a postal code.

[0006] In another aspect, an authentication server to authenticate in real time a cash withdrawal transaction from a bank account of a remitter is provided. The cash withdrawal transaction is performed at an automatic teller machine (ATM) by a beneficiary without using an electronic card. The remitter is subscribed to an authentication service having a user subscription database on the authentication server. The authentication server is configured to execute an authentication process including processing a request from the remitter to authorize a transaction amount from the bank account of the remitter to be dedicated to the beneficiary, verifying that the remitter is subscribed to the authentication service based on an information associated with the mobile communication device associated with the remitter, generating a transaction code if the transaction amount is less than an available balance in the bank account of the remitter, communicating the transaction code to at least one of a mobile communication device associated with the remitter or a mobile communication device associated with the beneficiary, the request includes a contact number of the mobile communication device associated with the beneficiary, a transaction amount, and a location identifier of the cash withdrawal transaction and the beneficiary enters the transaction code, the transaction amount, and at least one of a contact number associated with the mobile communication device associated with the remitter or a contact number associated with the mobile communication device associated with the beneficiary at the ATM to perform the cash withdrawal transaction, the beneficiary additionally enters a financial institution identifier associated with the bank account of the remitter at the ATM if the ATM is not of a bank with which the remitter has the bank account. [0007] The authentication process further includes communicating a message to the mobile communication device associated with the remitter, the message includes a request for a confirmation to authorize the cash withdrawal transaction, receiving a response to the request, wherein the response indicates one of a 'yes' or a 'no' from a client application of the mobile communication device associated with the remitter, the remitter sends the response that indicates 'no' to decline the cash withdrawal transaction based on one of a potential fraud or an error on receiving the request from the authentication server, and authenticating the cash withdrawal transaction to the beneficiary based on the response, the remitter declines the cash withdrawal transaction using a client application of the mobile communication device associated with the remitter if the remitter suspects the potential fraud or if the remitter sent the request to authorize the cash withdrawal transaction in error. [0008] The authentication process further includes communicating an acknowledgement message to the beneficiary on the cash withdrawal transaction being authenticated by the authentication server. The beneficiary declines the cash withdrawal transaction using a mobile communication device associated with the beneficiary if the beneficiary suspects the potential fraud. The beneficiary withdraws cash equal to the , transaction amount from the bank account of the remitter at the ATM. The request from the s. remitter to authorize the transaction amount is processed on the mobile communication A ? device of the remitter using the client application. The remitter communicates the transaction ι\ code, the transaction amount, the contact number associated with the mobile communication,^ device associated with the remitter, and the financial institution identifier associated with the , \ bank account of the remitter to the beneficiary via at least one of a telephone call, an email, or a voice message. The beneficiary receives the acknowledgement message from the authentication server via at least one of a SMS, a MMS, or an IVR.

[0009] In yet another aspect, a method of authenticating in real time a cash withdrawal transaction from a bank account of a remitter is provided. The cash withdrawal transaction is performed at an automatic teller machine (ATM) by a beneficiary without using an electronic card. The remitter is subscribed to an authentication service having a user subscription database on the authentication server. The authentication server is configured to execute an authentication process including processing a request from the remitter to authorize a transaction amount from the bank account of the remitter to be dedicated to the beneficiary, verifying that the remitter is subscribed to the authentication service based on an information associated with the mobile communication device associated with the remitter, generating a transaction code if the transaction amount is less than an available balance in the bank account of the remitter, communicating the transaction code to at least one of a mobile communication device associated with the remitter or a mobile communication device associated with the beneficiary, the request comprises a contact number of the mobile communication device associated with the beneficiary, a transaction amount, and a location identifier of the cash withdrawal transaction and the beneficiary enters the transaction code, the transaction amount, and at least one of a contact number associated with the mobile communication device associated with the remitter or a contact number associated with the mobile communication device associated with the beneficiary at the ATM to perform the cash withdrawal transaction, the beneficiary additionally enters a financial institution identifier associated with the bank account of the remitter at the ATM if the ATM is not of a bank with which the remitter has the bank account.

[0010] The authentication process further includes communicating a message to the mobile communication device associated with the remitter, the message includes a request for a confirmation to authorize the cash withdrawal transaction, receiving a response to the request, wherein the response indicates one of a 'yes' or a 'no' from a client application of the mobile communication device associated with the remitter, the remitter sends the response that indicates 'no' to decline the cash withdrawal transaction based on one of a potential fraud or an error on receiving the request from the authentication server, and authenticating the cash withdrawal transaction to the beneficiary based on the response, and communicating an acknowledgement message to the beneficiary on the cash withdrawal transaction being authenticated by the authentication server.

[0011] The remitter declines the cash withdrawal transaction using a client application of the mobile communication device associated with the remitter if the remitter suspects a potential fraud or if the remitter has sent the request to authorize the cash withdrawal transaction in error. The beneficiary declines the cash withdrawal transaction using the mobile communication device associated with the beneficiary if the beneficiary suspects the potential fraud. The remitter communicates the transaction amount, the contact number associated with the mobile communication device associated with the remitter, and the financial institution identifier associated with the bank account of the remitter to the beneficiary via at least one of an SMS channel, an MMS channel, a GPRS data channel, a CDMA data channel, a Bluetooth channel, an infrared channel, an Interactive Voice Response (IVR), or a 3G network. The beneficiary receives the acknowledgement message from the authentication server via at least one of the SMS channel, the MMS channel, or the IVR. [0012] The request from the remitter to authorize the transaction amount from the bank account of the remitter to be dedicated to the beneficiary is sent to the authentication server using the client application of the mobile communication device associated with the remitter. The request from the remitter to authorize the transaction amount from the bank account of the remitter to be dedicated to the beneficiary is sent to the authentication server via internet banking.

[0013] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:

[0015] FIG. 1 illustrates a system view of a remitter communicating with a beneficiary through a network according to an embodiment herein; [0016] FIG. 2 illustrates an exploded view of the authentication server of FIG. 1 having a database, a updating module, a validating module, a message generating module, a matching module, and an acknowledgement module to an embodiment herein;

[0017] FIG. 3 is an interaction diagram illustrating an ATM transaction between the remitter of FIG. 1, and the beneficiary of FIG. 1 according to an embodiment herein; [0018] Fig. 4A and 4B is a table view of the database of the authentication server of

FIG. 1 according to an embodiment herein; [0019] FIG. 5 illustrates an exploded view of the mobile communication device of FIG. 1 according to an embodiment herein;

[0020] FIG. 6 illustrates a schematic diagram of a computer architecture used in accordance with the embodiment herein; and [0021] FIG. 7 is a flow diagram illustrating a method of authenticating a cash withdrawal transaction from a bank account of a remitter at an automatic teller machine (ATM) by a beneficiary without using an electronic card according to an embodiment herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

[0022] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein. [0023] As mentioned, there remains a need for securing ATM transactions. The embodiments herein achieve this by providing an authentication to a beneficiary to withdraw cash at an ATM from one location by a remitter from another location. Referring now to the drawings, and more particularly to FIGS. 1 through 7, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0024] FIG. 1 illustrates a system view of a remitter 102 communicating with a beneficiary 112 through a network 106 according to an embodiment herein. The system 100 includes the remitter 102, a mobile communication device 104, the network 106, the authentication server 108, the beneficiary 112, a mobile communication device 110 associated with the beneficiary 112, and an ATM machine 114. The remitter 102 registers with the authentication server 108 by subscribing to a service through the network 106 (e.g., an SMS channel, an MMS channel, a GPRS data channel, a CDMA data channel, and/or a 3G network). The mobile communication device 104 of remitter 102 includes a client application 116. In one embodiment, the mobile communication device 104 includes at least one of any International Mobile Equipment Identity (IMEI) information, Subscriber Identity Module IMSI information and a contact number. In another embodiment, the mobile communication device 110 of beneficiary 112 may include a . client application 116 (not shown in FIG. 1).

[0025] The client application 116 may be a software application. In one embodiment, the mobile communication device 104 must have some provision for downloading the client application 116 (e.g., Bluetooth). In another embodiment, the client application 116 is sent through an SMS channel to the mobile communication device 104. In yet another embodiment, the remitter 102 may download the client application 116 on the mobile communication device 104 through internet (e.g., by connecting a data cable to the mobile communication device 104). [0026] An installation of the client application 116 is processed on the mobile communication device 104. A confirmation is sent by the remitter 102 to the authentication server 108. Simultaneously, the client application 116 residing on the mobile communication device 104 automatically sends the IMEI information, the SIM information (IMSI), the contact information associated with the mobile communication device 104 of the remitter 102 to the authentication server 108. The information associated with the mobile communication device 104 may be sent via SMS channel or a GPRS channel (e.g., internet).

[0027] In one embodiment, the client application 116 may send the IMEI information and the contact information to the authentication server 108. In another embodiment, the client application 116 may send the SIM information and the contact information to the authentication server 108. In yet another embodiment, the client application may send the IMEI information and the SIM information (IMSI) to the authentication server 108. In addition, the remitter 102 may register to the service for a secondary mobile communication device (e.g., in the event if the primary mobile communication device is not available).

[0028] The remitter 102 pays the transaction amount to the beneficiary 112 through ATM machine 114 without using a payment card (e.g., a credit card, a debit card, or an ATM card). In one embodiment, beneficiary 112 is in another location. In one embodiment, the remitter 102 and the beneficiary 112 are in different location but in a same city. In another embodiment, both users (e.g., the remitter 102 and the beneficiary 112) are in different cities (e.g. or countries). The mobile communication device 104 and the mobile communication device 110 may be a GSM phone, a UMTS phone, a CDMA phone, a CDMA 2000 phone, a TDMA phone, a smart phone, a PDA (Pocket Digital Assistant), a touch sensitive device, a handheld device, and/or a wireless device. The mobile communication device 104 of the remitter is used to send the transaction details for cash withdrawal to the authentication server 108 and the beneficiary 112.

[0029] The network 106 may be at least one of an SMS channel, an MMS channel, a GPRS data channel, a CDMA data channel, and/or a 3G/2G network. The authentication server 108 may be computer at a remote location. The ATM machine 114 may be at different locations where a beneficiary 112 may enter the transaction details associated with remitter 102 and collect the transaction amount.

[0030] The authentication server 108 sends and receives a message (e.g., a SMS (Short messaging service, an MMS, or an IVR) from the mobile communication device 104 and the mobile communication device 110 through the network 106. In one embodiment, the authentication server 108 communicates a transaction code to the mobile communication device 104 associated with the remitter. The client application 116 is installed in the mobile communication device 104. When the remitter 102 subscribes for a service from the authentication server 108, the remitter 102 can then send a transaction request to the authentication server 108 via an SMS or an IVR.

[0031] FIG. 2 illustrates an exploded view of the authentication server 108 of FIG. 1 having a database 202, an updating module 204, a validating module 206, a code generating module 208, a matching module 210 and an^" acknowledgement module 212 according to an embodiment herein. The matching module 210 further includes a location identifier module 214, a financial institution identifier module 216, and a pin authentication module 218. The database 202 contains the remitter information, beneficiary information, the contact information, the transaction amount information, the location information of the ATM machine where cash is withdrawn, a financial institution ID code information, transaction code information, the pin. The updating module 204 updates the user information (e.g., information of the remitter 102 and the beneficiary 112) in the database 202 and validates the remitter 102 financial account information in the database 202. The remitter initiates a transaction request to the authentication server 108 by sending a contact number of the mobile communication device 110 associated with the beneficiary 112, a transaction amount, and a location identifier of the cash withdrawal transaction. In one embodiment, the transaction request received from the remitter 102 is processed to authorize a transaction amount from the bank account of the remitter 102 to be dedicated to the beneficiary 112 using the client application 116 of the mobile communication device 104 of the remitter 102. In another embodiment, the transaction request received from the remitter 102 is processed to authorize a transaction amount from the bank account of the remitter 102 to be dedicated to the beneficiary 112 via internet banking. The location identifier module 214 identifies the location of based on the information or the details entered at the ATM 114.

[0032] The code generating module 208 generates a transaction code and sends to the remitter 102 on requisitions from the authentication server 108. In one embodiment, the remitter 102 sends the transaction code to the beneficiary 112 for entering at the ATM machine 114. The beneficiary 112 also enters the contact number, transaction amount, a location identifier (e.g., a STD code, or an ISD code, or a postal code) associated with the transaction amount, and a financial institution ID code for transacting the amount from remitter bank account. The validating module 206 validates the transaction through the authentication server 108 by requesting the remitter 102 to enter the (PIN). In one embodiment, the PIN is a 4 digit identification number.

[0033] The matching module 210 matches a location associated with the cash withdrawal transaction, a financial institution identifier associated with the bank account of the remitter, and the PIN received from the remitter 102 with the one stored in the database 202 of the authentication server 108. In another embodiment, the authentication server 108 on receiving the PIN from the remitter 102 authenticates the transaction and sends an SMS to the mobile communication device 110 of beneficiary 112 to acknowledge the transaction. The pin authentication module matches the received PIN with a PIN stored the database 202. In one embodiment, the acknowledgement module 212 sends a message to the beneficiary 112 to acknowledge the message for performing the transaction. [0034] The beneficiary 112 acknowledges the transaction by sending a response. In one embodiment, a YES response is sent to the authentication server 108 through the mobile communication device 110 of the beneficiary 112. In another embodiment, a NO response is sent to the authentication server 108 through the mobile communication device 110 of the beneficiary. In yet another embodiment, the beneficiary 112 may have to additionally enter the amount of cash to withdraw (e.g., same as the remitter entering the information), the financial institution identifier, the transaction code. In one embodiment, the beneficiary 112 additionally enters a financial institution identifier associated with the bank account of the remitter 102 at the ATM 114 if the ATM 114 is not of a bank with which the remitter 102 has the bank account. The financial institution identifier module 216 matches the financial institution identifier with the one stored in the database 202. [0035] In one embodiment, the beneficiary may enter a partial amount for cash withdrawal. When the authentication server 108 receives the acknowledgement message from the beneficiary 112, the cash gets dispensed through the ATM 114 to the beneficiary 112 who is in a different location from remitter 102. The beneficiary 112 and the remitter 102 may be in the same location or a different location (e.g., a different city or a different country). In one embodiment, if the beneficiary 112 is withdrawing cash, at times, may not receive the acknowledgement message.

[0036] FIG. 3 is an interaction diagram of an ATM transaction between the remitter 102, the authentication server 108, and the beneficiary 112 of FIG. 1 according to an embodiment herein. FIG. 3 illustrates a series of operations carried out during various stages of interaction between the remitter 102, the beneficiary 112, the authentication server 108 and the ATM machine 114. In operation 302, the remitter 102 generates a transaction request and sends to the authentication server 108 by entering beneficiary 112 contact number of the mobile communication device 110, a location identifier (e.g., a STD code, or an ISD code, or a postal code) of cash withdrawal and the amount to initiate the transaction to the beneficiary 112. The remitter generates the transaction request to authorize a transaction amount from the bank account of the remitter 102 to be dedicated to the beneficiary 112.

[0037] In one embodiment, the transaction request received from the remitter 102 is processed to authorize a transaction amount from the bank account of the remitter 102 to be dedicated to the beneficiary 112 using the client application 116 of the mobile communication device 104 of the remitter 102. In another embodiment, the transaction request received from the remitter 102 is processed to authorize a transaction amount from the bank account of the remitter 102 to be dedicated to the beneficiary 112 via internet banking. This information may be stored on the database 202 of the authentication server 108. [0038] In one embodiment, the transaction may be associated with the authentication server 108, the ATM 112 and the beneficiary 112. In operation 304, the authentication server 108 generates a transaction code (e.g., using a code generating module 208) and sends to the remitter 102 on request from the remitter 102. The authentication server 108 may send the transaction code to the remitter 102 via at least one of a SMS channel, a GPRS channel and/or IVR channel. The authentication server 108 may also send the transaction code to the beneficiary 112 via at least one of a SMS channel, a GPRS channel and/or IVR channel. The authentication server 108 verifies that the remitter 102 is subscribed to the authentication service based on information associated with the mobile communication device associated with the remitter 102. The authentication server 108 generates the transaction code if the transaction amount is less than an available balance in the bank account of the remitter 102.

[0039] In one embodiment, the remitter 102 may decline the cash withdrawal transaction at any time after initiating the transaction request using the client application 116 of the mobile communication device 104 associated with the remitter 102 if the remitter 102 suspects a potential fraud or if the remitter 102 sends the request to authorize the cash withdrawal transaction in error. In operation 306, the remitter 102 receives the transaction code and sends the transaction code to the beneficiary 112 along with a financial institution identifier to perform the cash withdrawal transaction. In one embodiment, the authentication server 108 may also send the transaction code to the beneficiary 112. In operation 308, the beneficiary 110 enters a contact number associated with the mobile communication device 104 of the remitter 102 or a contact number associated with the mobile communication device 110 of the beneficiary 112, the transaction code received from the remitter 102. In one embodiment, the beneficiary 110 may also additionally enter the financial institution identifier associated with the bank account of the remitter 102 at the ATM 114 if the ATM 114 is not of a bank with which the remitter 102 has the bank account. [0040] In operation 310, the authentication server 108 requests the remitter 102 to enter the Personal Identification Number (PIN) to authenticate the transaction. In one embodiment, the authentication server 108 may send a message for confirming the cash withdrawal transaction. In operation 312, the remitter 102 receives the request from the authentication server 108 and enters the PFN (e.g., 4 digit pin) and sends to the authentication server 108 (e.g., via SMS channel, a GPRS channel or an IVR). In one embodiment, the remitter 102 may respond to the request by logging into the client application 116 and entering a YES/NO response and sending it to the authentication server 108.

[0041] In operation 314, the authentication server 108 receives the PIN as authentication message from remitter 102 and sends an SMS to beneficiary 112 to acknowledge the cash withdrawal transaction. The authentication server 108 may receive a YES/NO response from the mobile communication device 104 associated with the remitter 102. In one embodiment, the authentication server 108 validates the PIN received from the remitter 102 and authenticates the transaction. The authentication server 108 matches the PIN received from the remitter 102 using the PIN authentication module 218. In another embodiment, the authentication server 108 may confirm the transaction based on the YES/NO response received from the remitter 102. In one embodiment, the NO response indicates that the remitter 102 has declined the cash withdrawal transaction based on one of the potential fraud or the error. In operation 316, the authentication server 108 sends an acknowledgement message (e.g., using the acknowledgement module 212) to the beneficiary 112. In one embodiment, the acknowledgement may be communicated by at least one of a SMS channel, a MMS channel and/or an IVR to the beneficiary 112.

[0042] In operation 318, the beneficiary 112 acknowledges the transaction. In one embodiment, the beneficiary 112 may respond a YES/NO message to the authentication server 108 for acknowledging the message received. In another embodiment, the beneficiary 112 may have to additionally enter the amount of cash to withdraw (e.g., same as the remitter entering the information). In one embodiment, the beneficiary 112 may withdraw the cash less than the transaction amount or equal to the transaction amount. In operation 320, the authentication server 108 receives the acknowledgement message from beneficiary 112, and dispenses the cash at the ATM 114 to be withdrawn by the beneficiary. The beneficiary 112 may decline the cash withdrawal transaction using the mobile communication device 110 associated with the beneficiary 112 if the beneficiary 112 suspects the potential fraud.

[0043] Fig. 4A and 4B is a table view of the database 202 of the authentication server 108 of FIG. 1 according to an embodiment herein. The database 202 includes a Transaction amount information field 402, a remitter 102 contact information field 404, a beneficiary 112 contact information field 406, a financial account information field 408, a location information field 410, a transaction information field 412 and a pin field 414. [0044] The transaction amount information field contains the amount to be transacted from the remitter 102 to the beneficiary 112. The contact information field 404 contains the contact numbers (e.g., 9111763526) associated with the mobile communication device 104 of the remitter 102 for sending and receiving SMS messages. The contact information field 406 contains mobile numbers (e.g., 9894856231, 9587426351) associated with the mobile communication device 110 of the beneficiary 112 for sending and receiving SMS messages. In one embodiment, remitter 102 and the beneficiary 112 are in different location (e.g., the remitter 102 is in Mumbai and the beneficiary 112 is in Bangalore).

[0045] The financial account information field 408 contains the financial institution identifier (e.g., 187426) for the amount to be transacted from the specified financial institution (e.g., remitter bank information from where he/she wants to transact). The location information field 410 contains the place of cash withdrawal (e.g., M G Road in Bangalore, and Sri Lanka) of the beneficiary 112. The Transaction information field 412 contains the transaction code (e.g., 7456) information associated with the cash withdrawal transaction for which the transaction amount 402 to be transferred from the remitter 102 to the beneficiary 112. The PIN field 414 contains the PIN of the remitter 102 to be sent to the authentication server 108 for authenticating the transaction.

[0046] FIG. 4B is a table view of the database 202 of the authentication server 108 of FIG. 1 according to an embodiment herein. The database 202 includes an IMEI information field 416, a contact information field 418, and a SIM information field 420 associated with the mobile communication device 104 of the remitter 102. The IMEI information field 416 contains the IMEI information (e.g., 3231457284982265) associated with the mobile communication device 104 of the remitter 102.

[0047] The contact information field 418 contains the contact information (e.g., 9111763526) of the remitter 102 associated with the mobile communication device 104. The SIM information field 420 contains the SIM information IMSI (e.g., 5362748762167) associated with the mobile communication device 104 of the remitter 102. [0048] FIG. 5 illustrates an exploded view of the mobile communication device 104 of FIG. 1 having an a memory 502 having a computer set of instructions, a bus 504, a display 506, a speaker 508, and a processor 510 capable of processing a set of instructions to perform any one or more of the methodologies herein, according to an embodiment herein. The processor 510 may also enable digital content to be consumed in the form of video for output via one or more displays 506 or audio for output via speaker and/or earphones 508. The processor 510 may also carry out the methods described herein and in accordance with the embodiments herein.

[0049] Digital content may also be stored in the memory 502 for future processing or consumption. The memory 502 may also store program specific information and/or service information (PSI/SI), including information about digital content (e.g., the detected information bits) available in the future or stored from the past. A user 502 of the mobile communication device 104 may view this stored information on display 506 and select an item of for viewing, listening, or other uses via input, which may take the form of keypad, scroll, or other input device(s) or combinations thereof. When digital content is selected, the processor 510 may pass information. The content and PSI/SI may be passed among functions within the mobile communication device 104 using bus 504.

[0050] The techniques provided by the embodiments herein may be implemented on an integrated circuit chip (not shown). The chip design is created in a graphical computer programming language, and stored in a computer storage medium (such as a disk, tape, physical hard drive, or virtual hard drive such as in a storage access network). If the designer does not fabricate chips or the photolithographic masks used to fabricate chips, the designer transmits the resulting design by physical means (e.g., by providing a copy of the storage medium storing the design) or electronically (e.g., through the Internet) to such entities, directly or indirectly.

[0051] The stored design is then converted into the appropriate format (e.g., GDSII) for the fabrication of photolithographic masks, which typically include multiple copies of the chip design in question that are to be formed on a wafer. The photolithographic masks are utilized to define areas of the wafer (and/or the layers thereon) to be etched or otherwise processed. The resulting integrated circuit chips can be distributed by the fabricator in raw wafer form (that is, as a single wafer that has multiple unpackaged chips), as a bare die, or in a packaged form. In the latter case the chip is mounted in a single chip package (such as a plastic carrier, with leads that are affixed to a motherboard or other higher level carrier) or in a multichip package (such as a ceramic carrier that has either or both surface interconnections or buried interconnections). [0052] In any case the chip is then integrated with other chips, discrete circuit elements, and/or other signal processing devices as part of either (a) an intermediate product, such as a motherboard, or (b) an end product. The end product can be any product that includes integrated circuit chips, ranging from toys and other low-end applications to advanced computer products having a display, a keyboard or other input device, and a central processor.

[0053] The embodiments herein can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment including both hardware and software elements. The embodiments that are implemented in software include but are not limited to, firmware, resident software, microcode, etc. [0054] Furthermore, the embodiments herein can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can comprise, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

[0055] The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk - read only memory (CD-ROM), compact disk - read/write (CD-R/W) and DVD.

[0056] A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

[0057] Input/output (I/O) devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters.

[0058] A representative hardware environment for practicing the embodiments herein is depicted in FIG. 6. This schematic drawing illustrates a hardware configuration of an information handling/computer system in accordance with the embodiments herein. The system comprises at least one processor or central processing unit (CPU) 10. The CPUs 10 are interconnected via system bus 12 to various devices such as a random access memory (RAM) 14, read-only memory (ROM) 16, and an input/output (I/O) adapter 18. The I/O adapter 18 can connect to peripheral devices, such as disk units 11 and tape drives 13, or other program storage devices that are readable by the system. The system can read the inventive instructions on the program storage devices and follow these instructions to execute the methodology of the embodiments herein.

[0059] The system further includes a user interface adapter 19 that connects a keyboard 15, mouse 17, speaker 24, microphone 22, and/or other user interface devices such as a touch screen device (not shown) to the bus 12 to gather user input. Additionally, a communication adapter 20 connects the bus 12 to a data processing network 25, and a display adapter 21 connects the bus 12 to a display device 23 which may be embodied as an output device such as a monitor, printer, or transmitter, for example. [0060] FIG. 7 is a flow diagram illustrating a method of authenticating a cash withdrawal transaction from a bank account of the remitter 102 at an automatic teller machine (ATM) 114 by the beneficiary 112 without using an electronic card according to an embodiment herein. The remitter 102 is subscribed to an authentication service having a user subscription database 202 on the authentication server 108. In step 702, a request from the remitter 102 is processed to authorize a transaction amount from the bank account of the remitter 102 to be dedicated to the beneficiary 112. The request includes a contact number of the mobile communication device 110 associated with the beneficiary 112, a transaction amount, and a location identifier (e.g., a STD code, an ISD code, or a postal code) of the cash withdrawal transaction. In one embodiment, the transaction request received from the remitter 102 is processed to authorize a transaction amount from the bank account of the remitter 102 to be dedicated to the beneficiary 112 using the client application 116 of the mobile communication device 104 of the remitter 102. In another embodiment, the transaction request received from the remitter 102 is processed to authorize a transaction amount from the bank account of the remitter 102 to be dedicated to the beneficiary 112 via internet banking. [0061] In step 704, it is verified at the authentication server 108 that the remitter 102 is subscribed to the authentication service based on an information associated with the mobile communication device 104 associated with the remitter 102. In step 706, a transaction code is generated if the transaction amount is less than an available balance in the bank account of the remitter 102. In step 708, the transaction code is communicated to at least one of the mobile communication device 104 associated with the remitter 102 or the mobile communication device 110 of the beneficiary. In one embodiment, the remitter 102 may also communicate the transaction code to the beneficiary 112.

[0062] The beneficiary 112 enters the transaction code, the transaction amount, a contact number associated with the mobile communication device associated with the remitter 102, and a financial institution identifier associated with the bank account of the remitter at the ATM to perform the cash withdrawal transaction. The financial institution identifier is matched (e.g., using the financial identifier module 216 of FIG. 2) with the one stored in the database 202. The beneficiary 112 additionally enters a financial institution identifier associated with the bank account of the remitter 102 at the ATM 114 if the ATM is not of a bank with which the remitter 102 has the bank account. Simultaneously, the location of the cash withdrawal transaction is identified (using the location identifier module 214 of FIG. 2) when the beneficiary 112 enters the transaction code, the transaction amount, the contact number associated with the mobile communication device 104 associated with the remitter 102, and the financial institution identifier associated with the bank account of the remitter at the ATM 114 to perform the cash withdrawal transaction. In one embodiment, the beneficiary 112 additionally enters the financial institution identifier associated with the bank account of the remitter 102 at the ATM 114 if the ATM 114 is not of a bank with which the remitter 102 has the bank account.

[0063] In step 710, a message is communicated to the mobile communication device 104 associated with the remitter 102. The message includes a request for a confirmation to authorize the cash withdrawal transaction. In step 712, a response to the request is received from the remitter 102 at the authentication server 108. The response indicates one of a 'yes' or a 'no' from the client application 116 of the mobile communication device 104 associated with the remitter 102.

[0064] The remitter 102 sends the response that indicates 'no' to decline the cash withdrawal transaction based on one of the potential fraud or the error on receiving the request from the authentication server 108. In step 714, the authentication server 108 authenticates the cash withdrawal transaction to the beneficiary 112 based on the response. In step 716, an acknowledgement message is communicated to the beneficiary 112 from the authentication server 108 on the cash withdrawal transaction being authenticated by the authentication server 108. In one embodiment, the acknowledgement module 212 of FIG. 2 generates the acknowledgement message and sends to the mobile communication device 110 of the beneficiary 112. The remitter 102 may decline the cash withdrawal transaction using the client application 116 of the mobile communication device 104 associated with the remitter 102 if the remitter 102 suspects a potential fraud or if the remitter 102 sent the request to authorize the cash withdrawal transaction in error. The beneficiary 112 may declines the cash withdrawal transaction using the mobile communication device 110 associated with the beneficiary 112 if the beneficiary 112 suspects the potential fraud.

[0065] The remitter 102 communicates the transaction amount, the contact number associated with the mobile communication device 104 associated with the remitter 102, and the financial institution identifier associated with the bank account of the remitter 102 to the beneficiary 112 via at least one of an SMS channel, an MMS channel, a GPRS data channel, a CDMA data channel, a Bluetooth channel, an infrared channel, an Interactive Voice Response (IVR), or a 3G network. The beneficiary 112 receives the acknowledgement message from the authentication server 108 via at least one of the SMS channel, the MMS channel, or the IVR.

[0066] The cash withdrawal transaction at an ATM without using an electronic card. The remittances can be made at a substantially lower cost. The remittances can be made from one location to other location (e.g., from one location within the city to other location within the city, from one city to other city, or from one country to other country) without incurring wire transfer charges. If the beneficiary withdraws cash from an ATM of a bank other than the bank with which the remitter has the bank account, the beneficiary enters a financial institution identifier associated with the bank account of the remitter.

[0067] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the appended claims.

Claims

What is claimed is: 1. An authentication server to authenticate in real time a cash withdrawal transaction from a bank account of a remitter, wherein said cash withdrawal transaction is performed at an automatic teller machine (ATM) by a beneficiary without using an electronic card, wherein said remitter is subscribed to an authentication service having a user subscription database on said authentication server, said authentication server configured to execute an authentication process comprising: processing a request from a mobile communication device associated with said remitter to authorize said cash withdrawal transaction performed by said beneficiary, wherein said request comprises a contact number of a mobile communication device associated with said beneficiary, a transaction amount, and a location identifier of said cash withdrawal transaction; verifying that said remitter is subscribed to said authentication service based on an information associated with said mobile communication device associated with said remitter; generating a transaction code if said transaction amount is less than an available balance in said bank account of said remitter; communicating said transaction code to said mobile communication device associated with said remitter, wherein said remitter communicates said transaction code to said beneficiary, and said beneficiary enters said transaction code, said transaction amount, and a contact number associated with said mobile communication device associated with said remitter at said ATM to perform said cash withdrawal transaction; communicating a request to said mobile communication device associated with said remitter, wherein said request comprises a request for a PIN associated with a client application of said mobile communication device associated with said remitter; obtaining said PIN from said mobile communication device associated with said remitter to authorize said cash withdrawal transaction; and authenticating said cash withdrawal transaction if said PIN matches with a PIN associated with said remitter stored in said user subscription database.

2. The authentication server of claim 1, wherein said authentication process further comprises communicating an acknowledgement message to said beneficiary on said cash withdrawal transaction being authenticated.

3. The authentication server of claim 1, wherein said beneficiary enters a financial institution identifier associated with said bank account of said remitter at said ATM on receiving from said remitter to perform said cash withdrawal transaction if said ATM is an ATM that is not associated with said bank account.

4. The authentication server of claim 3, wherein said remitter communicates said transaction code, said transaction amount, said contact number associated with said mobile communication device associated with said remitter, and said financial institution identifier associated with said bank account of said remitter to said beneficiary via at least one of an SMS channel, an MMS channel, a GPRS data channel, a CDMA data channel, a Bluetooth channel, an infrared channel, an Interactive Voice Response (IVR), or a 3G network.

5. The authentication server of claim 1, wherein said beneficiary withdraws cash less than said transaction amount from said bank account of said remitter at said ATM, wherein said location identifier is at least one of a STD code, an ISD code, or a postal code.

6. An authentication server to authenticate in real time a cash withdrawal transaction from a bank account of a remitter, wherein said cash withdrawal transaction is performed at an automatic teller machine (ATM) by a beneficiary without using an electronic card, wherein said remitter is subscribed to an authentication service having a user subscription database on said authentication server, said authentication server configured to execute an authentication process comprising: processing a request from said remitter to authorize a transaction amount from said bank account of said remitter to be dedicated to said beneficiary; verifying that said remitter is subscribed to said authentication service based on an information associated with said mobile communication device associated with said remitter; generating a transaction code if said transaction amount is less than an available balance in said bank account of said remitter; communicating said transaction code to at least one of a mobile communication device associated with said remitter or a mobile communication device associated with said beneficiary, wherein said request comprises a contact number of said mobile communication device associated with said beneficiary, a transaction amount, and a location identifier of said cash withdrawal transaction and said beneficiary enters said transaction code, said transaction amount, and at least one of a contact number associated with said mobile communication device associated with said remitter or a contact number associated with said mobile communication device associated with said beneficiary at said ATM to perform said cash withdrawal transaction, wherein said beneficiary additionally enters a financial institution identifier associated with said bank account of said remitter at said ATM if said ATM is not of a bank with which said remitter has said bank account; communicating a message to said mobile communication device associated with said remitter, wherein said message comprises a request for a confirmation to authorize said cash withdrawal transaction; ^} receiving a response to said request, wherein said response indicates one of a 'yes' or a 'no' from a client application of said mobile communication device associated with said remitter, wherein said remitter sends said response that indicates 'no' to decline said cash withdrawal transaction based on one of a potential fraud or an error on receiving said request from said authentication server; and authenticating said cash withdrawal transaction to said beneficiary based on said response, wherein said remitter declines said cash withdrawal transaction using a client application of said mobile communication device associated with said remitter if said remitter suspects said potential fraud or if said remitter sent said request to authorize said cash withdrawal transaction in error.

7. The authentication server of claim 6, wherein said authentication process ftirther comprises communicating an acknowledgement message to said beneficiary on said cash withdrawal transaction being authenticated by said authentication server.

8. The authentication server of claim 6, wherein said beneficiary declines said cash withdrawal transaction using a mobile communication device associated with said beneficiary if said beneficiary suspects said potential fraud.

9. The authentication server of claim 6, wherein said beneficiary withdraws cash equal to said transaction amount from said bank account of said remitter at said ATM, wherein said request from said remitter to authorize said transaction amount is processed on said mobile communication device of said remitter using said client application.

10. The authentication server of claim 6, wherein said remitter communicates said transaction code, said transaction amount, said contact number associated with said mobile communication device associated with said remitter, and said financial institution identifier associated with said bank account of said remitter to said beneficiary via at least one of a telephone call, an email, or a voice message.

11. The authentication server of claim 7, wherein said beneficiary receives said acknowledgement message from said authentication server via at least one of a SMS, a MMS, or an IVR.

12. A method of authenticating in real time a cash withdrawal transaction from a bank account of a remitter, wherein said cash withdrawal transaction is performed at an automatic teller machine (ATM) by a beneficiary without using an electronic card, wherein said remitter is subscribed to an authentication service having a user subscription database on said authentication server, said authentication server configured to execute an authentication process comprising: processing a request from said remitter to authorize a transaction amount from said bank account of said remitter to be dedicated to said beneficiary; verifying that said remitter is subscribed to said authentication service based on an information associated with said mobile communication device associated with said remitter; generating a transaction code if said transaction amount is less than an available balance in said bank account of said remitter; communicating said transaction code to at least one of a mobile communication device associated with said remitter or a mobile communication device associated with said beneficiary, wherein said request comprises a contact number of said mobile communication device associated with said beneficiary, a transaction amount, and a location identifier of said cash withdrawal transaction and said beneficiary enters said transaction code, said transaction amount, and at least one of a contact number associated with said mobile communication device associated with said remitter or a contact number associated with said mobile communication device associated with said beneficiary at said ATM to perform said cash withdrawal transaction, wherein said beneficiary additionally enters a financial institution identifier associated with said bank account of said remitter at said ATM if said ATM is not of a bank with which said remitter has said bank account; communicating a message to said mobile communication device associated with said remitter, wherein said message comprises a request for a confirmation to authorize said cash withdrawal transaction; receiving a response to said request, wherein said response indicates one of a 'yes' or a 'no' from a client application of said mobile communication device associated with said remitter, wherein said remitter sends said response that indicates 'no' to decline said cash withdrawal transaction based on one of a potential fraud or an error on receiving said request from said authentication server; authenticating said cash withdrawal transaction to said beneficiary based on said response; and communicating an acknowledgement message to said beneficiary on said cash withdrawal transaction being authenticated by said authentication server, wherein said remitter declines said cash withdrawal transaction using a client application of said mobile communication device associated with said remitter if said remitter suspects a potential fraud or if said remitter sent said request to authorize said cash withdrawal transaction in error, wherein said beneficiary declines said cash withdrawal transaction using said mobile communication device associated with said beneficiary if said beneficiary suspects said potential fraud.

13. The method of claim 12, wherein said remitter communicates said transaction amount, said contact number associated with said mobile communication device associated with said remitter, and said financial institution identifier associated with said bank account of said remitter to said beneficiary via at least one of an SMS channel, an MMS channel, a GPRS data channel, a CDMA data channel, a Bluetooth channel, an infrared channel, an Interactive Voice Response (IVR), or a 3G network.

14. The method of claim 13, wherein said beneficiary receives said acknowledgement message from said authentication server via at least one of said SMS channel, said MMS channel, or said IVR.

15. The method of claim 13, wherein said request from said remitter to authorize said transaction amount from said bank account of said remitter to be dedicated to said beneficiary is sent to said authentication server using said client application of said mobile communication device associated with said remitter.

16. The method of claim 13, wherein said request from said remitter to authorize said transaction amount from said bank account of said remitter to be dedicated to said beneficiary is sent to said authentication server via internet banking.