U.S. patent application number 12/955390 was filed with the patent office on 2011-03-24 for system and method for securely authorizing and distributing stored-value card data.
Invention is credited to Phillip Craig Graves, Merrill Brooks SMITH.
Application Number | 20110068168 12/955390 |
Document ID | / |
Family ID | 34226208 |
Filed Date | 2011-03-24 |
United States Patent
Application |
20110068168 |
Kind Code |
A1 |
Graves; Phillip Craig ; et
al. |
March 24, 2011 |
System and Method for Securely Authorizing and Distributing
Stored-Value Card Data
Abstract
A computerized system and method for securely authorizing and
distributing stored-value card data over a communications network
is provided. The method allows for storing in the database a
plurality of records comprising stored-value card data for each
stored-value card as well as information identifying a plurality of
trusted sources of stored-value card activation requests and/or a
plurality of trusted communications networks for transmitting
stored-value card activation requests. A transmitting step allows
for a requesting terminal to transmit over a communications network
a request to change the status of a stored-value card. The central
processor then determines whether the requesting terminal and/or
the communications network is a trusted source. Based on whether
the requesting terminal or communications network is a trusted
source or trusted communications network, the request can be
processed and the card can be activated. A method for establishing
a list of trusted sources and trusted communications networks is
also provided.
Inventors: |
Graves; Phillip Craig;
(Atlanta, GA) ; SMITH; Merrill Brooks; (Ft.
Lauderdale, FL) |
Family ID: |
34226208 |
Appl. No.: |
12/955390 |
Filed: |
November 29, 2010 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10655828 |
Sep 5, 2003 |
|
|
|
12955390 |
|
|
|
|
10411971 |
Apr 11, 2003 |
7083084 |
|
|
10655828 |
|
|
|
|
09641363 |
Aug 18, 2000 |
6575361 |
|
|
10411971 |
|
|
|
|
60149740 |
Aug 19, 1999 |
|
|
|
Current U.S.
Class: |
235/379 |
Current CPC
Class: |
G06Q 20/02 20130101;
G06Q 20/3558 20130101; G06Q 20/3552 20130101; G06Q 20/28 20130101;
G06Q 20/3829 20130101; G07F 7/1008 20130101; G06Q 20/04
20130101 |
Class at
Publication: |
235/379 |
International
Class: |
G06Q 40/00 20060101
G06Q040/00 |
Claims
1-60. (canceled)
61. A computer-implemented method for processing a stored-value
card transaction request in a card data management system having a
central processor in communication with a plurality of
point-of-sale terminals over a communications network, each of the
one or more terminals having a unique terminal identifier and being
associated with a location and a prepaid card merchant, the central
processor being in communication with a database having stored
therein a plurality of card records, each card record containing
data associated with a stored-value card distributed to a prepaid
card merchant for further distribution to purchasers at a location
controlled by the prepaid card merchant, the method comprising:
receiving the stored-value card transaction request from a
requesting terminal, the requesting terminal being one of the
plurality of point-of-sale terminals, the transaction request
comprising a requesting terminal identifier, a card identifier
assigned to a stored value card, and information indicative of a
requested transaction type; determining if the requesting terminal
is authorized to request the requested transaction type for the
stored value card; responsive to a determination that the
requesting terminal is authorized to request the requested
transaction type, initiating the requested transaction; and
transmitting a request response to the requesting terminal.
62. A computer-implemented method according to claim 61 wherein the
requested transaction type is one of the group consisting of card
activation, card value incrementation, card deactivation, and card
value redemption.
63. A computer-implemented method according to claim 61 further
comprising the action of: associating in the database a set of
authorized terminal identifiers with the stored-value card.
64. A computer-implemented method according to claim 63 wherein the
action of determining if the requesting terminal is authorized
comprises the action of: comparing the requesting terminal
identifier to the set of authorized terminal identifiers.
65. A computer-implemented method according to claim 63 further
comprising the actions of: determining criteria for authorizing
terminals to request transactions for the stored value card; and
assembling the set of authorized terminal identifiers based on the
criteria for authorizing.
66. A computer-implemented method according to claim 65 wherein the
criteria for authorizing include at least one of the set consisting
of a terminal location requirement, a terminal ownership
requirement, and terminal affiliation with a particular
merchant
67. A computer-implemented method according to claim 63 further
comprising the actions of: associating in the database a set of one
or more authorized transaction types with each authorized terminal
identifier.
68. A computer-implemented method according to claim 67 wherein the
action of determining if the requesting terminal is authorized
further comprises the actions of: comparing the requesting terminal
identifier to the set of authorized terminal identifiers; and
responsive to a determination that the requesting terminal
identifier matches an authorized terminal identifier, comparing the
requested transaction type to the set of authorized transaction
types associated with the authorized terminal identifier.
69. A computer-implemented method according to claim 61 wherein the
stored-value card transaction is a card value redemption
transaction and the transaction request further comprises a
purchase amount.
70. A computer-implemented method according to claim 69 wherein the
card record data includes a stored value for the stored-value card
and the action of initiating the requested transaction comprises:
determining from the database the stored value associated with the
stored-value card; determining whether the purchase amount exceeds
the stored value; and responsive to a determination that the
purchase amount does not exceed the stored value, subtracting the
purchase amount from the stored value.
71. A computer-implemented method according to claim 69 further
comprising: responsive to a determination that the purchase amount
exceeds the stored value, setting the stored value to zero.
72. A system for processing a request for a stored-value card
transaction for a stored-value card, the transaction request being
submitted by a retailer using a point-of-sale terminal that is one
of a plurality of terminals capable of communicating over a
network, each terminal having a unique terminal identifier and
being associated with one of a plurality of merchants, the
stored-value card transaction request comprising a unique card
identifier for the particular stored value card, the terminal
identifier of the point-of-sale terminal, and information
indicative of a requested transaction type, the system comprising:
a central processor in communication with the network, the central
processor being adapted to receive the transaction request from the
point-of-sale terminal; a database in communication with the
central processor, the database having stored therein a plurality
of stored-value card records, each comprising a unique card
identifier associated with a stored-value card distributed to one
of the plurality of merchants; an associating module in the central
processor configured for associating, in the database, a set of
authorized terminal identifiers with each stored-value card record;
a transaction authorization module in the central processor
configured for determining, based on information in the transaction
request and the database, whether the requesting terminal is
authorized to request the requested transaction type; and at least
one transaction processing module in the central processor
configured for processing the requested transaction responsive to a
determination by the transaction authorization module that the
requesting terminal is authorized to request the requested
transaction type.
73. A system according to claim 72 wherein the transaction
authorization module is configured to determine whether the
requesting terminal is authorized by determining whether the
requesting terminal identifier matches an authorized terminal
identifier in the set of authorized terminal identifiers.
74. A system according to claim 72 wherein the associating module
is further configured for associating, in the database, a set of
one or more authorized transaction types with each authorized
terminal identifier.
75. A system according to claim 74 wherein the transaction
authorization module is configured to determine whether the
requesting terminal is authorized by determining whether the
requesting terminal identifier matches an authorized terminal
identifier in the set of authorized terminal identifiers, and by
comparing the requested transaction type to the set of authorized
transaction types associated with the authorized terminal
identifier.
76. A system according to claim 72 wherein the set of authorized
terminal identifiers is based on authorization criteria comprising
at least one of the set consisting of a terminal location
requirement, a terminal ownership requirement, and terminal
affiliation with a particular merchant.
77. A system according to claim 72 wherein the at least one
transaction processing module includes at least one of the group
consisting of a card activation module, a card value incrementation
module, a card deactivation module, and a card value redemption
module.
78. A system according to claim 72 further comprising: a value
module adapted to determine and store in the database, in response
to a stored-value card transaction, a card value for the
stored-value card of the transaction.
79. A computer program embodied in a computer-readable medium for
processing a stored-value card transaction request in a card data
management system having a central processor in communication with
a plurality of point-of-sale terminals over a communications
network, each of the one or more terminals having a unique terminal
identifier and being associated with a location and a prepaid card
merchant, the central processor being in communication with a
database having stored therein a plurality of card records, each
card record containing data associated with a stored-value card
distributed to a prepaid card merchant for further distribution to
purchasers at a location controlled by the prepaid card merchant,
the computer program comprising instructions for performing a set
of actions comprising: receiving the stored-value card transaction
request from a requesting terminal, the requesting terminal being
one of the plurality of point-of-sale terminals, the transaction
request comprising a requesting terminal identifier, a card
identifier assigned to a stored value card, and information
indicative of a requested transaction type; determining if the
requesting terminal is authorized to request the requested
transaction type for the stored value card; responsive to a
determination that the requesting terminal is authorized to request
the requested transaction type, initiating the requested
transaction; and transmitting a request response to the requesting
terminal.
80. A computer program according to claim 79 wherein the requested
transaction type is one of the group consisting of card activation,
card value incrementation, card deactivation, and card value
redemption.
81. A computer program according to claim 79 wherein the set of
actions further comprises: associating in the database a set of
authorized terminal identifiers with the stored-value card.
82. A computer program according to claim 81 wherein the action of
determining if the requesting terminal is authorized comprises the
action of: comparing the requesting terminal identifier to the set
of authorized terminal identifiers.
83. A computer program according to claim 81 wherein the set of
actions further comprises: determining criteria for authorizing
terminals to request transactions for the stored value card; and
assembling the set of authorized terminal identifiers based on the
criteria for authorizing.
84. A computer program according to claim 83 wherein the criteria
for authorizing include at least one of the set consisting of a
terminal location requirement, a terminal ownership requirement,
and terminal affiliation with a particular merchant.
85. A computer program according to claim 81 wherein the set of
actions further comprises: associating in the database a set of one
or more authorized transaction types with each authorized terminal
identifier.
86. A computer program according to claim 85 wherein the action of
determining if the requesting terminal is authorized further
comprises the actions of: comparing the requesting terminal
identifier to the set of authorized terminal identifiers; and
responsive to a determination that the requesting terminal
identifier matches an authorized terminal identifier, comparing the
requested transaction type to the set of authorized transaction
types associated with the authorized terminal identifier.
87. A computer program according to claim 79 wherein the
stored-value card transaction is a card value redemption
transaction and the transaction request further comprises a
purchase amount.
88. A computer program according to claim 87 wherein the card
record data includes a stored value for the stored-value card and
the action of initiating the requested transaction comprises:
determining from the database the stored value associated with the
stored-value card; determining whether the purchase amount exceeds
the stored value; and responsive to a determination that the
purchase amount does not exceed the stored value, subtracting the
purchase amount from the stored value.
89. A computer program according to claim 88 wherein the action of
initiating the requested transaction further comprises: responsive
to a determination that the purchase amount equals or exceeds the
stored value, setting the stored value to zero.
Description
RELATED APPLICATIONS
[0001] This application claims the benefit of the U.S. application
Ser. No. 10/411,971, filed Apr. 11, 2003, which claims priority to
U.S. application Ser. No. 09/641,363 filed on Aug. 18, 2000, which
claims priority to U.S. Provisional Application No. 60/149,740
filed on Aug. 19, 1999, all of which are incorporated herein by
reference. This application is related to U.S. application Ser. No.
10/253,243 filed on Sep. 24, 2002 and International Application No.
PCT/US02/30281 filed Sep. 24, 2002, which claim priority to U.S.
Provisional Application No. 60/396,404 filed Jul. 15, 2002 and U.S.
Provisional Application No. 60/324,333 filed Sep. 24, 2001, which
are all incorporated herein by reference.
FIELD OF THE INVENTION
[0002] The present invention is generally related to remote data
authorization and distribution. More particularly, the present
invention is related to a system and method for securely
authorizing and distributing stored-value card data between a
plurality of users and a central processor over a communications
network.
BACKGROUND OF THE INVENTION
[0003] Stored-value cards can be authorized and distributed over
communications networks. Examples of communications networks
include dedicated telephone lines, public telephone links, and the
internet or other networked communication. The data of the
stored-value cards is related to services and/or products prepaid
by the owner or end user of the card. Examples of prepaid services
that may be accommodated by the stored-value data include long
distance telephone communication, wireless communication, paging
and internet-enabled communication services, including wireless web
access. Other examples of prepaid services and/or products that may
be accommodated by the stored-value card include gift cards,
prepaid gas cards, prepaid grocery cards, prepaid entertainment
cards, downloadable ring tone cards, downloadable game cards,
downloadable music cards that use MP3, MP4, WMV, WAV, or other
music formats, any other downloadable software card, customer
rewards cards, and any other type of stored-value cards for
products, services, or both, that may be prepaid by the owner of
the card.
[0004] Stored-value cards, such as prepaid long distance phone
cards, are generally used in the telephone industry to allow
customers to pre-purchase long distance calling time. Each of the
cards has a printed identification number. Associated
identification information can be magnetically stored therein or
printed in a barcode. The identification number is also stored in a
file in a database maintained by the card issuer. In the
traditional business model, when the cards are sent to the retail
location from which they will be sold, the corresponding records in
the database are activated, thus allowing the card to be used
immediately by a customer. To use the card as a prepaid long
distance card, the customer dials a toll free number to access the
card issuer's system, enters the identification number, and then
makes the desired long-distance call.
[0005] These prior art prepaid phone card systems have several
disadvantages. For example, since the cards are active while on the
shelf in the retail location, the cards may be stolen by a thief
and easily used. One way to address some of the drawbacks of prior
art prepaid phone card systems would be to install activation
terminals unique to the prepaid card issuer. This is referred to as
a "closed system." U.S. Pat. No. 5,577,109 to Stimson et al.
discloses such a closed system. In the Stimson system, the cards
are not preactivated. Each of the retail locations from which cards
are to be sold is provided with a dedicated activation terminal
which allows the retail operator to set the value of the card at
the time of the sale. The activation terminal connects to the card
issuer's system to pass along the value amount and to request
activation of the card. Depleted cards can be recharged in the same
manner as they are sold. A serious disadvantage of the Stimson
system is that it requires single-function dedicated hardware to be
installed in each retail location, resulting in a very inflexible
and expensive system.
[0006] US. Pat. No. 6,000,608 to Dorf provides a multifunction card
system including a prepaid phone card activating system which
allows cards to be purchased in varying amounts and to be recharged
without requiring the use of a closed system to handle the
transactions. Although Dorf purports to alleviate some of the
drawbacks of Stimson by using point-of-sale devices connected to a
banking system, it is believed that Dorf fails to verify sources of
card activation requests so as to enhance detection of potential
security breaches that could ensue in any system accessible to a
large number of users.
[0007] It would be further desirable to provide a system and method
for selectively processing stored-value card requests, such as
stored-value card activation, deactivation, and/or value change,
based on the communications network over which the request is
transmitted. Additionally, it would be further desirable to provide
a system and method for selectively processing stored-value card
requests based on the source of the request, wherein such request
can be received over a variety of communications networks that are
available to unauthorized users. It would be further desirable to
provide a method of determining a plurality of communications
networks and a plurality of sources of activation requests that are
authorized to carry or make valid requests, respectively, either
prior to or at the same time as such requests are made.
BRIEF SUMMARY OF THE INVENTION
[0008] Generally speaking, the foregoing needs are fulfilled by
providing in one exemplary embodiment a computerized method for
securely authorizing and distributing stored-value card data over a
communications network. The method allows for storing in the
database a plurality of records comprising stored-value card data
for each stored-value card and a plurality of records comprising
information identifying trusted sources of requests to change the
status of a stored-value card and/or information identifying
trusted communications networks known to transmit valid requests.
Trusted sources can include any requestor, including merchant
terminals on a dedicated line, merchant terminals at a particular
or identified phone number, and merchant terminals at a particular
or identified internet IP address. Trusted communications networks
that are identified to be trusted sources may comprise the internet
when the requestor has a static IP address or any other computer
network such as a WAN or LAN, a dedicated data line such as a
dedicated phone line, and a public switched telephone network that
provides automatic number identification (ANI). A transmitting step
allows for transmitting a request to change the status of a
stored-value card over a communications network from a requesting
terminal to the central processor. Such communications networks
comprise dedicated data lines such as dedicated phone lines, frame
relay or X.25 circuits, public telephone links such as a public
switched telephone network, and the internet, including networks
wherein the merchant terminal is part of a WAN or LAN. The central
processor is configured to receive requests from merchant terminals
over one or more communications networks and determine whether the
respective terminal is a trusted source and/or whether the request
was transmitted over a trusted communications network. A processing
step allows for processing the request based on the determining
step.
[0009] In yet another aspect thereof, the present invention
fulfills the foregoing needs by providing a computer-readable
medium encoded with computer program code for securely authorizing
and distributing stored-value card requests over a communications
network, the program code causing a computer to execute a method
comprising: controlling a database coupled to the central
processor; storing in the database a plurality of records
comprising stored-value card data for each stored-value card as
well as information identifying trusted sources for making
stored-value card processing requests and/or information
identifying trusted communications networks for carrying or
transmitting stored-value card processing requests; receiving a
request for processing the stored-value card over a communications
network from a requesting terminal to the central processor;
determining whether the respective requesting terminal is a trusted
source of requests for processing and/or whether the communications
network is a trusted communications network for carrying or
transmitting requests for processing; and processing the request
based on the determining step.
[0010] Other embodiments can be considered.
[0011] In yet another aspect thereof, the present invention
fulfills the foregoing needs by providing a method for securely
authorizing stored-value card transactions. The method includes an
identifying step for identifying one or more trusted sources of
stored-value card processing requests and/or one or more trusted
communications networks for carrying and/or transmitting
stored-value card processing requests. An assigning step allows for
identifiers to be assigned to each identified trusted source and
trusted communications network. A storing step allows for storing
the identifiers in a database coupled to a processor configured to
receive a request to process stored-value cards, wherein the
request is received from a user terminal over a communications
network. In another step, it is determined whether the respective
requesting terminal is a trusted source of requests for processing
and/or it is determined whether the communications network is a
trusted communications network for carrying or transmitting
requests for processing. Finally, the method allows for processing
the request based on the determining step.
[0012] Other embodiments can be considered.
[0013] In yet another aspect thereof, the present invention
fulfills the foregoing needs by providing a system for authorizing
stored-value card requests over a communications network between a
plurality of terminals and a central processor. The system
comprises a database coupled to the central processor. The system
also comprises a storage module configured to store in the database
a plurality of records comprising stored-value card data for each
stored-value card as well as information identifying trusted
sources for making stored-value card processing requests and/or
information identifying trusted communications networks for
carrying or transmitting stored-value card processing requests. The
system also comprises a value module configured to define in each
stored record a parameter corresponding to the value of each
respective stored-value card; a first processing module configured
to process a request from a respective requesting terminal to the
central processor, the central processor configured to accept the
request based on whether the request originated from a trusted
source and/or whether the request was transmitted or carried by a
trusted communications network.
[0014] Other embodiments could be considered.
[0015] According to yet another embodiment of the invention, a
method for securely authorizing stored-value card transactions is
provided. The method comprises identifying one or more trusted
sources of stored-value card processing requests and/or one or more
trusted communications networks for carrying and/or transmitting
stored-value card processing requests. An assigning step allows for
assigning identifiers to each identified trusted source and trusted
communications network. A storing step allows for storing the
identifiers in a database coupled to a processor. A receiving step
allows for receiving a request to process stored-value cards,
wherein the request is received from a user terminal over a
communications network. A determining step allows for determining
whether the respective requesting terminal is a trusted source of
requests for processing and/or determining whether the
communications network is a trusted communications network for
carrying or transmitting requests for processing. Finally, a
processing step allows for processing the request based on the
determining step.
[0016] Other embodiments could be considered.
DESCRIPTION OF THE DRAWINGS
[0017] FIGS. 1-4 respectively illustrate schematic block diagrams
showing how various exemplary stored-value card user trees, as
shown in FIGS. 1-3, may be connected via a communications network
to a remote stored-value card data management system embodying the
present invention;
[0018] FIG. 5 is an exemplary modular architecture of the
telecommunications card data management system shown in FIGS.
1-3;
[0019] FIG. 6 is an exemplary flow chart illustrating one aspect of
the present invention as may be implemented by the system of FIG.
5;
[0020] FIG. 7 is an exemplary flow chart illustrating another
aspect of the present invention as may be implemented by the system
of FIG. 4;
[0021] FIGS. 8A, 8B, and 8C are block diagrams illustrating
different types of communications networks;
[0022] FIG. 9 is a block diagram illustrating an exemplary user
tree and communication path of requests for stored-value cards
between terminals and the central processor; and
[0023] FIG. 10 is an exemplary flow chart illustrating another
aspect of the present invention as may be implemented by the system
of FIG. 3.
[0024] Before any embodiment of the invention is explained in
detail, it is to be understood that the invention is not limited in
its application to the details of construction and the arrangements
of components set forth in the following description or illustrated
in the drawings. The invention is capable of other embodiments and
of being practiced or being carried out in various ways. Also, it
is to be understood that the phraseology and terminology used
herein is for the purpose of description and should not be regarded
as limiting.
DETAILED DESCRIPTION OF THE INVENTION
[0025] FIGS. 1-4 illustrate examples of entity trees that may
benefit from the system and techniques of the present invention.
For simplicity of illustration, the customer/distributor layer at
the top is omitted. Each distributor can have subordinate to it any
of the illustrated types of structures. Note that in each case, a
merchant 2 is at the top, with a layer of locations 3 just above a
layer of terminals 12.
[0026] As shown in FIGS. 1 through 3, by way of a communications
network 10, e.g., a public switched phone network, a wireless
network, a dedicated data circuit such as a dedicated phone line, a
credit or debit card network, the Internet, an intranet, etc., over
which credit or debit card transactions are authorized or denied,
and/or a point-of-sale terminal 12, e.g., a credit or debit card
terminal, is used to send an authorization request to a
stored-value card data management system 14, such as may be managed
and operated by the assignee of the present invention. System 14
comprises a central processor 16 coupled to a database 18. The
central processor 16 can be a host computer, a computer server, a
computer system with software applications that receive
transactions and process them according to preset rules, and any
other computer system. The database 18 stores a plurality of
records including stored-value card data for each stored-value card
issued by the assignee of the present invention. The database can
also store information identifying trusted sources for making
stored-value card processing requests, such as requests to activate
a stored-value card, and it can additionally store information
identifying trusted communications networks for carrying or
otherwise transmitting stored-value card processing requests. The
identification information can be a telephone number, a static IP
address, a password, a PIN, a merchant and/or terminal ID, or
another unique code that can be associated with a particular user,
merchant terminal, or communications network. The code may be
chosen by a user at the terminal, randomly assigned, or selected
from a list of codes by the central processor 16 and assigned to
the terminal. It will be appreciated that in the case of a credit
or debit card network, each stored-value card transaction request
is expected to be handled, on average, within a certain time period
such as approximately two seconds, or else one could lose its
certification to use that network.
[0027] A respective requesting terminal, using the communications
network 10, may send an authorization request through a suitable
host bank 20 to the central processor. The authorization request
could also be routed straight to the communications network 10
without passing through a host bank 20. FIGS. 1 through 3 show an
exemplary link architecture between the communications network and
the central processor, optionally through the host bank. That is,
the link architecture allows communication of card related data
from the merchant, to the communications network, which in one
exemplary embodiment would be the Visa network for a Visa-routed
transaction, to the host bank, and then to the central processor.
It will be appreciated that other link architectures may be
implemented, such as a host-to-host architectural connection. In
this case, the communications network, such as a dedicated link or
the internet, would be directly between a merchant's "host" system
and a "host" system of the assignee of the present invention. Thus,
the present invention is not limited to applications that require a
host bank being that a host-to-host connection does not require any
host bank or Visa network to transfer the card-related data to the
central processor.
[0028] The authorization request may include information about the
card swiped and the terminal used to swipe it, such as the
electronic signature of that terminal, an IP address of the
terminal, a phone number of the terminal, or a password provided by
the terminal. It should be appreciated that other methods may be
used to capture identification of the card besides swiping it; for
instance, the information can be barcode-scanned or entered
manually at a keypad of a computer. Further, merchant terminals 12
may be any system that can transmit card identifier information
over a communications network. Thus, merchant terminals 12 can be
telephones, electronic cash registers, credit card machines, fax
machines, computers, or other devices that can receive and transmit
information.
[0029] In another aspect of the system of the present invention, as
shown in FIGS. 3 and 4, merchants and terminals can be divided into
groups, membership of which varies depending on whether the context
of the grouping is for the purpose of executing any specific action
out of a set of actions that a respective user may execute, such as
card activation, billing, commission payments, reporting, inventory
management, etc. For example, terminal A from Merchant X may be in
activation group I with terminal B from merchant Y, yet for billing
purposes the two terminals may be in different groups. Also,
Merchant X may be affiliated with terminals A, B, and C, and thus
A, B, and C may be classified in the same group. Merchant X may
also be grouped with Merchant Y and its terminals D, E, and F. In
this way, terminals A-F may be in the same activation group for
instance. The central processor can be preconfigured to determine
whether a terminal is a trusted source based on whether the
requestor is in the same group as another terminal or merchant that
is considered a trusted source.
[0030] Terminals in a given group can share a communications
network. For instance, all the terminals in a given group may share
a dedicated data line that connects them to the central processor.
Requests can then be authorized when the central processor
recognizes that the request was received via the dedicated data
line and determines that the dedicated data line is a trusted
source. Similarly, terminals in a given group can share a set of
static IP addresses. In one embodiment, terminals are assigned
static IP addresses when they log on to a server operated by an
entity associated with the group. The server entity assigns a
terminal an IP address selected from a defined set of IP addresses.
Each of the IP addresses in the defined set is a trusted source and
therefore has identifying information stored at the database.
[0031] Management and definition of these groups is the
responsibility of a module configured to store in the database a
list of trusted sources and trusted communications networks. The
database can also include a table indicative of the set of actions
that a respective user may execute from a respective terminal.
[0032] FIG. 4 shows an exemplary entity tree for a store-value card
merchant 2. One or more merchant terminals 12 are located at a
particular location 3 of a merchant, such as a particular store
location. One or more locations 3 will be associated with a
stored-value card merchant 2. Stored-value card merchants 2 may
then be affiliated or otherwise associated with other stored-value
card merchants 2, which may in turn have further affiliations with
additional stored-value card merchants 2. By means of such a
stored-value card merchant 2 network, a given merchant 2 may be
associated with one or more locations 3 and terminals 12 through
other merchants 2. For the sake of simplicity of illustration,
blocks representing the stored-value card data management system
and other associated blocks are not shown in the user entity trees
shown in FIG. 4. It will be appreciated, however, that each of such
user entity trees will be similarly interconnected to the
stored-value card data management system 14 as exemplarily
illustrated in FIGS. 1 through 3 or as further described
herein.
[0033] FIG. 5 illustrates further details in connection with
stored-value card data management system 16. As shown in FIG. 5,
central processor 16 includes a storage control module 34 that
allows for storing in database 18 a plurality of stored-value card
records 37 comprising stored-value card data for each stored-value
card, information identifying trusted sources for making
stored-value card processing requests, and information identifying
trusted communications networks for carrying or transmitting
stored-value card processing requests. An associating module 36
allows for associating in each stored record respective identifiers
that uniquely match a respective stored-value card and a respective
terminal, or to match a card or terminal with other associated
identifier information. A card value module 35 allows for defining
in each stored record a parameter corresponding to the value of
each respective stored-value card. That parameter could comprise a
monetary amount corresponding to the value of each respective
stored-value card or such parameter could comprise time units
corresponding to the value of each respective stored-value card, or
both. The card value module 35 may also allow for defining the
parameters or methods by which a card's value can be changed.
[0034] Stored-value card data transmitted over the communications
network may be received by input/output module 33 so that a first
processing module 30 may process a request of stored-value card
activation to the central processor from a respective requesting
terminal. The central processor thus allows for accepting or
declining an activation request, or other processing request, based
on whether the request is from a trusted source or whether the
request is transmitted over a trusted communications network.
[0035] The processing modules may also comprise modules for
changing value, refreshing value, redeeming value, switching the
value to another product, service, or currency, or otherwise
changing the status of the stored-value card. Other processing
modules can be considered. The refreshing module may change the
value of the card back to the card's original value. Alternately,
the refreshing module may add the card's original value to the
current value of the card. For instance, via the refreshing module,
a card with a current value of $15 and an original value of $20
could be increased to $20 (original value) or to $35 (current value
plus original value), depending on the type of refreshing module.
Generally speaking, values can be changed in predetermined
increments (like $10) or any amount that is not predetermined. The
redeeming module may refund to the customer the value of the card
or a portion of the value of the card, or it may provide a monetary
or other credit to the customer's account. It may also convert the
value of the card into other goods or services offered by the
merchant, merchant partner(s), or any other entity associated with
the sale of the card, including the central processing station.
[0036] In one aspect of the present invention, the stored-value
card may only be authorized if the request is made by any of a set
of trusted sources, or made through a communication that travels
over a trusted communications network. Through means described
above, terminals that are trusted sources can be associated with
respective identifiers by the associating module 36. However,
trusted sources may not have any associated identifiers before a
given transaction; instead, trusted sources may be verified to be
trusted sources through means described herein.
[0037] As further shown in FIG. 5, data from the terminal is
received at the I/O module 33. In one embodiment, information about
the communications network used to make the request can be
identified to the first processing module 30 based on the source of
the request signal received at the I/O module 33. For instance, a
dedicated data line may have a dedicated input at the I/O module
33, and requests made over the dedicated line will therefore be
recognized to be transmitted by the dedicated data line because
they are received at the 1/O module 33 through the dedicated input.
Alternately, a dedicated data line can carry or add identification
information as an addition to the request communication. For
instance, a dedicated data terminal can be preconfigured to
transmit the series of numbers "1234567" before or after every
merchant terminal communication in order to identify that the
merchant terminal communication is being transmitted over the
dedicated data line. In this embodiment, the central processor 16
can then determine that the request was made over a dedicated line
by analyzing the information identifying the dedicated data
line.
[0038] A first processing module 30 configured to process a request
of stored-value card activation will analyze this data and send
back either an authorization or a disapproval to the requesting
terminal. For instance, a first processing module 30 can access the
database through the I/O module 33 and compare the information of
the terminal with a list of trusted sources stored in the database.
If the information of the terminal matches a trusted source data
entry in the database, the request will be authorized. If
authorized, a database coupled to the central processor can be
updated to reflect any authorization or disapproval. A similar
process can be used when information is received over a trusted
communications network. The first processing module 30 identifies
the communications network used to make the request and grants the
request if it determines that the communications network is a
trusted one. The first processing module 30 can make this
determination by itself or by comparing identification information
of the communications network to a list of trusted communications
networks stored at the database 18.
[0039] As further shown in FIG. 5, a second processing module 31
allows for processing a request for changing the value associated
with a respective stored-value card. The request is transmitted
over the communications network to the central processor from a
respective requesting terminal. The central processor thus further
allows for accepting or declining the change value request based on
whether the respective identifiers stored in the record for the
stored-value card whose associated value is to be changed match the
identifiers actually transmitted by the requesting terminal for
that stored-value card and terminal. A third processing module 32
allows for processing a request of stored-value card deactivation
to the central processor from a respective requesting terminal. In
this case, the central processor is configured to accept or decline
the deactivation request based on whether the request is from a
trusted source or whether the request is transmitted over a trusted
communications network.
[0040] FIG. 6 illustrates an exemplary flow chart 100 such as may
be implemented by a stored-value card data management system
embodying one aspect of the present invention. The method described
in this flowchart is preferably used when a requesting terminal has
already been assigned an associated identifier, such as the number
456 as used in the following example. As shown in step 52, a
stored-value card serial No. 123 is associated with terminal No.
456. In step 53, a request for activation of stored-value card
serial No. 123 is processed. In one embodiment, it may be processed
as follows. A verification module would allow for determining
whether that request came from terminal No. 456, as in step 54.
Then the verification module determines whether card 123 has been
assigned to the location containing No. 456, as shown in step 55.
If the verification module determines that in fact such request was
generated from terminal No. 456, and card 123 has been assigned to
the location containing terminal 456, then the central processor
would generate a message indicating that the request has been
accepted, as in step 57. If the verification module determines that
the requesting terminal is other than No. 456, or if the card is
not assigned to the location, then a message would be issued
declining the transaction, as shown in step 56.
[0041] FIG. 7 illustrates an exemplary flow chart 101 such as may
be implemented by a stored-value card data management system
embodying one aspect of the present invention. As shown in steps 64
and 65 of FIG. 7, a terminal with no associated identifier makes a
request for changing the status of a stored-value card with
exemplary serial No. 123, which serial number has not been
associated with any terminal. The request may then be processed as
follows. In step 66, a verification and/or authorization module
would allow for determining whether the request originated from a
trusted source, such as a source identified in the central
processor's database. The operation of the verification module
depends on the type of communications network on which the request
was made, as shown further in FIG. 8. If the request is not from a
trusted source, then the request is denied or otherwise held or
halted in step 67. Appropriate action may then be taken, such as
attempting to identify or locate the requestor or merchant
terminal, or invalidating the stored-value card with the identified
serial number.
[0042] If the request is determined to be from a trusted source,
then the request will continue to be processed. As shown in step
68, the unidentified merchant terminal may then be assigned an
identifier, and the identifier may then be associated with the
stored-value card identifier as in step 69. The request is then
processed and/or accepted in step 70.
[0043] FIGS. 8A, 8B and 8C illustrate various exemplary
communications networks, which can be used to verify that a request
is made from a trusted source. In FIG. 8A, a merchant data channel
interface 12A communicates with a central processing apparatus 17,
which can be a central processor, host bank, or other centralized
entity, via a dedicated data channel between a merchant and the
central processing apparatus, such as dedicated telephone line 10A.
Because the communications network is a dedicated data channel,
only the merchant and the central processing apparatus have access
to the communications network, in addition to those entities that
may be granted access to the communications network by the merchant
and central processing apparatus. Thus, the central processor
authorizes all requests made over the dedicated data channel
because such requests are deemed to be from a terminal affiliated
with the trusted merchant who has access to the dedicated line. In
this embodiment, the central processing apparatus determines that
the request is from a trusted source if the request is received
over a dedicated data source.
[0044] It may be appreciated that the central processing unit 16
can then add the requestor to the list of trusted sources by
storing information identifying the trusted source in the database
18. This could be accomplished by assigning an identifier, such as
a password or code, to the requestor and storing said identifying
information in the database 18 as a trusted source. Then, if the
requestor later makes a request over a communications network that
is not considered a trusted communications network, like a public
switched telephone network, then the requestor can identify itself
over the network while making a request. The central processor 16
can then determine that the requestor is a trusted source and
accordingly grant the request. That requestor may then be
classified as a trusted source for subsequent transactions so that
future requests will be automatically granted.
[0045] One way the processor can determine that future requests
from a particular trusted requestor are indeed from the trusted
requestor is to assign identifying information to the requestor at
the time the requestor is first determined to be a trusted source,
such as when the requestor makes a request over a trusted
communications network like a dedicated data line. In this
embodiment, the processor 16 communicates the identifying
information to the requestor over the communications network 10 and
also stores the information in its database 18. When the trusted
source makes subsequent requests over any communications network,
it includes the identifying information in its request to the
processor 16. The processor receives the request with the
accompanying identifying information. It can then compare the
identifying information to the records stored in the database 18.
By comparing the identifying information to the identifying
information stored in the database 18, the processor can determine
whether the merchant is a trusted source.
[0046] In one exemplary embodiment of FIG. 8A, ABC Stores, Inc.
("ABC"), a hypothetical trusted source, has a dedicated data line
connecting one or more of its merchant terminals to a central
processing apparatus. ABC opens a new ABC store with new merchant
terminals that are as yet unknown to the central processing
apparatus. In particular, the ABC store has been assigned no
identifying information, and the database does not contain any
information specifically identifying this particular ABC store. The
unidentified terminal of the new store makes a request over the
dedicated line. Although the central processing apparatus has never
verified the identity of the new ABC terminals, the central
processing apparatus will process and grant the request because it
treats all requests made over ABC's dedicated line as a request
made by a trusted source. In effect, any requestor on a dedicated
line is automatically a trusted source. Other embodiments can be
considered.
[0047] However, in another exemplary embodiment, the new ABC store
terminal must first obtain an identifier before its request can be
granted. Upon receiving the request and determining that the
request was received over a dedicated line that is a trusted
source, the central processing apparatus assigns an identifier to
the requesting terminal and associates the identifier with the
stored-value card's identifier. Then the request can be processed
and the card can be activated. Other embodiments can be
considered.
[0048] In another embodiment, the central processing apparatus sets
up an identifier before the request. For instance, ABC notifies the
central processor that a new ABC store is opening soon, and an
identifier is reserved for that new ABC store in the event that a
terminal at the new ABC store makes a request. Then when the
requesting entity makes a request, the requesting identity is
already identified. In this instance, the request could be
processed without the step of assigning an identifier to the new
terminal. However, additional identification could be added and/or
assigned at the time of the first request as needed. For instance,
the new store could be issued a default password, and then the new
store could request and/or obtain a new password when it makes its
first request to the central processor.
[0049] In FIG. 8B, an unidentified merchant with a unique phone
number 12B communicates a request for a stored-value card to a
central processing apparatus 17, such as a central processor 16,
over a public switched phone line 10B. Such communication may use a
modem, an interactive voice response system (IVR), or any other
means of communicating over a public switched telephone network.
The central processing apparatus can identify the unique phone
number of the merchant based on the DNIS and ANI numbers that are
carried on regular phone calls. Similarly, the "caller ID" feature
can be used to identify the phone number of entities contacting a
remote entity over a public switched phone line. The central
processing apparatus can then determine if the identified phone
number is a trusted source by comparing the merchant terminal's
phone number with the phone numbers of the trusted sources stored
in the database 18. If the central processing apparatus 17
determines that the phone number does belong to a trusted source,
then the central processing apparatus 17 will process and grant the
request. Otherwise, the request may be rejected.
[0050] Other methods of identifying merchant terminals can be
considered.
[0051] In the embodiment of FIG. 8B, the merchant 12B communicates
a request for a stored-value card to a central apparatus over a
public switched phone line 10B. The merchant 12B enters a password
or other identifying information over the phone line, such as by
transmitting a series of tones during a phone call with a central
processing apparatus 17. Other methods of communicating
identification information over a phone line can be considered,
such as by fax or interne communication. The central processing
apparatus 17 then compares the identifying information of the
merchant 12B with identifying information of the trusted sources
listed in the database 18. Based on the comparison, the central
processing apparatus determines whether the merchant 12B is a
trusted source. If the central processing apparatus 17 determines
that the merchant 12B is a trusted source, then the central
processing apparatus 17 will process and grant the request.
Otherwise, the request may be rejected. Other embodiments can be
considered.
[0052] In FIG. 8C, a merchant computer terminal with a static IP
(interne protocol) address submits a request by communicating with
the central processing apparatus 17 via the internet 10C. Through
methods well known in the art, a merchant computer terminal can
connect to the internet through a modem, LAN, WAN, cable
connection, or other internet connection. The merchant terminal is
assigned a static IP address by its internet service provider,
which could be a merchant, merchant group, or another service
provider. The merchant terminal 12C communicates a request to the
central processing apparatus 17. Through methods well known in the
art, the central processing apparatus 17 determines the static IP
address of the terminal 12C based on the received electronic
communication. By comparing the static IP address with the static
IP addresses of trusted sources, the central processing apparatus
17 can determine if the terminal 12C is a trusted source. If it is,
then in a method similar to that described above for FIGS. 8A and
8B, the central processing apparatus 17 processes the request and
activates the card. If it is not determined to be a trusted source,
then the request may be rejected.
[0053] In one embodiment, the request is accompanied by information
identifying the merchant computer terminal 12C. For instance, the
merchant terminal 12C may enter a password, which is transmitted
from the merchant computer 12C with a static IP address to the
central processing apparatus 17. Through methods described above,
the central processing apparatus 17 can then determine whether the
merchant terminal 12C is a trusted source based on the password. If
the merchant computer 12C is a trusted source, then the IP address
may become a trusted source, such as by storing the IP address in
the list of trusted sources in the database. However, because in
some cases a given merchant computer 12C may have a different IP
address the next time it logs onto the internet, the central
processing apparatus 17 may purge such static IP addresses unless
the merchant computer 12C is otherwise known to have a permanent
static IP address.
[0054] In another embodiment, the central processing apparatus 17
does not store the IP address as a trusted source. In this
embodiment, verification of the identification at the beginning of
the request is sufficient to authorize the transaction, and no
further authorization steps are necessary. Other embodiments can be
considered.
[0055] In one embodiment, due to an arrangement with the merchant
terminal's 12C internet service provider, the merchant has the same
static IP address for every internet session. The central
processing apparatus 17 stores this address in the database as an
identifier for a trusted source. The merchant 12C makes a request
over the internet from the same static IP address, and the central
processing apparatus 17 processes and grants such request after it
identifies the request as originating from a trusted static IP
address, such as a trusted static IP address of a merchant terminal
12C.
[0056] In another embodiment, the merchant 12C will be assigned one
of a set of static IP addresses, each of which are trusted sources.
The merchant 12C can then make requests that will be processed, as
described above, because it will always make such request using a
static IP address that is a trusted source.
[0057] FIG. 9 shows an exemplary user tree and communication path
between a merchant terminal and the host bank and central
processor. As illustrated in FIG. 9, point-of-sale terminals 12 can
communicate with the host bank and central processor by interfacing
first with a merchant communication interface 12D. The merchant
communication interface 12D can be connected to any number of
point-of-sale terminals 12, which in turn can be connected to any
number of merchants. The merchant communication interface 12D may
itself be a point-of-sale terminal 12. For instance, the
point-of-sale terminals 12 and the merchant communication interface
12D may be computers connected on a LAN (local area network) or a
WAN (wide area network). Communications from multiple terminals 12
may first pass through a merchant network hub before the
communications leave the merchant and pass through other
communications networks such as the internet, a dedicated line, or
an outside phone system.
[0058] Alternately, in FIG. 9, as in FIGS. 1 and 2, the
point-of-sale terminal can interface directly with the
communications network.
[0059] It must be noted that in the above FIGS. 7-9, the requesting
terminal or other requesting entity may not have a prior identifier
associated with it before the first request. Thus, to this extent,
the requesting entity is not identified to the central processor
and host bank. However, other information may already be known
about the requesting entity. In the ABC example described for FIG.
8A above, the data management system 14 could already determine
that the requestor was an ABC entity, such as an ABC store
terminal, because only ABC entities have access to the dedicated
line. It should be appreciated that the step of associating an
identifier with a previously unidentified terminal can be removed
entirely. It should also be appreciated that these methods apply
equally to the request/activation process over phone lines and the
internet.
[0060] Those skilled in the art may also appreciate that the
service provider and/or card value can be chosen by the user upon
purchase or activation, or at any time chosen by the user. When the
requesting entity such as a merchant terminal requests a card or
PIN, the requesting entity asks for a specific dollar, minute, or
other value for the card. The central processor could then simply
alter the existing record for the card, if one exists, in order to
reflect a higher or lower dollar amount as requested by the user
over the communications network. E.g., a customer could request
that a given amount, such as $50, be assigned to a particular card.
During the process of authenticating the transaction, the central
processor could edit its records to reflect the new card value.
Thus, card values can be variable. This is true whether the card
values are initially fixed, or whether their value is unidentified
and unassigned until the point of sale. Similarly, in the case of
telecommunications service or any other kind of user services
applicable to stored-value cards, the user may select the service
provider at the point of sale, or later if the card must be
redeemed by the user at a later date. At any point when the user
interacts with the central processor, that processor has the
ability to amend and alter the identifiers associated with a card
as well as any other associated information, such as the card's
current value or face value.
[0061] The stored-value card data management system in one
exemplary embodiment enables a web-based, ID and password protected
application available to anyone with internet access and the
appropriate ID and Password. As described-above, the system
comprises respective modules for card generation, merchant
establishment, location establishment, terminal setup, and
inventory assignment to merchants and/or locations. The system may
also be used for other card-related actions, such as web-based
activation, deactivation, value change, refresh, and value
redemption.
[0062] The present invention can be embodied in the form of
computer-implemented processes and apparatus for practicing the
processes described above. The present invention can also be
embodied in the form of computer program code containing
computer-readable instructions embodied in tangible media, such as
floppy diskettes, CD-ROMs, hard drives, or any other
computer-readable storage medium, wherein, when the computer
program code is loaded into and executed by a computer, the
computer becomes an apparatus for practicing the invention. The
present invention can also be embodied in the form of computer
program code, for example, whether stored in a storage medium,
loaded into and/or executed by a computer, or transmitted over some
transmission medium, such as over electrical wiring or cabling,
through fiber optics, or via electromagnetic radiation, wherein,
when the computer program code is loaded into and executed by a
computer, the computer becomes an apparatus for practicing the
invention. When implemented on a general-purpose computer, the
computer program code segments configure the computer to create
specific logic circuits or processing modules.
[0063] FIG. 10 is an exemplary flow chart illustrating another
aspect of the present invention as may be implemented by the system
of FIG. 3. In step 71, a person(s), processor, computer, or other
entity identifies one or more trusted sources that are authorized
to make stored-value card requests. The trusted sources may
include, in a preferred embodiment, a list of merchants authorized
to request PINs. Similarly, in step 72, an entity identifies one or
more trusted communications networks that are known to carry or
transmit only valid stored-value card requests. The trusted
communications networks may include, in a preferred embodiment, a
list identifying the various dedicated data lines connecting
authorized merchants or merchant terminals to the central
processor. Steps 71 and 72 are described separately, but it should
be understood that these two steps need not be done in order.
Further, the system should be constantly updating its list of
trusted sources as new sources and networks are determined to be
trusted sources.
[0064] In step 73, an entity such as the central processor 16
assigns identification information to the identified trusted
sources and identified trusted communications networks. The
identification information may be a merchant terminal ID number or
other identifier, such as a static IP address or phone number. For
communications networks, the identifier may be an internal code
used to identify a particular communications network from another
network. For instance, different communications networks that have
different inputs into the processor system can be identified by
assigning different numbers to the different inputs. In step 74,
the identifiers are stored in a database 18. It should be noted
that communications networks may not have identifiers in the
traditional sense of the word, and such identifiers may not be
amenable to storing in a database. For instance, trusted
communications networks may be identified by virtue of having a
different connection or input to the processor than communications
networks that are not trusted, and thus they can be identified by
virtue of having the separate connection.
[0065] In step 75, a request is received from a merchant terminal.
Here, merchant terminal can mean any entity that submits a request
to the processor. In step 76, the processor determines whether the
request is from a trusted source, i.e., whether the requesting
merchant terminal is a trusted source. The processor can make its
determination based on information identifying the requestor. For
instance, requestors can be verified to be trusted sources by
correctly entering a password over a phone network. Phone
requestors can also be verified by determining that the requestor's
phone number is listed in the database as a trusted source.
Requestors who request over the internet can be verified by having
made the request from a trusted static IP address, or from a static
IP address known to have previously submitted a correct password.
The processor verifies the sources by comparing their identifier
information such as passwords with the identification information
stored in the database 18.
[0066] The processor also determines whether the communications
network carrying the request is a trusted communications network.
If the request carries an identifier that identifies the
communications network, the processor can compare the identifier
with the trusted identifiers in the database. This verification
process can also be done by simply determining how the request
arrived at the processor. For instance, if input #3 is a trusted
source and the processor determines that the request arrived via
input #3, then the processor can determine that the request was
carried by a trusted source. Other methods can be used, which are
well-known in the art.
[0067] If the request is determined to be from either a trusted
source or a trusted communications network, then the request is
processed and granted in step 77. If the request is not determined
to be from a trusted source or trusted communications network, then
in step 78 the request may be denied, other means of verification
can be pursued, or the request can be put into a hold category.
[0068] Other embodiments can be considered. For instance, for many
of the embodiments described above, the request can be any request,
including a request for activation, deactivation, value change, or
another request.
[0069] It will be understood that the specific embodiment of the
invention shown and described herein is exemplary only. Numerous
variations, changes, substitutions and equivalents will now occur
to those skilled in the art without departing from the spirit and
scope of the present invention. Accordingly, it is intended that
all subject matter described herein and shown in the accompanying
drawings be regarded as illustrative only and not in a limiting
sense and that the scope of the invention be solely determined by
the appended claims.
* * * * *