WO2003098525A1 - Method for guaranteeing safe financial transactions when using wireless network - Google Patents

Method for guaranteeing safe financial transactions when using wireless network Download PDF

Info

Publication number
WO2003098525A1
WO2003098525A1 PCT/KR2003/000957 KR0300957W WO03098525A1 WO 2003098525 A1 WO2003098525 A1 WO 2003098525A1 KR 0300957 W KR0300957 W KR 0300957W WO 03098525 A1 WO03098525 A1 WO 03098525A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
financial transaction
user
requested
financial
Prior art date
Application number
PCT/KR2003/000957
Other languages
French (fr)
Inventor
Kyung-Joon Lee
Si-Woo Pakr
Original Assignee
Ktfreetel Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ktfreetel Co., Ltd. filed Critical Ktfreetel Co., Ltd.
Priority to CN038111837A priority Critical patent/CN1653472B/en
Priority to AU2003228107A priority patent/AU2003228107A1/en
Publication of WO2003098525A1 publication Critical patent/WO2003098525A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3224Transactions dependent on location of M-devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4016Transaction verification involving fraud or risk level assessment in transaction processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/407Cancellation of a transaction
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/42Confirmation, e.g. check or permission by the legal debtor of payment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation or account maintenance
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12Detection or prevention of fraud
    • H04W12/126Anti-theft arrangements, e.g. protection against subscriber identity module [SIM] cloning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60Context-dependent security
    • H04W12/63Location-dependent; Proximity-dependent
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • H04W4/021Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
    • H04W4/185Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals by embedding added-value information into content, e.g. geo-tagging

Definitions

  • the present invention relates to methods for guaranteeing safe financial
  • the present invention relates to a wireless network. More particularly, the present invention relates
  • ATM automatic messaging machine
  • credit card reader when using a wireless network.
  • the object of the present invention is to provide the methods for
  • the user's loss can be less than a
  • Another object of the present invention is to provide the methods for
  • said method comprises the following steps: (1) receiving a financial transaction;
  • FTCR comprises at least one selected from among a group consisting of (a) user identification data, (b) a location of a financial transaction terminal, and (c) a password
  • the user identification data comprises at least one selected from
  • financial transaction is the normal transaction based on the criterion that is selected
  • radius of the financial transaction terminal if either of two conditions occurs as follows: the location of the financial transaction terminal does not correspond to the safe
  • the financial institution system performs the following steps: receiving an
  • ARFT approval request for the financial transaction
  • the financial institution system further performs the step of putting a
  • the step of determining whether or not the requested financial transaction is the
  • the entered password is the emergency password or
  • the calculated distance is more than the predetermined distance. Further, the financial
  • institution system performs the following steps: receiving an ARFT including the
  • entered password is a normal password
  • the financial institution system further performs the step of putting a
  • the method further comprises the following steps: determining whether or not
  • mobile network system oversees is one selected from a group consisting of number(s),
  • the FTCR comprises at least one selected
  • transaction is a normal transaction based on a criterion that is selected from a group
  • the requested financial transaction if the requested financial transaction is a normal transaction according to the determination; and disapproving the requested financial
  • the step of determining whether or not the requested financial transaction is the
  • the password comprises the following steps: determining whether or not
  • the calculated distance is more than a predetermined distance
  • the password comprises the following steps: determining whether or not
  • the entered password is an emergency password
  • the entered password is the emergency password or the calculated
  • the method further comprises the following steps: determining whether or not
  • the method further comprises the step of transmitting a
  • requested financial transaction is a normal transaction based on a criterion that is
  • the requested financial transaction is a normal transaction according to the
  • the requested financial transaction is a temporary abnormal transaction according to the
  • FIG. 1 A through FIG. 1H show various position location technologies.
  • FIG. 2 is a flowchart of the method for guaranteeing safety of a financial transaction according to the present invention.
  • FIG. 3A is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 3B is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 4A is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 4B is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 5 is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 6A through FIG. 6C are flowcharts of the method for guaranteeing safety
  • FIG. 7A is a flowchart of the method for guaranteeing safety of a financial
  • FIG 7B is a flowchart of the method for guaranteeing safety of a financial
  • the present invention is based on the valid assumption that all mobile
  • 'F IT Financial Transaction Terminal'
  • the mobile network system undertakes second approval of a financial
  • FIG. 1A shows AGPS ("Assisted GPS")
  • FIG. IB shows AFLT ("Advanced Forward Link
  • FIG. 1C shows Multipath Fingerprinting
  • FIG. ID shows AOA ("Angle
  • FIG. IE shows TOA ("Time of Arrival")
  • FIG. IF shows TDOA
  • FIG. IG shows a Hybrid method
  • FIG. IH shows a Cell ID
  • the position location system can be classified into an MS (mobile station)-
  • the MS-based solution is based solution, a network-based solution, and a hybrid solution.
  • the MS-based solution is based solution, a network-based solution, and a hybrid solution.
  • the network-based solution comprises GPS, AGPS, and AFLT; the network-based solution comprises TOA, TDOA,
  • the hybrid solution comprises QUALCOMM, Inc.,
  • gpsOneTM which combines AFLT and AGPS. Since GPS based solution is well known
  • MS station provides partial GPS data to MS.
  • AFLT produces the subscriber's position by the use of a
  • AFLT is MS-based version of TDOA.
  • AFLT solution calculates the subscriber's position as
  • calculated position depends on the kind of method for measuring arrival time, multi-
  • Multipath Fingerprinting solution calculates the subscriber's position by the use
  • the Multipath Fingerprinting solution calculates the subscriber's position as
  • a position decision module determines the position by comparing the RF signature
  • Fingerprinting are as follows: (1) uses one received signal different from other network-
  • the AOA solution calculates the subscriber's position by the using an incidence
  • two BS measure the incidence angle of an arrived signal transmitted from the MS.
  • the MS travels further away from the BS.
  • a hybrid solution which is a combination of AFLT and AGPS, produces the
  • this solution can provide the subscriber's
  • FIG. 2 is a flowchart of the method for guaranteeing safety of a financial
  • the present invention relates to methods
  • step 100 when a user who subscribes to the safe financial transaction
  • the FTT reads card data from a cash card or credit card and receives a password inputted
  • the requested transaction is approved as a normal
  • step 106
  • step 106 the safe financial transaction service predetermined by the user is initiated.
  • the requested transaction is defined as a temporary abnormal
  • the requested transaction is defined as a
  • step 108 when the requested transaction is defined as the temporary abnormal transaction, the distance between the location where the financial transaction
  • the requested financial transaction location can be determined by
  • the location of the user's mobile terminal can be determined by
  • a confirmation message will be sent to the user's mobile terminal (step 112).
  • the reason to send a confirmation message is that even though the user is located near
  • location and the location of the user's mobile terminal may be in the same cell when a
  • the confirmation message is sent to the user's mobile terminal.
  • the message is a kind of bi-directional message such as ARS voice call, a
  • the user can send the confirmation data (for example, "Is it
  • an emergency results when the user does
  • step 118 the location of the user's mobile terminal and information of all
  • radius is (1) the radius of a cell in a cell ID solution, or (2) the radius of an error range
  • step 120 if the user does not input valid confirmation data, the system
  • FIG. 3A is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 3A shows the method for guaranteeing safety of a financial transaction by using a
  • the financial institution's system (1) oversees the payment
  • step 150 the user inserts his card to FTT and enters the password for the
  • step 152 a determination is made whether or not the entered password corresponds to the normal password. If the normal password is indicated, at step 152.
  • step 154 approval is given for a normal transaction and the user can draw out the
  • step 152 determines not only
  • step 156 if the entered password is not the normal password, the system
  • the system defines the requested transaction as a temporary abnormal transaction
  • step 160 If the user does not subscribe to the DP or the entered password
  • step 158 the system proceeds to step 158 to invalidate the requested
  • step 160 if the requested transaction is defined as the temporary abnormal
  • step 162 permits the cash withdrawal
  • the user can determine the allowance limit, however, preferably the financial institution will determine the allowance limit. Also,
  • the monetary balance displayed on FTT or printed on the receipt is the
  • step 164 if the mobile network system receives the confirmation request of
  • the mobile network system searches the current location of the
  • the current location of the user is sent to the financial institution.
  • step 172 requests the mobile network system to record all mobile terminal
  • the mobile network system On receiving the record request, the mobile network system
  • step 176 If the calculated distance is greater than the predetermined distance, the system proceeds to step 176.
  • the financial institution's system sends a confirmation message to
  • the confirmation message includes the description about the
  • the user can send
  • SMS confirmation data via SMS, ARS or Internet.
  • step 178 if the confirmation data transmitted by the user is valid, the
  • step 180 to release the allowance limit and pay
  • step 182 if the requested transaction is considered an emergency, further
  • the confirmation message is sent to the user's
  • the user is requested to input confirmation data
  • the user can be approved by inputting the confirmation data
  • FIG. 3B is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 3B shows the method for guaranteeing safety of a financial transaction
  • the financial institution's system oversees the payment
  • the pre-steps 200 to 210 for the safe financial transaction such as determination
  • Step 200 to step 208 are identical to step 150 to
  • step 158 there are some differences at step 202 or step 206; if another
  • step 210 to send the entered password to the mobile network system (at step 210
  • step 210 only if the user subscribes
  • the financial institution's system sends a financial transaction
  • the mobile network system At step 212, on receiving the FTCR, the mobile network
  • system determines whether or not the entered password corresponds to the emergency
  • the mobile network system defines the requested transaction as a temporary abnormal transaction, and sends a notice of temporary
  • the invalid password means a password that
  • the mobile network system searches the current location of the user
  • the user identification data received from the financial institution's system The user identification data received from the financial institution's system.
  • identification data is selected from a group consisting of user's name, resident's
  • the distance between the user and the requested financial transaction location is
  • the mobile network system proceeds to
  • step 220 and records all mobile terminal holders nearby the user and the requested financial transaction location respectively. Then the process proceeds to step 222. If the
  • step 222 to step 222 and sends the confirmation message to the user's mobile terminal.
  • the data of the requested financial transaction location is considered an emergency, the data of the requested financial transaction location is
  • FIG. 4A is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 4A shows the method for guaranteeing safety of the financial
  • the financial institution's system (1) supervises the payment
  • FTT at a credit card member store transmits a financial transaction
  • request including card data read from the user's card and price data to the financial
  • institution's system retrieves the user data by the card data, and confirms that the user
  • the financial institution's system approves the requested transaction and sends a
  • FTT On receiving the transaction approval, FTT prints a bill for
  • the financial institution's system requests the current location of
  • system retrieves the user's mobile terminal data from the user database and searches the
  • the searched location of the user's terminal is
  • step 246 approve the requested transaction. However, if the calculated
  • the confirmation message is sent to the user's mobile terminal at step 264.
  • the mobile network system receives and sends the confirmation data to the financial
  • the financial institution's system determines whether or not the
  • confirmation data is valid. If valid, the requested transaction is approved at step 246. If
  • step 272 on receiving
  • the FFT displays a
  • the confirmation message is sent to the user's mobile terminal immediately before calculating the distance between the mobile
  • the user is requested to input confirmation data
  • the user can be approved by inputting the confirmation data
  • embodiment (2) can be applied to a transaction occurring at some
  • the user will receive the confirmation
  • FIG. 4B is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 4B shows the method for guaranteeing safety of a financial transaction
  • the financial institution's system approves or
  • the pre-steps 300 through 310 for the safe financial transaction that is, steps of
  • determining the user's subscription to the DL service are performed by the financial
  • Step 300 through step 308 are identical to step 240 through step
  • the financial institution's system sends a financial transaction
  • Step 312 through step 316 are identical to step 252 through step 256.
  • Step 312 through step 316 are identical to step 252 through step 256.
  • the mobile network system measures the current location of the user's terminal and
  • the calculated distance is less than the predetermined distance, for example, 10 M or
  • the mobile network system sends a normal transaction
  • step 322 a confirmation message is sent to the user's mobile terminal.
  • the user inputs the confirmation data.
  • network system receives the confirmation data from the user's mobile terminal at step
  • a lost card message for notifying that the user's
  • the financial institution's system determines whether or not the
  • the FFT displays a message for denying the requested cash withdrawal or credit
  • FIG. 5 is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 5 shows the method for guaranteeing safety of a financial transaction
  • the financial institution's system (1) supervises the payment
  • the system sends the confirmation message to the user.
  • the STR is at least one place that
  • the user inserts his card into the FTT and enters the password for
  • the FTT determines whether or not the user
  • step 356 the process proceeds to step 356.
  • the financial institution's system determines whether or not the
  • requested financial transaction location corresponds to an STR.
  • the user has to select an STR.
  • STR for use by wired/wireless communication means such as telephone or Internet, and
  • the selected STR is stored in the user database. Accordingly, the financial institution's system retrieves STR data from the user's information stored in the user database, and
  • the requested transaction is defined as a
  • the financial institution's system sends a confirmation message to the financial institution's system.
  • the user's mobile terminal through the mobile network, and approves the requested
  • the financial institution's system waits until the confirmation data is transmitted from
  • the mobile network system transmits the confirmation
  • the financial institution's system determines whether or not the
  • transaction location is sent to police.
  • FIG. 6A to FIG. 6C are flowcharts of the method for guaranteeing safety of a
  • FIG. 6A to FIG. 6C show the method for guaranteeing safety of a financial
  • the financial institution's system (1) determines
  • the STR is at least one place that the user designated for a financial transaction.
  • step 400 through step 404 are identical to step 350
  • step 406 if the user who requests the financial
  • the financial transaction confirmation request further comprises details
  • the mobile network system searches for the current
  • step 410 If the user's terminal is located within the predetermined distance from the FTT, the process proceeds to step 410. Otherwise, the process proceeds to step 434.
  • predetermined distance is a fixed distance, for example, 10 M or within an error range
  • the mobile network system determines
  • the financial institution's system approves the requested
  • the temporary abnormal transaction notice is sent to the financial institution's
  • step 420 the mobile network system
  • step 422 if the user responds to the confirmation message or inputs the
  • the mobile network system determines whether or not the
  • step 424 the
  • mobile network system sends the abnormal transaction confirmation notice to the financial institution's system, and at step 442 records the location of the user's mobile
  • step 438 From FTT from the mobile network system (step 438 through step 440).
  • the mobile network system determines
  • the temporary abnormal transaction notice is sent to the financial institution's system and
  • step 452 the mobile network system records all mobile
  • the mobile network system sends the confirmation message to the
  • step 456 if the user responds to the confirmation message or inputs
  • the mobile network system determines whether or not the confirmation data
  • step 464 the process proceeds to step 464.
  • the mobile network system sends the abnormal transaction
  • the predetermined allowance limit is released (step 474 through step 476).
  • step 478 the mobile network system (step 478 through step 480).
  • FIG. 7A is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 7A shows the method for guaranteeing safety of a financial
  • step 500 when the user requests a financial transaction such as a cash
  • the financial institution's system determines whether or not the
  • the requested transaction is approved only when the correct password is
  • step 506. the financial institution's system determines whether or not the
  • step 508 If not, the process proceeds to step 510.
  • the financial institution's system determines whether or not the
  • the entered password is the normal password.
  • the normal password the normal password
  • step 510 if the
  • step 512 on receiving the request to transmit the confirmation message, the
  • the predetermined allowance limit is released (step 524 through step 526).
  • the mobile network system records the
  • the mobile network system sends the location of the user's mobile terminal and all mobile terminal holders within the minimum radius from the FTT. Also, the mobile network system sends the location of
  • FIG. 7B is a flowchart of the method for guaranteeing safety of a financial
  • FIG. 7B shows the method for guaranteeing safety of a financial transaction
  • Step 550 through step 554 are identical to step 500 through step 504 in FIG. 7A.
  • the financial institution's system sends a financial transaction
  • system can send the entered password without distinction between the normal password
  • the financial institution's system can send the
  • the entered password is not the normal password.
  • the entered password is not the normal password.
  • the mobile network system determines whether or not the transaction is requested at the
  • the mobile network system retrieves the data of the STR from the
  • step 560 If not, the process proceeds to step 570.
  • the mobile network system determines whether or not the entered
  • the normal password is the normal password.
  • the normal password is the normal password.
  • transaction confirmation notice is sent to the financial institution's system and the
  • step 570 the process proceeds to step 570.
  • step 570 if the entered password is the emergency password or the
  • the mobile network system sends the confirmation
  • step 576 if the user responds to the confirmation message or sends the
  • the mobile network determines whether or not the confirmation data
  • transaction confirmation notice is sent to the financial institution's system.
  • the predetermined allowance limit is released (step 584 through step 586).
  • the mobile network system records the location of the user's mobile terminal and all mobile terminal holders within the
  • the mobile network system sends the location of
  • the present invention is not limited those specific aforementioned

Abstract

The present invention relates to the methods for guaranteeing safe financial transactions when using a wireless network. According to the present invention, a method is provided for a method comprising the following steps: receiving a financial transaction confirmation request (FTCR) transmitted by the financial institution system corresponding to a financial transaction requested by the user; searching a current location of the mobile terminal of the user, which is connected to the mobile network system, by the use of the user identification data; calculating a distance between the location of the mobile terminal of the user and the financial transaction terminal; determining whether or not the requested financial transaction is a normal transaction based on a criterion that is selected from a group consisting of a safe transaction region predetermined by the user, the calculated distance, and the password; transmitting a normal transaction confirmation notice to the financial institution system, if the requested financial transaction is the normal transaction according to the determination; and transmitting a confirmation message to the mobile terminal, if the requested financial transaction is a temporary abnormal transaction according to the determination.

Description

METHOD FOR GUARANTEEING SAFE FINANCIAL TRANSACTIONS
WHEN USING WIRELESS NETWORK
Field of the invention
The present invention relates to methods for guaranteeing safe financial
transactions by using a wireless network. More particularly, the present invention relates
to methods for guaranteeing the security of transactions occurring at an automatic teller
machine ("ATM") or by a credit card reader when using a wireless network.
Background of the invention
Up until recently, adverse incidents regarding financial transactions have
happened frequently, and the number of incidents is on the increase. Specific examples
of these financial incidents are as follows: (1) the secret withdrawal of cash after
finding/stealing/robbing the cash card/credit card from the owner, and (2) actually
threatening the cash/credit cardholder to withdraw cash while at the ATM. These
situations pose not only financial loss but also physical injury to the cardholder. Also,
when the cardholder loses the credit card or is even robbed of it, this can result in a
serious loss that he is not prepared to overcome. Disclosure of the invention
Accordingly, the object of the present invention is to provide the methods for
guaranteeing safe financial transactions, in which the financial transaction is approved
only through a confirmation process with the user who really owns the cash/credit card
at the time of transaction in order to prevent serious financial loss from occurring due to
loss/robbery of cash/credit card. Therefore the user's loss can be less than a
predetermined cash/credit allowance limit when an abnormal financial transaction
occurs.
Also, another object of the present invention is to provide the methods for
guaranteeing safe financial transactions, in which the location of the user who is being
threatened and information about the person(s) threatening the user to complete the
financial transaction are sent to the police automatically, in order to rescue the user from
the emergency situation effectively.
To achieve these aforementioned objects according to a preferred embodiment
of the present invention, a method on a mobile network system coupled to a financial
institution system through a network for approving a user's financial transaction is
provided, said method comprises the following steps: (1) receiving a financial
transaction confirmation request ("FTCR") transmitted by the financial institution
system corresponding to a financial transaction requested by the user, wherein the
FTCR comprises at least one selected from among a group consisting of (a) user identification data, (b) a location of a financial transaction terminal, and (c) a password
inputted by the user; (2) searching for the current location of the mobile terminal of the
user, which is connected to the mobile network system, by the use of the user
identification data; (3) calculating a distance between the location of the mobile
terminal of the user and the financial transaction terminal; (4) determining whether or
not the requested financial transaction is a normal transaction based on a criterion that is
selected from among a group consisting of a safe transaction region predetermined by
the user, the calculated distance, and the password; (5) transmitting a normal transaction
confirmation notice to the financial institution system, if the requested financial
transaction indicates a normal transaction according to a determination; and (6)
transmitting a confirmation message to the mobile terminal, if the requested financial
transaction is a temporary abnormal transaction according to the determination.
Furthermore, the user identification data comprises at least one selected from
among a group consisting of a user's name, a resident's identification/registration
number, and a mobile terminal number. Also the current location of the mobile terminal
of the user is acquired through a location search method that is selected from a group
consisting of GPS, AGPS, AFLT, TOA, TDOA, AOA, Radio Camera, AFLT-AGPS
combined method, and Cell ID method.
The step of determining whether or not the requested financial transaction is a
normal transaction based on the criterion that is selected from among the group consisting of the safe transaction region predetermined by the user, the calculated
distance, and the password, comprises the following steps: (1) determining whether or
not the calculated distance is more than a predetermined distance; (2) defining the
requested financial transaction to be a normal transaction if the calculated distance is
less than the predetermined distance; and (3) defining the requested financial transaction
to be a temporary abnormal transaction if the calculated distance is more than the
predetermined distance. Also, the step of determining whether or not the requested
financial transaction is the normal transaction based on the criterion that is selected
from among the group consisting of the safe transaction region predetermined by the
user, the calculated distance, and the password, comprises the following steps: (1)
determining whether or not the calculated distance is more than a predetermined
distance; (2) determining whether or not the location of the financial transaction
terminal corresponds to the safe transaction region; (3) defining the requested financial
transaction to be the normal transaction if the location of the financial transaction
terminal corresponds to the safe transaction region and the calculated distance is less
than the predetermined distance; and (4) defining the requested financial transaction to
be the temporary abnormal transaction, transmitting a temporary abnormal transaction
notice to the financial transaction institution, and recording the location of the user's
mobile terminal and information of all mobile terminals located within a minimum
radius of the financial transaction terminal, if either of two conditions occurs as follows: the location of the financial transaction terminal does not correspond to the safe
transaction region or the calculated distance is more than the predetermined distance.
Accordingly, the financial institution system performs the following steps: receiving an
approval request for the financial transaction ("ARFT") from the financial transaction
terminal; transmitting an FTCR corresponding to an ARFT to the mobile network
system; determining whether or not a financial transaction confirmation notice in
response to the FTCR received from the mobile network system is the normal
transaction confirmation notice; approving the requested financial transaction if the
financial transaction confirmation notice is the normal transaction confirming notice;
and disapproving the requested financial transaction if the financial transaction
confirmation notice is a temporary abnormal transaction confirmation notice.
Also, the financial institution system further performs the step of putting a
predetermined limit on a cash/credit allowance limit of the requested financial
transaction, if the financial transaction confirmation notice is a temporary abnormal
transaction confirmation notice. Additionally, the financial institution system further
performs the step of suspending an account when the temporary abnormal transaction
occurs, if the financial transaction confirmation notice is the temporary abnormal
transaction confirmation notice.
The step of determining whether or not the requested financial transaction is the
normal transaction based on the criterion that is selected from among the group consisting of the safe transaction region predetermined by the user, the calculated
distance, and the password, comprises the following steps: (1) determining whether or
not the entered password is an emergency password; (2) determining whether or not the
calculated distance is more than a predetermined distance; and (3) defining the
requested financial transaction to be the temporary abnormal transaction, transmitting a
temporary abnormal transaction notice to the financial transaction institution, and
recording the location of the user's mobile terminal and information of all mobile
terminals located within a minimum radius of the financial transaction terminal, if either
of two conditions occurs as follows: the entered password is the emergency password or
the calculated distance is more than the predetermined distance. Further, the financial
institution system performs the following steps: receiving an ARFT including the
password from the financial transaction terminal; determining whether or not the
entered password is a normal password; transmitting an FTCR to the mobile network
system if the entered password is not the normal password; determining whether or not
a financial transaction confirmation notice in response to the FTCR received from the
mobile network system is the normal transaction confirmation notice; releasing the
allowance limit to approve the requested financial transaction if the financial transaction
confirmation notice is the normal transaction confirmation notice; but disapproving the
requested financial transaction if the financial transaction confirmation notice is the
temporary abnormal transaction confirmation notice. The financial institution system further performs the step of putting a
predetermined limit on a cash/credit allowance limit of the requested financial
transaction, if the financial transaction confirmation notice is the temporary abnormal
transaction confirmation notice.
The method further comprises the following steps: determining whether or not
confirmation data transmitted by the user's mobile terminal in response to the
confirmation message is valid; transmitting the normal transaction confirmation notice
to the financial institution system if the confirmation data is valid; and transmitting the
abnormal transaction confirming notice to the financial institution system if the
confirmation data is invalid. The confirmation data, which the user has selected and the
mobile network system oversees, is one selected from a group consisting of number(s),
character (s), and a combination of number(s) and character(s).
According to the another preferred embodiment of the present invention, a
method is provided within a mobile network system coupled to a financial institution
system through a network for approving a user's financial transaction, said method
comprises the following steps: receiving a financial transaction confirmation request
(FTCR) transmitted by the financial institution system corresponding to a financial
transaction requested by the user, wherein the FTCR comprises at least one selected
from a group consisting of user identification data, a location of a financial transaction
terminal, and a password inputted by the user; searching for the current location of the mobile terminal of the user, which is connected to the mobile network system, by the
use of the user identification data; determining whether or not the requested financial
transaction is a normal transaction based on a criterion that is selected from a group
consisting of a safe transaction region predetermined by the user, the searched location,
and the password; transmitting a normal transaction confirmation notice to the financial
institution system if the requested financial transaction is the normal transaction
according to the determination; and transmitting a confirmation message to the mobile
terminal if the requested financial transaction is a temporary abnormal transaction
according to the determination.
According to another preferred embodiment of the present invention, a method
is provided for a mobile network and a financial institution's system for securely
performing a user's financial transaction, said method comprising the following steps:
receiving a financial transaction request of the user according to a financial transaction
from a financial transaction terminal; acquiring a current location of the mobile terminal
of the user according to the financial transaction request; calculating a distance between
the location of the mobile terminal of the user and the financial transaction terminal;
determining whether or not the requested financial transaction is a normal transaction
based on a criterion that is selected from a group consisting of a safe transaction region
predetermined by the user, the calculated distance, and the password; approving the
requested financial transaction if the requested financial transaction is a normal transaction according to the determination; and disapproving the requested financial
transaction if the requested financial transaction is a temporary abnormal transaction
according to the determination.
The step of determining whether or not the requested financial transaction is the
normal transaction based on the criterion that is selected from the group consisting of
the safe transaction region predetermined by the user, the calculated distance, and the
password comprises the following steps: determining whether or not the calculated
distance is more than a predetermined distance; defining the requested financial
transaction as the normal transaction if the calculated distance is less than the
predetermined distance; and defining the requested financial transaction as the
temporary abnormal transaction if the calculated distance is more that the predetermined
distance.
Also, the step of determining whether or not the requested financial transaction
is the normal transaction based on the criterion that is selected from the group
consisting of the safe transaction region predetermined by the user, the calculated
distance, and the password comprises the following steps: determining whether or not
the calculated distance is more than a predetermined distance; determining whether or
not the location of the financial transaction terminal corresponds to the safe transaction
region; defining the requested financial transaction as the normal transaction if the
location of the financial transaction terminal corresponds to the safe transaction region and the calculated distance is less than the predetermined distance; and defining the
requested financial transaction as the temporary abnormal transaction if one of the two
conditions occurs as follows: the location of the financial transaction terminal does not
correspond to the safe transaction region or the calculated distance is more than the
predetermined distance.
Also, the step of determining whether or not the requested financial transaction
is the normal transaction based on the criterion that is selected from the group
consisting of the safe transaction region predetermined by the user, the calculated
distance, and the password comprises the following steps: determining whether or not
the entered password is an emergency password; determining whether or not the
calculated distance is more than a predetermined distance; and defining the requested
financial transaction as the temporary abnormal transaction if one of two conditions
occurs as follows: the entered password is the emergency password or the calculated
distance is more than the predetermined distance.
The method further comprises the following steps: determining whether or not
confirmation data transmitted by the user's mobile terminal as a response to the
confirmation message is valid; approving the requested financial transaction if the
confirmation data is valid; and disapproving the requested financial transaction if the
confirmation data is invalid. The method further comprises the step of transmitting a
record request for recording the location of the user's mobile terminal and information of all mobile terminals located within a minimum radius of the financial transaction
terminal if one of two conditions occurs as follows: the requested financial transaction
is the temporary abnormal transaction or the confirmation data is invalid.
According to the preferred embodiment of the present invention, a method is
provided for a mobile network and a financial institution's system for securely
performing a user's financial transaction, said method comprising the following steps:
receiving a financial transaction request of the user according to a financial transaction
from a financial transaction terminal; acquiring a current location of the mobile terminal
of the user according to the financial transaction request; determining whether or not the
requested financial transaction is a normal transaction based on a criterion that is
selected from a group consisting of a safe transaction region predetermined by the user,
the acquired location, and the password; approving the requested financial transaction if
the requested financial transaction is a normal transaction according to the
determination; and transmitting a confirmation message to the user's mobile terminal if
the requested financial transaction is a temporary abnormal transaction according to the
determination.
Brief description of the drawings
FIG. 1 A through FIG. 1H show various position location technologies.
FIG. 2 is a flowchart of the method for guaranteeing safety of a financial transaction according to the present invention.
FIG. 3A is a flowchart of the method for guaranteeing safety of a financial
transaction according to the first embodiment of the present invention.
FIG. 3B is a flowchart of the method for guaranteeing safety of a financial
transaction according to the second embodiment of the present invention.
FIG. 4A is a flowchart of the method for guaranteeing safety of a financial
transaction according to the third embodiment of the present invention.
FIG. 4B is a flowchart of the method for guaranteeing safety of a financial
transaction according to the fourth embodiment of the present invention.
FIG. 5 is a flowchart of the method for guaranteeing safety of a financial
transaction according to the fifth embodiment of the present invention.
FIG. 6A through FIG. 6C are flowcharts of the method for guaranteeing safety
of a financial transaction according to the sixth embodiment of the present invention.
FIG. 7A is a flowchart of the method for guaranteeing safety of a financial
transaction according to the seventh embodiment of the present invention.
FIG 7B is a flowchart of the method for guaranteeing safety of a financial
transaction according to the eighth embodiment of the present invention.
Hereinafter, the preferred embodiments of the present invention will be
described with the accompanying drawings. Embodiments
The present invention is based on the valid assumption that all mobile
communication service subscribers always carry their mobile terminals, and guarantees
the safety of the subscriber who undertakes a financial transaction (including a cash
withdrawal or a payment with credit card) at some place where an ATM or credit card
terminal (hereinafter, 'F IT: Financial Transaction Terminal') is located. Various
embodiments for guaranteeing the safety of the subscriber are shown in this
specification: (1) a dual password (hereinafter 'DP' whereby one is a normal password
and another is an emergency password), (2) a distance limit (hereinafter 'DL'), (3) a safe
transaction region (hereinafter 'STR'), (4) a safe financial transaction(hereinafter,
'SFT'), and (5) a combination of nos. (l)-(3) above. The main concept of the present
invention is that the mobile network system undertakes second approval of a financial
transaction immediately after first approval of a financial institution's system based on
the location where a financial transaction occurs and the location where the subscriber is
located, and then proceeds with proper action if approval is denied (that is, an
emergency occurs). The term 'financial institution' herein is used to stand for all
financial companies such as a bank, a credit card company, a security corporation, an
insurance company, a loaning company, etc.
Before presenting a detailed description of the embodiments, various position
location technologies applicable to the present invention will be described briefly. FIG. 1A shows AGPS ("Assisted GPS"), FIG. IB shows AFLT ("Advanced Forward Link
Triangulation"), FIG. 1C shows Multipath Fingerprinting, FIG. ID shows AOA ("Angle
of Arrival"), FIG. IE shows TOA ("Time of Arrival"), FIG. IF shows TDOA ("Time
Difference of Arrival"), FIG. IG shows a Hybrid method, and FIG. IH shows a Cell ID
method.
A position location system operated by a mobile communication provider
means a system that locates the subscriber's position by the use of the mobile network
and GPS equipment and provides an additional or valued-added service to the
subscriber. The position location system can be classified into an MS (mobile station)-
based solution, a network-based solution, and a hybrid solution. The MS-based solution
comprises GPS, AGPS, and AFLT; the network-based solution comprises TOA, TDOA,
AOA, and Multipath Fingerprinting; the hybrid solution comprises QUALCOMM, Inc.,
gpsOne™, which combines AFLT and AGPS. Since GPS based solution is well known
to those who skilled in the art, the position location technologies in FIG 1A - IH will be
mainly described.
Since AGPS has been developed to overcome the disadvantages of
conventional GPS such as slow booting time and high power consumption, a BS (base
station) provides partial GPS data to MS.
Also because AFLT produces the subscriber's position by the use of a
difference in the arrival times of the signals transmitted from each BS, then AFLT is MS-based version of TDOA. AFLT solution calculates the subscriber's position as
follows: (1) measures the arrival times of at least three BS, (2) converts the arrival time
into distance, and (3) draws each hyperbola to calculate the subscriber's position. To
accomplish this, synchronization between each BS is required, and the accuracy of a
calculated position depends on the kind of method for measuring arrival time, multi-
path, NLOS transmission, etc,.
Multipath Fingerprinting solution calculates the subscriber's position by the use
of both the direct path components and multipath components of a signal transmitted
from MS. The Multipath Fingerprinting solution calculates the subscriber's position as
follows: (1) BS makes an RF signature of the received signal with a radio camera, and
(2) a position decision module determines the position by comparing the RF signature
with the RF signatures of all BSs stored in a database. The features of Multipath
Fingerprinting are as follows: (1) uses one received signal different from other network-
based solutions, and (2) uses multipaths that are not used in TDOA and AOA causing a
reduction of accuracy. However, a disadvantage is that radio camera is required at all
BSs.
The AOA solution calculates the subscriber's position by the using an incidence
angle of an arrived signal transmitted from MS. According to the AOA solution, at least
two BS measure the incidence angle of an arrived signal transmitted from the MS. To
accomplish this, an antenna array for measuring the incidence angle is required at the BS. In the AOA solution, the accuracy of a calculated position depends on the kind of
method for measuring the incidence angle, multipath, NLOS transmission, multiple
access interference, etc., and the measuring error of the incidence angle increases when
the MS travels further away from the BS.
Since the TDOA solution produces the subscriber's position by the use of the
difference of arrival times of the signals transmitted from MS, the exact time data of
signal transmission at MS is not needed in the TDOA solution. The TDOA solution
calculates the subscriber's position as follows: (1) at least three BSs measure the arrival
time of a signal transmitted by MS, (2) convert the arrival times into distances, and (3)
draw each hyperbola to calculate the subscriber's position. To accomplish this
synchronization between each BS is required, and the accuracy of a calculated position
depends on the kind of method for measuring arrival time, multi-path, NLOS
transmission, etc. Also the measuring error of arrival time increases when the MS
travels further away from the BS.
A hybrid solution, which is a combination of AFLT and AGPS, produces the
subscriber's position mainly by AFTL but complemented by a GPS signal transmitted
by a mobile network.
Because the cell ID solution produces the subscriber's position by searching the
current cell where the subscriber is located, this solution can provide the subscriber's
position by a cell unit with HLR or VLR. However, the accuracy of cell ID is lower than that of the aforementioned solutions.
FIG. 2 is a flowchart of the method for guaranteeing safety of a financial
transaction according to the present invention. The present invention relates to methods
performed by a mobile network system and a financial institution's system in co¬
operation with the mobile network system, and the flowchart in FIG. 2 shows all steps
without separating the operating bodies of each step.
At step 100, when a user who subscribes to the safe financial transaction
service in advance and carries a mobile terminal then requests a financial transaction,
the FTT reads card data from a cash card or credit card and receives a password inputted
by the user.
At step 102, on receiving a financial transaction request ("FTR"), the
confirmation about subscribing to the safe financial transaction service is checked. The
confirmation about subscribing will be checked by searching a user database storing
user information. At this step, it is preferable to check the kind of safe financial
transaction service along with the confirmation about the subscription. If the user does
not subscribe to the service, the requested transaction is approved as a normal
transaction at step 104. If the user subscribed to the service, then the process proceeds to
step 106.
At step 106, the safe financial transaction service predetermined by the user is initiated.
When a user who has subscribed to the DP service, which is composed of a
normal password and an emergency password, requests cash withdrawal on FTT with a
cash card, if the entered password is the normal password, then the requested
transaction is approved as a normal transaction. However, if the entered password is the
emergency password, the requested transaction is defined as a temporary abnormal
transaction and the cash withdrawal limit is reduced to the predetermined allowance
limit.
When a user who subscribed to the DL service requests cash withdrawal or
credit payment on FTT, the transaction is approved or disapproved after finding the
location of the user's mobile terminal and the location of FTT.
When a user who subscribed to an STR service requests cash withdrawal on an
FTT by a cash card, the step to confirm whether the location of the FTT where the user
undertakes the current transaction is an STR predetermined by the user is then
performed. If the current TFF corresponds to the predetermined STR, the request
transaction is approved as a normal transaction. However, if the current TFF does not
correspond to the predetermined STR, the requested transaction is defined as a
temporary abnormal transaction and the cash withdrawal limit is reduced to the
predetermined allowance limit.
At step 108, when the requested transaction is defined as the temporary abnormal transaction, the distance between the location where the financial transaction
is requested and the location of the user's mobile terminal is less than the predetermined
distance is confirmed. The requested financial transaction location can be determined by
the location of FTT. The location of the user's mobile terminal can be determined by
one of aforementioned solutions. If the user's mobile terminal is located within the
predetermined distance from the requested financial transaction location, (1) the
requested transaction will be approved as a normal transaction (step 110), and (2) more
preferably a confirmation message will be sent to the user's mobile terminal (step 112).
The reason to send a confirmation message is that even though the user is located near
the requested financial transaction location, someone may still threaten the user forcing
him to make the transaction. Also, it is possible that the requested financial transaction
location and the location of the user's mobile terminal may be in the same cell when a
cell ID solution having a large measuring error is used, so it is preferable to perform the
confirmation step. Thus, if the distance between the requested financial transaction
location and the user's location is greater than the predetermined distance, or according
to the selection predetermined by the user, the process proceeds to step 112.
At step 112, the confirmation message is sent to the user's mobile terminal. The
confirmation message includes the description about the abnormal financial transaction,
and preferably the message is a kind of bi-directional message such as ARS voice call, a
return message, SMS callback or URL push message. Thus, on receiving the confirmation message, the user can send the confirmation data (for example, "Is it
possible to call the user?" or "Does the user have to input the emergency confirmation
password?"). According to the embodiment, a proper action can be made when the user
does not receive the confirmation message.
At step 114, when confirmation data is transmitted from the user's mobile
terminal, confirmation occurs that the received confirmation data corresponds to the
emergency confirmation password predetermined by the user. The emergency
confirmation password, which is predetermined by the user to receive approval when
the user himself has breached the safe financial transaction service requirements, is
composed of number(s) and character(s) or any combination of number(s) and
character(s). According to the embodiment, an emergency results when the user does
not receive the confirmation message or does not input the confirmation data after
receipt of the confirmation message, so proper action must be undertaken. If the
received emergency confirmation password is valid, then the process proceeds to step
116 and the requested transaction is approved as a normal transaction. Otherwise, the
process proceeds to step 118.
At step 118, the location of the user's mobile terminal and information of all
mobile terminals located within a minimum radius of FTT are recorded. The minimum
radius is (1) the radius of a cell in a cell ID solution, or (2) the radius of an error range
in another position location solution. In the cell ID solution, plural mobile terminals included within the same cell are recorded by the use of HLR or VLR.
At step 120 if the user does not input valid confirmation data, the system
regards the requested transaction to originate from fraudulent use of a lost card or illegal
forced use of the card during theft/robbery of the card owner, and thereafter suspends
further monetary withdrawal while notifying the police of the situation.
Hereinafter, the embodiments of each of the operating bodies will be described
in detail.
FIG. 3A is a flowchart of the method for guaranteeing safety of a financial
transaction according to the first embodiment of the present invention. More particularly,
FIG. 3A shows the method for guaranteeing safety of a financial transaction by using a
DP, whereby the main steps are performed by the financial institution's system.
In the first embodiment, the financial institution's system (1) oversees the
normal password and the emergency password, and (2) calculates the distance between
FTT and the user's mobile terminal, whereas the mobile network system (1) measures
the location of the user's mobile terminal, (2) sends the confirmation message to the
user, and (3) records all subscribers who are located within the minimum radius from
FTT when an emergency situation occurs.
At step 150, the user inserts his card to FTT and enters the password for the
financial transaction. At step 152, a determination is made whether or not the entered password corresponds to the normal password. If the normal password is indicated, at
step 154 approval is given for a normal transaction and the user can draw out the
requested amount of money. However, if the entered password is not the normal
password, then the process proceeds to step 156. If the step 152 determines not only
whether or not the entered password is the normal password but also whether or not the
entered password corresponds to the emergency password, the process can proceed
directly to step 160.
At step 156, if the entered password is not the normal password, the system
confirms that the user subscribed to the DP service. According to the confirmation, if
the user subscribed to the DP service, then the entered password corresponds to the
emergency password. If the entered password corresponds to the emergency password,
the system defines the requested transaction as a temporary abnormal transaction and
proceeds to step 160. If the user does not subscribe to the DP or the entered password
does not correspond to the emergency password even though the user had subscribed to
the DP service, then the system proceeds to step 158 to invalidate the requested
transaction.
At step 160, if the requested transaction is defined as the temporary abnormal
transaction, then the financial institution's system requests the current location of the
user along with the user identification data, and at step 162 permits the cash withdrawal
within the predetermined allowance limit. The user can determine the allowance limit, however, preferably the financial institution will determine the allowance limit. Also,
preferably the monetary balance displayed on FTT or printed on the receipt is the
predetermined allowance limit for preparing the financial transaction performed during
a real situation. If the user cannot withdraw the requested amount of cash even though
there is a remaining balance, the situation could become quite dangerous to the user if
he has been threatened for not complying.
At step 164, if the mobile network system receives the confirmation request of
the user's location, then the mobile network system searches the current location of the
user's mobile terminal by the use of the user identification data at step 166. The search
of the current location is performed by one of the aforementioned position location
solutions. At step 168, the current location of the user is sent to the financial
institution's system.
At step 170, on receiving the location of the user, the distance between the
client and the requested financial transaction location (the location of the FTT) is
calculated. If the calculated distance is less than the predetermined distance, for
example, 10 M or within an error range, then the financial institution's system proceeds
to step 172 and requests the mobile network system to record all mobile terminal
holders. At step 174, on receiving the record request, the mobile network system
records the location of the user and all mobile terminal holders within the minimum
radius from FTT. If the calculated distance is greater than the predetermined distance, the system proceeds to step 176.
At step 176, the financial institution's system sends a confirmation message to
the user's mobile terminal. The confirmation message includes the description about the
abnormal transaction, and on receiving the confirmation message, the user can send
confirmation data via SMS, ARS or Internet.
At step 178, if the confirmation data transmitted by the user is valid, the
financial institution's system proceeds to step 180 to release the allowance limit and pay
the requested amount of cash to the user. However, if the confirmation data transmitted
by the user is invalid or the user does not respond to the confirmation message, the
requested transaction is considered an emergency caused by the abnormal transaction.
At step 182, if the requested transaction is considered an emergency, further
withdrawal is prohibited and data about the requested financial transaction location is
sent to the police. Also, if the emergency occurs at an open 24-hour branch where its
door can be locked by remote control, the door of the branch will be locked
automatically.
The aforementioned embodiment can change variously as follows: (1) when the
user requests a financial transaction, the confirmation message is sent to the user's
mobile terminal immediately before calculating the distance between the mobile
terminal and FTT, and the financial transaction is approved when the confirmation data
inputted by the user is valid, (2) although the distance between the mobile terminal and FTT corresponds to the normal transaction, the confirmation message is sent to the
user's mobile terminal to receive confirmation data from the user.
In the embodiments (1) and (2), the user is requested to input confirmation data
such as a password when the user requests a financial transaction. When a normal
transaction occurs, the user can be approved by inputting the confirmation data;
however, when an abnormal transaction such as loss of the credit card occurs, the user
can assume that someone may try to purchase something at any time, and thus prevent
this illegal use merely by inputting the emergency password or not inputting the
confirmation data. Therefore even without reporting the loss of the credit card, the user
can prevent fraudulent use by an unauthorized person.
FIG. 3B is a flowchart of the method for guaranteeing safety of a financial
transaction according to the second embodiment of the present invention. More
particularly, FIG. 3B shows the method for guaranteeing safety of a financial transaction
by using a DP, whereby the main steps are performed by the mobile network system.
In the second embodiment, the financial institution's system oversees the
normal password and the emergency password, while the mobile network system (1)
calculates the distance between FTT and the user's mobile terminal, (2) sends the
confirmation message to the user, (3) determines whether or not an emergency occurs
and notes the occurrence of the emergency, and (4) records all subscribers who are located within the minimum radius from FTT when the emergency occurs. Hereinafter,
the same description applicable to FIG. 3B but already described in FIG 3A will be
omitted so only the differences will be mainly described.
The pre-steps 200 to 210 for the safe financial transaction such as determination
of the normal password and limitation of cash withdrawal allowance limit are performed
by the financial institution's system. Step 200 to step 208 are identical to step 150 to
step 158, however, there are some differences at step 202 or step 206; if another
password that is not a normal password is entered, the financial institution's system
proceeds to step 210 to send the entered password to the mobile network system (at step
202) or the financial institution's system proceeds to step 210 only if the user subscribes
to the DP service (step 206).
At step 210, the financial institution's system sends a financial transaction
confirmation request (FTCR) including the location of FTT and the entered password to
the mobile network system. The steps 212 to 228 for a safe financial transaction such as
confirmation of the entered password and the distance calculation are performed by the
mobile network system. At step 212, on receiving the FTCR, the mobile network
system determines whether or not the entered password corresponds to the emergency
password at step 214.
At step 216, if the entered password corresponds to the emergency password
according to the determination, the mobile network system defines the requested transaction as a temporary abnormal transaction, and sends a notice of temporary
abnormal transaction to the financial institution's system. At step 230, on receiving the
notice of temporary abnormal transaction, the financial institution's system limits the
allowance limit to the predetermined limit and waits until the mobile network system
sends a financial transaction confirmation notice.
If the entered password is an invalid password, an invalid password notice is
sent to the financial institution's system. The invalid password means a password that
the user inputs by mistake and corresponds to neither the normal password nor
emergency password. On receiving the invalid password notice, the financial
institution's system invalidates the requested transaction. According to the result of
invalidation, a special alert such as "Password is invalid. Please input password again."
can be displayed on the screen of FTT.
At step 218, the mobile network system searches the current location of the user
by the user identification data received from the financial institution's system. The user
identification data is selected from a group consisting of user's name, resident's
registration number, ID, and phone number. When the current location of the user is
found, the distance between the user and the requested financial transaction location is
calculated. If the calculated distance is less than the predetermined distance, for
example, 10 M or within an error range, then the mobile network system proceeds to
step 220 and records all mobile terminal holders nearby the user and the requested financial transaction location respectively. Then the process proceeds to step 222. If the
calculated distance is greater than the predetermined distance, then the process proceeds
to step 222 and sends the confirmation message to the user's mobile terminal.
At step 228, if the confirmation data transmitted from the user's mobile
terminal is valid, a normal transaction confirmation notice is sent to the financial
institution's system. According to this notice, the financial institution's system releases
the allowance limit and pays the requested amount of cash to the user at step 232.
However, if the confirmation data transmitted by the user is invalid or the user does not
respond to the confirmation message, the requested transaction is considered an
emergency caused by the abnormal transaction. At step 226, if the requested transaction
is considered an emergency, the data of the requested financial transaction location is
sent to the police.
FIG. 4A is a flowchart of the method for guaranteeing safety of a financial
transaction according to the third embodiment of the present invention. More
particularly, FIG. 4A shows the method for guaranteeing safety of the financial
transaction by using a distance limitation, in which the main steps are performed by the
financial institution's system.
In the third embodiment, the financial institution's system (1) supervises the
distance limitation and the confirmation data that are both predetermined by the user, (2) calculates the distance between FTT and the user's mobile terminal, and (3)
approves or disapproves the requested transaction, whereas the mobile network system
(1) measures the location of the user's mobile terminal, and (2) sends the confirmation
message to the user.
At step 240, FTT at a credit card member store transmits a financial transaction
request including card data read from the user's card and price data to the financial
institution's system.
At step 242, on receiving the financial transaction request, the financial
institution's system retrieves the user data by the card data, and confirms that the user
subscribed to the DL service. If the user did not subscribe to the DL service, at step 246
the financial institution's system approves the requested transaction and sends a
transaction approval to FTT. On receiving the transaction approval, FTT prints a bill for
a credit purchase. If the requested transaction is for cash withdrawal, the requested
amount of cash is paid to the user. If the user subscribed to the DL service, the process
proceeds to step 250.
At step 250, the financial institution's system requests the current location of
the user along with the user identification data. When the mobile network system
receives the request for the current location of the user at step 252, the mobile network
system retrieves the user's mobile terminal data from the user database and searches the
current location of the user's mobile terminal by one of the aforementioned position location solutions at step 254. At step 256, the searched location of the user's terminal is
sent to the financial institution's system.
At step 258, on receiving the location of the user, the distance between the
client and the requested financial transaction location (the location of the FTT) is
calculated at step 260. If the calculated distance is less than the predetermined distance,
for example, 10 M or within an error range, then the financial institution's system
proceeds to step 246 to approve the requested transaction. However, if the calculated
distance is greater than the predetermined distance, the process proceeds to step 262.
At step 262, when the financial institution's system requests a confirmation
message, the confirmation message is sent to the user's mobile terminal at step 264.
When the user who receives the confirmation message transmits the confirmation data,
the mobile network system receives and sends the confirmation data to the financial
institution's system at step 266.
At step 268, the financial institution's system determines whether or not the
confirmation data is valid. If valid, the requested transaction is approved at step 246. If
invalid, the requested transaction is disapproved at step 270. At step 272, on receiving
transaction disapproval from the financial institution's system, the FFT displays a
message for denying the requested cash withdrawal or credit purchase.
The aforementioned embodiment can be changed variously as follows: (1)
when the user requests a financial transaction, the confirmation message is sent to the user's mobile terminal immediately before calculating the distance between the mobile
terminal and FTT, and the financial transaction is approved when the confirmation data
inputted by the user is valid, and (2) although the distance between the mobile terminal
and FTT corresponds to the normal transaction, the confirmation message is sent to the
user's mobile terminal to receive confirmation data from the user.
In the embodiments (1) and (2), the user is requested to input confirmation data
such as a password when the user requests a financial transaction. When a normal
transaction occurs, the user can be approved by inputting the confirmation data;
however, when an abnormal transaction such as loss of the credit card occurs, the user
can assume that someone may try to purchase something at any time, and thus prevent
this illegal use merely by inputting the emergency password or not inputting the
confirmation data. Therefore even without reporting the loss of the credit card, the user
can prevent fraudulent use by an unauthorized person.
In particular, embodiment (2) can be applied to a transaction occurring at some
places, for example, restaurant or gas station, where the user cannot easily scrutinize the
clerk's operation on the FTT. In more detail, even though the requested transaction may
be approved because the distance is less than the predetermined distance, the transaction
could be double charged due to a simple error of the clerk or even intentional
overcharged by an unscrupulous clerk with malicious intent. As a result, the card owner
may not realize the overcharge to his account until he receives his periodic statement to settle the account. Thereafter, a complicated process is usually required in order for the
user to receive proper crediting of his account to his complete satisfaction. However,
according to the aforementioned embodiment, the user will receive the confirmation
message per the number of requests and immediately realize an erroneous or
unauthorized overcharge has occurred.
The aforementioned variations can be commonly applied to the fourth to eighth
embodiments. Accordingly, the same description to each embodiment will be omitted.
FIG. 4B is a flowchart of the method for guaranteeing safety of a financial
transaction according to the fourth embodiment of the present invention. More
particularly, FIG. 4B shows the method for guaranteeing safety of a financial transaction
by using a distance limit, whereby the main steps are performed by the mobile network
system.
In the fourth embodiment, the financial institution's system approves or
disapproves the requested transaction, and the mobile network system (1) supervises the
distance limit and the confirmation data that are both predetermined by the user, (2)
measures the location of the user's mobile terminal, (3) calculates the distance between
FTT and the user's mobile terminal, (4) sends the confirmation message to the user, and
(5) records selectively all mobile terminal holders who are located nearby the FTT.
Hereinafter, the same description already described in FIG 4A will be omitted with only the differences mainly being described.
The pre-steps 300 through 310 for the safe financial transaction, that is, steps of
determining the user's subscription to the DL service are performed by the financial
institution's system. Step 300 through step 308 are identical to step 240 through step
248, however, there are some differences at step 310; the financial transaction
confirmation request includes the location of the FTT where the financial transaction is
requested.
At step 310, the financial institution's system sends a financial transaction
confirmation request (FTCR) including the user identification data and the location of
the FTT to the mobile network system. The steps 312 through 328 for a safe financial
transaction such as distance calculation and user approval are performed by the mobile
network system.
Step 312 through step 316 are identical to step 252 through step 256. At step
318, the mobile network system measures the current location of the user's terminal and
calculates the distance between the user's mobile terminal and the FTT, and also
determines whether or not the calculated distance is less than the predetermined distance.
If the calculated distance is less than the predetermined distance, for example, 10 M or
within an error range, the mobile network system sends a normal transaction
confirmation notice to the financial institution's system. Otherwise, the process
proceeds to step 322. At step 322, a confirmation message is sent to the user's mobile terminal. On
receiving the confirmation message, the user inputs the confirmation data. The mobile
network system receives the confirmation data from the user's mobile terminal at step
324, and determines whether or not the received confirmation data is valid. If valid, the
normal transaction confirmation notice is sent to the financial institution's system.
Otherwise, an abnormal transaction confirmation notice is sent to the financial
institution's system. Further at step 328, a lost card message for notifying that the user's
card is lost and someone has fraudulently tried to use the lost card is sent to the user's
mobile terminal.
At step 330, on receiving the transaction confirmation notice from the mobile
network system, the financial institution's system determines whether or not the
received transaction confirmation notice is the normal transaction confirmation notice.
If the normal transaction confirmation notice is received, the requested transaction is
approved at step 306. Otherwise, the requested transaction is disapproved at step 334.
At step 336, on receiving transaction disapproval from the financial institution's system,
the FFT displays a message for denying the requested cash withdrawal or credit
purchase.
FIG. 5 is a flowchart of the method for guaranteeing safety of a financial
transaction according to the fifth embodiment of the present invention. More particularly, FIG. 5 shows the method for guaranteeing safety of a financial transaction
by using an STR, whereby the main steps are performed by the financial institution's
system.
In the fifth embodiment, the financial institution's system (1) supervises the
STR and the confirmation data that are both predetermined by the user, (2) determines
whether or not the requested financial transaction location corresponds to the STR, and
(3) approves or disapproves the requested transaction, and then the mobile network
system sends the confirmation message to the user. The STR is at least one place that
the user designated for a financial transaction. The user who subscribed to the service
can do any kind of financial transactions such as cash withdrawal at the STR, however,
may be limited when conducting financial transaction at other places.
At step 350, the user inserts his card into the FTT and enters the password for
the financial transaction, and then the FTT determines whether or not the user
subscribed to the STR service. If the user did not subscribe to the service, the requested
transaction is approved only when the correct password is inputted. If the user
subscribed to the service, the process proceeds to step 356.
At step 356, the financial institution's system determines whether or not the
requested financial transaction location corresponds to an STR. The user has to select an
STR for use by wired/wireless communication means such as telephone or Internet, and
the selected STR is stored in the user database. Accordingly, the financial institution's system retrieves STR data from the user's information stored in the user database, and
determines whether or not the requested financial transaction location corresponds to
the STR. If the requested financial transaction location corresponds to the STR, then the
requested transaction is approved only when the correct password is inputted at step 358.
At step 382, if the requested transaction is approved, the particulars of the financial
transaction are sent to the user's mobile terminal. If the requested financial transaction
location does not correspond to the STR, then the requested transaction is defined as a
temporary abnormal transaction and the process proceeds to step 360.
At step 360, the financial institution's system sends a confirmation message to
the user's mobile terminal through the mobile network, and approves the requested
transaction within the predetermined allowance limit. In particular, if the requested
transaction is a cash withdrawal, the cash withdrawal cannot exceed the allowance limit.
The financial institution's system waits until the confirmation data is transmitted from
the user's terminal. At step 362, the mobile network system transmits the confirmation
message to the user's mobile terminal and sends the confirmation data received from the
user's terminal to the financial institution's system at step 364.
At step 368, when the user responses to the confirmation message or sends the
confirmation data, the financial institution's system determines whether or not the
received confirmation data is valid. If valid, the requested transaction is approved as a
normal transaction to bypass the predetermined allowance limit and permit any level of cash withdrawal according to the user's immediate request. If invalid, the requested
transaction is disapproved as an abnormal transaction setting up a further transaction
request for disapproval.
At step 372, when the user requests a bypass of the predetermined allowance
limit via phone call or in person visit after inputting the invalid confirmation data and
no further transaction has been requested, then the predetermined allowance limit is
released (step 374 through step 376). However, if another transaction request at the
same place occurs, then an emergency is indicated so the data of the requested financial
transaction location is sent to police.
FIG. 6A to FIG. 6C are flowcharts of the method for guaranteeing safety of a
financial transaction according to the sixth embodiment of the present invention. More
particularly, FIG. 6A to FIG. 6C show the method for guaranteeing safety of a financial
transaction by using an STR, whereby the main steps are performed by the mobile
network system.
In the sixth embodiment, the financial institution's system (1) determines
whether or not the user subscribed to the service, and (2) approves or disapproves the
requested transaction, whereas the mobile network system (1) supervises the STR and
the confirmation data that are both predetermined by the user, (2) determines whether or
not the requested financial transaction location corresponds to the STR, and (3) sends the confirmation message to the user and receives the confirmation data from the user.
The STR is at least one place that the user designated for a financial transaction. The
user who subscribed to the service can conduct any kind of financial transactions such
as cash withdrawal at the STR, however, he may be limited when doing financial
transactions at other places.
In the sixth embodiment, the main steps, which were performed by the financial
institution's system, are performed by the mobile network system so it is also an
important step to calculate the distance between the requested financial transaction
location and the user's mobile terminal. However, in another embodiment, the step of
calculating the distance can be omitted.
Referring to FIG. 6A, step 400 through step 404 are identical to step 350
through step 534 in FIG. 5. At step 406, if the user who requests the financial
transaction subscribed to the service, a financial transaction confirmation request
including the user identification data and the location of the FTT is sent to the mobile
network system. The financial transaction confirmation request further comprises details
of the financial transaction.
At step 408, on receiving the financial transaction confirmation request from
the financial institution's system, the mobile network system searches for the current
location of the user's mobile terminal by one of the aforementioned position location
solutions. If the user's terminal is located within the predetermined distance from the FTT, the process proceeds to step 410. Otherwise, the process proceeds to step 434. The
predetermined distance is a fixed distance, for example, 10 M or within an error range
of the position location solutions.
Referring to FIG. 6B, at step 410, the mobile network system determines
whether or not the location of the FTT corresponds to the STR. If the FTT is located at
the STR, a normal transaction confirmation notice is sent to the financial institution's
system, and at step 414 the particulars of the financial transaction are sent to the user's
mobile terminal. At step 416, on receiving the normal transaction notice from the
mobile network system, the financial institution's system approves the requested
transaction at step 418.
If the financial transaction is requested from the FTT at some place that is not
an STR, the temporary abnormal transaction notice is sent to the financial institution's
system and the process proceeds to step 420. At step 420, the mobile network system
sends a confirmation message to the user's mobile terminal and awaits the confirmation
data in response to the message.
At step 422, if the user responds to the confirmation message or inputs the
confirmation data, the mobile network system determines whether or not the
confirmation data is valid. If valid, the normal transaction notice is sent to the financial
institution's system at 412. If not, the process proceeds to step 424. At step 424, the
mobile network system sends the abnormal transaction confirmation notice to the financial institution's system, and at step 442 records the location of the user's mobile
terminal and all the mobile terminal holders within the minimum radius from the FTT.
At step 426, on receiving the abnormal transaction confirmation notice
indicating that the transaction is requested at some place that is not an STR, the
financial institution's system only permits a cash withdrawal within the predetermined
allowance limit. Thereafter, the financial institution's system waits until the user inputs
the confirmation data to verify a normal transaction. At step 428, on receiving the
abnormal transaction confirmation notice from the mobile network, the financial
institution's system prohibits further cash withdrawal.
At step 432, when the user requests a bypass of the predetermined allowance
limit via phone call or personal visit if further transaction is not requested at the same
place, then the predetermined allowance limit is released (step 434 through step 436).
On the contrary, if a further transaction is requested at the same place, the requested
transaction is not approved and then an emergency is indicated. The financial
institution's system sends the data of the requested financial transaction location to the
police and requests recording of all mobile terminal holders within the minimum radius
from FTT from the mobile network system (step 438 through step 440).
Referring to FIG. 6C, at step 450, the mobile network system determines
whether or not the location of the FTT corresponds to the predetermined STR. If the
financial transaction is requested from an FTT at some place that is not an STR, the temporary abnormal transaction notice is sent to the financial institution's system and
the process proceeds to step 454. On receiving the temporary abnormal transaction
notice indicating that the transaction is requested at the predetermined STR but the user
is not located at that place, the financial institution's system permits a cash withdrawal
within the predetermined allowance limit at step 466 and waits until a financial
transaction confirmation notice is received from the mobile network system. If the
financial transaction is requested from the FTT at the predetermined STR, the process
proceeds to step 452. At step 452, the mobile network system records all mobile
terminal holders within the minimum radius from the FTT and proceeds to step 454.
At step 454, the mobile network system sends the confirmation message to the
user's mobile terminal and waits until the confirmation data is received from the user's
mobile terminal. At step 456, if the user responds to the confirmation message or inputs
the confirmation data, the mobile network system determines whether or not the
confirmation data is valid. If valid, the normal transaction confirmation notice is sent to
the financial institution's system. If not, the process proceeds to step 464.
At step 460, on receiving the normal transaction confirmation notice, the
financial institution's system releases the predetermined allowance limit and approves
the requested transaction at step 462.
At step 464, the mobile network system sends the abnormal transaction
confirmation notice to the financial institution's system, and records the location of the user's mobile terminal and all mobile terminal holders within the minimum radius from
the FTT at step 482.
At step 468, on receiving the abnormal transaction confirmation notice
indicating that the transaction is requested from another place that is not an STR and the
user is not located at the requested transaction location, the financial institution's system
prohibits further cash withdrawal at step 470.
At step 472, when the user requests to bypass the predetermined allowance
limit via a phone call or personal visit after inputting the invalid confirmation data and
no further transaction is requested after the prohibition against a further cash withdrawal,
the predetermined allowance limit is released (step 474 through step 476). On the
contrary, if a further transaction is requested at the same place, the requested transaction
is not approved and then an emergency is indicated. The financial institution's system
sends the data of the requested financial transaction location to the police and requests
recording of all mobile terminal holders within the minimum radius from FTT from the
mobile network system (step 478 through step 480).
FIG. 7A is a flowchart of the method for guaranteeing safety of a financial
transaction according to the seventh embodiment of the present invention. More
particularly, FIG. 7A shows the method for guaranteeing safety of a financial
transaction by using DP and STR, whereby the main steps are performed by the financial institution's system.
At step 500, when the user requests a financial transaction such as a cash
withdrawal on the FTT, the financial institution's system determines whether or not the
user subscribed to the SFT service at step 502. If the user did not subscribe to the SFT
service, the requested transaction is approved only when the correct password is
inputted at step 504. If the user subscribed to the SFT service, the process proceeds to
step 506. At step 506, the financial institution's system determines whether or not the
financial transaction is requested at the predetermined STR. The financial institution's
system retrieves the data of the STR from the user database and determines whether or
not the current location of the requested transaction corresponds to one of the
predetermined STRs. If the location of the requested transaction corresponds to the STR,
the process proceeds to step 508. If not, the process proceeds to step 510.
At step 508, the financial institution's system determines whether or not the
entered password is the normal password. Regarding the normal password, the
requested transaction is approved and the requested amount of cash is paid to the user.
Regarding the emergency password, the process proceeds to step 510. At step 510, if the
entered password is the emergency password, the financial institution's system approves
the requested transaction only within the predetermined allowance limit and requests the
mobile network system to transmit the confirmation message to the user's mobile
terminal. At step 512, on receiving the request to transmit the confirmation message, the
mobile network system sends the confirmation message to the user's mobile terminal
and sends the confirmation data to the financial institution's system when the user
responds to the confirmation message or sends the confirmation data at step 514.
At step 516, on receiving the confirmation data, the financial institution's
system determines whether or not the confirmation data is valid. If valid, the financial
institution's system releases the allowance limit and permits the cash withdrawal in any
amount per the user's request at step 518. If invalid, the financial institution's system
prohibits further cash withdrawal.
At step 552, when the user requests to bypass the predetermined allowance
limit via phone call or personal visit after inputting the invalid confirmation data and no
further transaction has been requested after the prohibition against further cash
withdrawal, the predetermined allowance limit is released (step 524 through step 526).
On the contrary, if further transaction is requested at the same place, the requested
transaction is not approved and then an emergency is indicated. The financial
institution's system sends the data of the requested financial transaction location to the
police and requests the mobile network system to record all mobile terminal holders
within the minimum radius from the FTT (step 528 through step 530).
At step 452, on receiving the request, the mobile network system records the
location of the user's mobile terminal and all mobile terminal holders within the minimum radius from the FTT. Also, the mobile network system sends the location of
the user and/or the location of the FTT to the police.
FIG. 7B is a flowchart of the method for guaranteeing safety of a financial
transaction according to the seventh embodiment of the present invention. More
particularly, FIG. 7B shows the method for guaranteeing safety of a financial transaction
by using DP and STR, whereby the main steps are performed by the mobile network
system.
Step 550 through step 554 are identical to step 500 through step 504 in FIG. 7A.
At step 556, the financial institution's system sends a financial transaction
confirmation request (FTCR) including the user identification data, the location of the
FTT, and the entered password to the mobile network system. The financial institution's
system can send the entered password without distinction between the normal password
and the emergency password. Also, the financial institution's system can send the
password when the entered password is not the normal password. Preferably, the
financial institution's system sends the location of the FTT and the user identification
data with regard to the normal password, and waits until the normal transaction
confirmation notice is received. If the financial institution's system receives the normal
transaction confirmation notice, the requested transaction is approved.
At step 558, on receiving the financial transaction confirmation request, the mobile network system determines whether or not the transaction is requested at the
predetermined STR. The mobile network system retrieves the data of the STR from the
user database and determines whether or not the current location of the requested
transaction corresponds to one of the predetermined STRs. If the location of the
requested transaction corresponds to the predetermined STR, the process proceeds to
step 560. If not, the process proceeds to step 570.
At step 560, the mobile network system determines whether or not the entered
password is the normal password. Regarding the normal password, the normal
transaction confirmation notice is sent to the financial institution's system and the
particulars of the financial transaction are sent to the user's mobile terminal. At step 566,
on receiving the normal transaction confirmation notice, the financial institution's
system approves the requested transaction and pays the requested amount of cash to the
user. Regarding the emergency password, the process proceeds to step 570.
At step 570, if the entered password is the emergency password or the
transaction is requested at some place that is not the STR, the mobile network system
sends the temporary abnormal transaction confirmation notice to the financial
institution's system. At step 572, the mobile network system sends the confirmation
message to the user's mobile terminal and receives the confirmation data when the user
responds to the confirmation message or inputs confirmation data. At the same time, the
financial institution's system permits the requested transaction within the predetermined allowance limit.
At step 576, if the user responds to the confirmation message or sends the
confirmation data, the mobile network determines whether or not the confirmation data
is valid. If valid confirmation data, the normal transaction confirmation notice is sent to
the financial institution's system. On receiving the normal transaction confirmation
notice, the financial institution's system releases the predetermined allowance limit and
permits the requested transaction at step 578. If invalid confirmation data, the abnormal
transaction confirmation notice is sent to the financial institution's system. On receiving
the abnormal transaction confirmation notice, the financial institution's system prohibits
any further financial transaction at step 580.
At step 582, when the user requests to bypass the predetermined allowance
limit via phone call or personal visit after inputting the invalid confirmation data and no
further transaction has been requested after the prohibition against further cash
withdrawal, the predetermined allowance limit is released (step 584 through step 586).
On the contrary, if further transaction is requested at the same place, the requested
transaction is not approved and then an emergency is indicated. The financial
institution's system sends the data of the requested financial transaction location to the
police and requests the mobile network system to record all mobile terminal holders
within the minimum radius from the FTT (step 588 through step 590).
At step 452, on receiving the request, the mobile network system records the location of the user's mobile terminal and all mobile terminal holders within the
minimum radius from the FTT. Also, the mobile network system sends the location of
the user and/or the location of the FTT to the police.
Although the present invention has been described with the foregoing
embodiments, the present invention is not limited those specific aforementioned
embodiments. Rather various modifications and alternations can be made by those who
are skilled in the art to fall within the spirit and scope of the invention. Furthermore, the
spirit and scope of the present invention will only be determined by the claims.
Industrial applicability
As described above, according to the present invention, in order to prevent
serious monetary damage due to a loss/robbery of the owner's cash/credit card from
occurring, a financial transaction is approved only through the confirmation process
with the user who actually has the cash/credit card at the time of transaction. Therefore
the legal user's loss cannot exceed a predetermined allowance limit if an abnormal
financial transaction has occurred. Also, the locations of the legal user who is threatened
and someone who threatens the user to do the financial transaction are automatically
sent to police, so the user can be rescued from the emergency easily.

Claims

Claims
1. A method for a mobile network system coupled to a financial institution system
through a network for approving a user's financial transaction, said method comprising
the steps of:
receiving a financial transaction confirmation request (FTCR) transmitted by
the financial institution system corresponding to a financial transaction requested by the
user, wherein the FTCR comprises at least one selected from a group consisting of
user identification data, a location of a financial transaction terminal, and a password
inputted by the user;
searching a current location of the mobile terminal of the user, which is
connected to the mobile network system, by the use of the user identification data;
calculating a distance between the location of the mobile terminal of the user
and the financial transaction terminal;
determining whether or not the requested financial transaction is a normal
transaction based on a criterion that is selected from a group consisting of a safe
transaction region predetermined by the user, the calculated distance, and the password;
transmitting a normal transaction confirmation notice to the financial institution
system if the requested financial transaction is the normal transaction according to the
determination; and
transmitting a confirmation message to the mobile terminal if the requested financial transaction is a temporary abnormal transaction according to the determination.
2. The method as stated in claim 1, wherein the user identification data comprises at
least one selected from a group consisting of a user's name, a resident registration
number, and a mobile terminal number.
3. The method as stated in claim 1, wherein the current location of the mobile terminal
of the user is acquired through a location search method that is selected from a group
consisting of GPS, AGPS, AFLT, TOA, TDOA, AOA, Radio Camera, AFLT-AGPS
combined method, and Cell ID method.
4. The method as stated in claim 1, wherein the step of determining whether or not the
requested financial transaction is the normal transaction based on the criterion that is
selected from the group consisting of the safe transaction region predetermined by the
user, the calculated distance and the password, comprises the steps of:
determining whether or not the calculated distance is more than a
predetermined distance;
defining the requested financial transaction as the normal transaction if the
calculated distance is less than the predetermined distance; and
defining the requested financial transaction as the temporary abnormal transaction if the calculated distance is more that the predetermined distance.
5. The method as stated in claim 1, wherein the step of determining whether or not the
requested financial transaction is the normal transaction based on the criterion that is
selected from the group consisting of the safe transaction region predetermined by the
user, the calculated distance and the password, comprises the steps of:
determining whether or not the calculated distance is more than a
predetermined distance;
determining whether or not the location of the financial transaction terminal
corresponds to the safe transaction region;
defining the requested financial transaction as the normal transaction if the
location of the financial transaction terminal corresponds to the safe transaction region
and the calculated distance is less than the predetermined distance; and
defining the requested financial transaction as the temporary abnormal
transaction, transmitting a temporary abnormal transaction notice to the financial
transaction institution and recording the location of the user's mobile terminal and
information of all mobile terminals located within a minimum radius of the financial
transaction terminal, if one of two conditions occurs as follows: the location of the
financial transaction terminal does not correspond to the safe transaction region or the
calculated distance is more than the predetermined distance.
6. The method as stated in claim 4 or 5, wherein the financial institution system
performs the steps of:
receiving an approval request for the financial transaction (ARFT) from the
financial transaction terminal;
transmitting the FTCR corresponding to the ARFT to the mobile network
system;
determining whether or not a financial transaction confirmation notice in
response to the FTCR received from the mobile network system is the normal
transaction confirmation notice;
approving the requested financial transaction if the financial transaction
confirmation notice is the normal transaction confirmation notice; and
disapproving the requested financial transaction if the financial transaction
confirmation notice is a temporary abnormal transaction confirmation notice.
7. The method as stated in claim 6, wherein the financial institution system further
performs the step of putting a predetermined allowance limit on the requested financial
transaction, if the financial transaction confirmation notice is a temporary abnormal
transaction confirmation notice.
8. The method as stated in claim 6, wherein the financial institution system further
performs the step of suspending an account when the temporary abnormal transaction
occurs, if the financial transaction confirmation notice is the temporary abnormal
transaction confirmation notice.
9. The method as stated in claim 1, wherein the step of determining whether or not the
requested financial transaction is the normal transaction based on the criterion that is
selected from the group consisting of the safe transaction region predetermined by the
user, the calculated distance and the password, comprises the steps of:
determining whether or not the entered password is an emergency password;
determining whether or not the calculated distance is more than a
predetermined distance;
defining the requested financial transaction as the temporary abnormal
transaction, transmitting a temporary abnormal transaction notice to the financial
transaction institution and recording the location of the user's mobile terminal and
information of all mobile terminals locating within a minimum radius of the financial
transaction terminal, if one of two conditions occurs as follows: the entered password is
the emergency password or the calculated distance is more than the predetermined
distance.
10. The method as stated in claim 9, wherein the financial institution system performs
the steps of:
receiving the ARFT including the password from the financial transaction
terminal;
determining whether or not the entered password is a normal password;
transmitting the FTCR to the mobile network system if the entered password is
not the normal password;
determining whether or not a financial transaction confirmation notice in
response to the FTCR received from the mobile network system is the normal
transaction confirmation notice;
releasing the allowance limit to approve the requested financial transaction, if
the financial transaction confirmation notice is the normal transaction confirmation
notice; and
disapproving the requested financial transaction, if the financial transaction
confirmation notice is the temporary abnormal transaction confirmation notice.
11. The method as stated in claim 10, wherein the financial institution system further
performs the step of putting a predetermined allowance limit on the requested financial
transaction, if the financial transaction confirmation notice is the temporary abnormal
transaction confirmation notice.
12. The method as stated in claim 1 further comprising the steps of:
determining whether or not confirmation data transmitted by the user's mobile
terminal in response to the confirmation message is valid;
transmitting the normal transaction confirmation notice to the financial
institution system if the confirmation data is valid; and
transmitting the abnormal transaction confirmation notice to the financial
institution system if the confirmation data is invalid.
13. The method as stated in claim 12, wherein the confirmation data, which the user has
selected and the mobile network system oversees, is one selected from a group
consisting of number(s), character(s), and a combination of number(s) and character(s).
14. A method of a mobile network system coupled to a financial institution system
through a network for approving a user's financial transaction, said method comprising
the steps of:
receiving a financial transaction confirmation request (FTCR) transmitted by
the financial institution system corresponding to a financial transaction requested by the
user, wherein the FTCR comprises at least one selected from a group consisting of
user identification data, a location of a financial transaction terminal, and a password inputted by the user;
searching a current location of the mobile terminal of the user, which is
connected to the mobile network system, by the use of the user identification data;
determining whether or not the requested financial transaction is a normal
transaction based on a criterion that is selected from a group consisting of a safe
transaction region predetermined by the user, the searched location, and the password;
transmitting a normal transaction confirmation notice to the financial institution
system, if the requested financial transaction is the normal transaction according to the
determination; and
transmitting a confirmation message to the mobile terminal, if the requested
financial transaction is a temporary abnormal transaction according to the determination.
15. The method as stated in claim 14 further comprising the steps of:
determining whether or not confirmation data transmitted by the user's mobile
terminal in response to the confirmation message is valid;
transmitting the normal transaction confirmation notice to the financial
institution system if the confirmation data is valid; and
transmitting the abnormal transaction confirmation notice to the financial
institution system if the confirmation data is invalid.
16. A method of a mobile network and a financial institution's system for securely
performing a user's financial transaction, said method comprising the steps of:
receiving a financial transaction request of the user according to a financial
transaction from a financial transaction terminal;
acquiring a current location of the mobile terminal of the user according to the
financial transaction request;
calculating a distance between the location of the mobile terminal of the user
and the financial transaction terminal;
determining whether or not the requested financial transaction is a normal
transaction based on a criterion that is selected from a group consisting of a safe
transaction region predetermined by the user, the calculated distance, and the password;
approving the requested financial transaction, if the requested financial
transaction is a normal transaction according to the determination; and
disapproving the requested financial transaction, if the requested financial
transaction is a temporary abnormal transaction according to the determination.
17. The method as stated in claim 16, wherein the step of determining whether or not
the requested financial transaction is the normal transaction based on the criterion that is
selected from the group consisting of the safe transaction region predetermined by the
user, the calculated distance, and the password, comprises the steps of: determining whether or not the calculated distance is more than a
predetermined distance;
defining the requested financial transaction as the normal transaction, if the
calculated distance is less than the predetermined distance; and
defining the requested financial transaction as the temporary abnormal
transaction, if the calculated distance is more that the predetermined distance.
18. The method as stated in claim 16, wherein the step of determining whether or not
the requested financial transaction is the normal transaction based on the criterion that is
selected from the group consisting of the safe transaction region predetermined by the
user, the calculated distance, and the password, comprises the steps of:
determining whether or not the calculated distance is more than a
predetermined distance;
determining whether or not the location of the financial transaction terminal
corresponds to the safe transaction region;
defining the requested financial transaction as the normal transaction, if the
location of the financial transaction terminal corresponds to the safe transaction region
and the calculated distance is less than the predetermined distance; and
defining the requested financial transaction as the temporary abnormal
transaction, if one of two conditions occurs as follows: the location of the financial transaction terminal does not correspond to the safe transaction region or the calculated
distance is more than the predetermined distance.
19. The method as stated in claim 16, wherein the step of determining whether or not
the requested financial transaction is the normal transaction based on the criterion that is
selected from the group consisting of the safe transaction region predetermined by the
user, the calculated distance, and the password, comprises the steps of:
determining whether or not the entered password is an emergency password;
determining whether or not the calculated distance is more than a
predetermined distance;
defining the requested financial transaction as the temporary abnormal
transaction, if one of two conditions occurs as follows: the entered password is the
emergency password or the calculated distance is more than the predetermined distance.
20. The method as stated in claim 16 further comprising the steps of:
determining whether or not confirmation data transmitted by the user's mobile
terminal in response to the confirmation message is valid;
approving the requested financial transaction if the confirmation data is valid;
and
disapproving the requested financial transaction if the confirmation data is invalid.
21. The method as stated in claim 20 further comprising the step of transmitting a
record request for recording the location of the user's mobile terminal and information
of all mobile terminals located within a minimum radius of the financial transaction
terminal, if one of two conditions occurs as follows: the requested financial transaction
is the temporary abnormal transaction or the confirmation data is invalid.
22. A method for a mobile network and a financial institution's system for securely
performing a user's financial transaction, said method comprising the steps of:
receiving a financial transaction request of the user according to a financial
transaction from a financial transaction terminal;
acquiring a current location of the mobile terminal of the user according to the
financial transaction request;
determining whether or not the requested financial transaction is a normal
transaction based on a criterion that is selected from a group consisting of a safe
transaction region predetermined by the user, the acquired location, and the password;
approving the requested financial transaction, if the requested financial
transaction is a normal transaction according to the determination; and
transmitting a confirmation message to the user's mobile terminal, if the requested financial transaction is a temporary abnormal transaction according to the
determination.
23. The method as stated in claim 22 further comprising the steps of:
determining whether or not confirmation data transmitted by the user's mobile
terminal in response to the confirmation message is valid;
approving the requested financial transaction if the confirmation data is valid;
and
disapproving the requested financial transaction if the confirmation data is
invalid.
PCT/KR2003/000957 2002-05-16 2003-05-15 Method for guaranteeing safe financial transactions when using wireless network WO2003098525A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN038111837A CN1653472B (en) 2002-05-16 2003-05-15 Method for guaranteeing safe financial transactions when using wireless network
AU2003228107A AU2003228107A1 (en) 2002-05-16 2003-05-15 Method for guaranteeing safe financial transactions when using wireless network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2002-0027142 2002-05-16
KR10-2002-0027142A KR100466652B1 (en) 2002-05-16 2002-05-16 Method for guaranteeing financial transactions by using wireless network

Publications (1)

Publication Number Publication Date
WO2003098525A1 true WO2003098525A1 (en) 2003-11-27

Family

ID=27726344

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2003/000957 WO2003098525A1 (en) 2002-05-16 2003-05-15 Method for guaranteeing safe financial transactions when using wireless network

Country Status (4)

Country Link
KR (1) KR100466652B1 (en)
CN (1) CN1653472B (en)
AU (1) AU2003228107A1 (en)
WO (1) WO2003098525A1 (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1835468A2 (en) * 2006-03-15 2007-09-19 Omron Corporation User equipment, authentication system, authentication method, authentication program and recording medium
EP2199966A1 (en) * 2008-12-22 2010-06-23 Compagnie Industrielle et Financiere d'Ingenierie "Ingenico" Method for securing transactions, corresponding transaction device, banking server, mobile terminal and computer program products
GB2468977A (en) * 2009-01-28 2010-09-29 Validsoft Card false-positive prevention
US8131312B2 (en) 2010-05-24 2012-03-06 Nice Systems Ltd. Method and system for construction of radio environment model
US8166068B2 (en) * 2005-09-02 2012-04-24 Qwest Location based authorization of financial card transactions systems and methods
US8176077B2 (en) * 2005-09-02 2012-05-08 Qwest Communications International Inc. Location based access to financial information systems and methods
US8200244B2 (en) 2010-05-24 2012-06-12 Nice Systems Ltd. Method and system for mobile station location
WO2013048389A1 (en) * 2011-09-28 2013-04-04 Intel Corporation Techniques for dynamic enpoint secure location awareness
US8510319B2 (en) 2005-09-02 2013-08-13 Qwest Communications International Inc. Location based information for emergency services systems and methods
WO2013158905A1 (en) * 2012-04-19 2013-10-24 Alibaba Group Holding Limited Account security protection method and system
US8588808B2 (en) 2010-05-24 2013-11-19 Nice-Systems Ltd. Method and system for estimation of mobile station velocity in a cellular system based on geographical data
CN103702414B (en) * 2013-12-11 2017-05-24 北京智谷睿拓技术服务有限公司 Locating method, mobile equipment and base station
US10957166B2 (en) 2015-09-23 2021-03-23 Harex Infotech Inc. System and method for providing automated teller service using mobile terminal

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20040039034A (en) * 2002-10-30 2004-05-10 엘지전자 주식회사 Credit card approval system using mobile terminal and method thereof
CN101464981A (en) * 2007-12-18 2009-06-24 黄金富 Bank card account security system and method through mobile phone orientation authentication card owner identification
US20100049615A1 (en) 2008-01-24 2010-02-25 Qualcomm Incorporated Mobile commerce authentication and authorization system
CN101588577A (en) * 2008-05-19 2009-11-25 罗邵波 Safe system and method for bank transaction system
CN101303781B (en) * 2008-06-16 2011-08-10 北京邮电大学 Method and equipment for preventing finance card from brushing deceptively
US7933836B2 (en) * 2008-09-30 2011-04-26 Avaya Inc. Proxy-based, transaction authorization system
CN102014336A (en) * 2010-08-19 2011-04-13 上海闻泰电子科技有限公司 Mobile positioning method based on GPS
CN102346940A (en) * 2011-01-06 2012-02-08 杨明生 Forward bank counter system and method for utilizing same to conduct forward bank counter business
JP2013097650A (en) * 2011-11-02 2013-05-20 Bank Of Tokyo-Mitsubishi Ufj Ltd Authentication system, authentication method and authentication server
CN103167403A (en) * 2011-12-15 2013-06-19 中国移动通信集团四川有限公司 Authentication method and system of electronic channel service
CN103164802A (en) * 2013-03-14 2013-06-19 北京恒远创智信息技术有限公司 Position detection based method and system for preventing illegal electronic transaction
CN104252731B (en) * 2014-09-04 2017-05-24 天津大学 High-safety wireless transaction method based on self-authentication mechanism efficiency
CN104866887B (en) * 2015-06-11 2017-10-24 辽宁北斗平台科技有限公司 The bank card accessory system positioned based on the Big Dipper
KR101828445B1 (en) * 2015-09-23 2018-02-13 주식회사 하렉스인포텍 System and method for providing automated teller machine service using mobile device
CN106652257A (en) * 2016-11-29 2017-05-10 杭州东方通信软件技术有限公司 Supervision system and supervision method
CN106937248B (en) * 2017-01-25 2019-09-17 北京安云世纪科技有限公司 A kind of document handling method of mobile terminal, device and mobile terminal

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2240808A1 (en) * 1997-07-09 1999-01-09 Northern Telecom Limited Method and system in a wireless communications network for providing toll restrictions based on the geographic location of an originator
WO2001055982A1 (en) * 2000-01-28 2001-08-02 Fundamo (Proprietary) Limited System for conducting commercial transactions
US6326918B1 (en) * 1995-06-06 2001-12-04 Wayport, Inc. Method and apparatus for geographic-based communications service
US20020038287A1 (en) * 2000-08-30 2002-03-28 Jean-Marc Villaret EMV card-based identification, authentication, and access control for remote access
US20020125886A1 (en) * 2001-03-12 2002-09-12 International Business Machines Corporation Access to applications of an electronic processing device solely based on geographic location

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20010096373A (en) * 2000-04-18 2001-11-07 조진원 Settlement method using cellular phone and method of authentication for secure settlement thereof
TW589855B (en) * 2000-05-15 2004-06-01 Ntt Docomo Inc Authentication system and method
JP2002099860A (en) * 2000-09-26 2002-04-05 Sanyo Electric Co Ltd Card settlement member store terminal, card settlement service system and card effectiveness judging method for card settlement
KR20030039808A (en) * 2001-11-14 2003-05-22 인포뱅크 주식회사 System and Method for Location Based Mediating a Circulation of Money

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6326918B1 (en) * 1995-06-06 2001-12-04 Wayport, Inc. Method and apparatus for geographic-based communications service
CA2240808A1 (en) * 1997-07-09 1999-01-09 Northern Telecom Limited Method and system in a wireless communications network for providing toll restrictions based on the geographic location of an originator
WO2001055982A1 (en) * 2000-01-28 2001-08-02 Fundamo (Proprietary) Limited System for conducting commercial transactions
US20020038287A1 (en) * 2000-08-30 2002-03-28 Jean-Marc Villaret EMV card-based identification, authentication, and access control for remote access
US20020125886A1 (en) * 2001-03-12 2002-09-12 International Business Machines Corporation Access to applications of an electronic processing device solely based on geographic location

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8166068B2 (en) * 2005-09-02 2012-04-24 Qwest Location based authorization of financial card transactions systems and methods
US8510319B2 (en) 2005-09-02 2013-08-13 Qwest Communications International Inc. Location based information for emergency services systems and methods
US9002814B2 (en) 2005-09-02 2015-04-07 Qwest Communications International Inc. Location based authorization of financial card transactions systems and methods
US8935226B2 (en) 2005-09-02 2015-01-13 Qwest Communications International Inc. Location based access to financial information systems and methods
US8176077B2 (en) * 2005-09-02 2012-05-08 Qwest Communications International Inc. Location based access to financial information systems and methods
US8301116B2 (en) 2006-03-15 2012-10-30 Omron Corporation User equipment, authentication system, authentication method, authentication program and recording medium
EP1835468A2 (en) * 2006-03-15 2007-09-19 Omron Corporation User equipment, authentication system, authentication method, authentication program and recording medium
EP1835468A3 (en) * 2006-03-15 2009-09-30 Omron Corporation User equipment, authentication system, authentication method, authentication program and recording medium
FR2940567A1 (en) * 2008-12-22 2010-06-25 Ingenico Sa TRANSACTION SECURING METHOD, TRANSACTION DEVICE, BANK SERVER, MOBILE TERMINAL, AND CORRESPONDING COMPUTER PROGRAM PRODUCTS
US9697511B2 (en) 2008-12-22 2017-07-04 Ingenico Group Method for securing transactions, transaction device, bank server, mobile terminal, and corresponding computer programs
EP2199966A1 (en) * 2008-12-22 2010-06-23 Compagnie Industrielle et Financiere d'Ingenierie "Ingenico" Method for securing transactions, corresponding transaction device, banking server, mobile terminal and computer program products
GB2468977A (en) * 2009-01-28 2010-09-29 Validsoft Card false-positive prevention
US11449850B2 (en) 2009-01-28 2022-09-20 Validsoft Limited Card false-positive prevention
US8131312B2 (en) 2010-05-24 2012-03-06 Nice Systems Ltd. Method and system for construction of radio environment model
US8588808B2 (en) 2010-05-24 2013-11-19 Nice-Systems Ltd. Method and system for estimation of mobile station velocity in a cellular system based on geographical data
US8478294B2 (en) 2010-05-24 2013-07-02 Nice-Systems Ltd. Method and system for mobile station location
US8200244B2 (en) 2010-05-24 2012-06-12 Nice Systems Ltd. Method and system for mobile station location
WO2013048389A1 (en) * 2011-09-28 2013-04-04 Intel Corporation Techniques for dynamic enpoint secure location awareness
US9825968B2 (en) 2011-09-28 2017-11-21 Intel Corporation Techniques for dynamic enpoint secure location awareness
WO2013158905A1 (en) * 2012-04-19 2013-10-24 Alibaba Group Holding Limited Account security protection method and system
JP2015520442A (en) * 2012-04-19 2015-07-16 アリババ・グループ・ホールディング・リミテッドAlibaba Group Holding Limited Account security protection method and system
CN103702414B (en) * 2013-12-11 2017-05-24 北京智谷睿拓技术服务有限公司 Locating method, mobile equipment and base station
US10957166B2 (en) 2015-09-23 2021-03-23 Harex Infotech Inc. System and method for providing automated teller service using mobile terminal

Also Published As

Publication number Publication date
CN1653472B (en) 2010-05-05
CN1653472A (en) 2005-08-10
KR20020070165A (en) 2002-09-05
KR100466652B1 (en) 2005-01-17
AU2003228107A1 (en) 2003-12-02

Similar Documents

Publication Publication Date Title
WO2003098525A1 (en) Method for guaranteeing safe financial transactions when using wireless network
AU2018204529B2 (en) Electronic transaction fraud prevention
US6913194B2 (en) Method and system to prevent fraudulent payment in credit/debit card transactions, and terminals therefor
EP2507754B1 (en) System and method for approving transactions
EP1487176A1 (en) A method of paying from an account by a customer having a mobile user terminal, and a customer authenticating network
US20020017561A1 (en) Electronic payment system using accounting function in a mobile communication network
US20090012898A1 (en) Location based credit card fraud prevention
US20110282789A1 (en) Card false-positive prevention
US20090150248A1 (en) System for enhancing payment security, method thereof and payment center
JP2002117377A (en) Personal authentication system using position information, authentication system by card and door lock system by password number
CN102197407A (en) System and method of secure payment transactions
CA2694926A1 (en) Financial transaction system having location-based fraud-protection
EP2710825A2 (en) Methods, systems, and computer-readable storage media for managing risk using location, mobile, and user participating - based identity verification
KR20130086841A (en) System and method for preventing abuse urgent call using smart phone
WO2016180185A1 (en) Method and apparatus for determining position of point of sale (pos)
KR100497223B1 (en) Method and System for Providing Location-Based Credit Card Authentication Service
CN106127463B (en) Transfer control method and terminal equipment
WO2002021354A1 (en) Payment system
JP4755865B2 (en) Card authentication device, card authentication system, card authentication method, and card authentication program
KR101751534B1 (en) Illegal financial service prevention apparatus
KR20030052800A (en) Method for approval a financial transaction in bank server
JP2002288744A (en) Card certification system
KR20040098407A (en) System and Method of financial transaction using Emergency Password Number
KR20030031087A (en) Method for financial transaction using by location information of mobile terminal
KR101719450B1 (en) Mobile payment system and mobile payment method

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 1-2004-501775

Country of ref document: PH

WWE Wipo information: entry into national phase

Ref document number: 20038111837

Country of ref document: CN

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP