WO2010054259A1 - Service d’intermédiaire et procédé pour traiter des données de transaction financière avec confirmation par dispositif mobile - Google Patents

Service d’intermédiaire et procédé pour traiter des données de transaction financière avec confirmation par dispositif mobile Download PDF

Info

Publication number
WO2010054259A1
WO2010054259A1 PCT/US2009/063641 US2009063641W WO2010054259A1 WO 2010054259 A1 WO2010054259 A1 WO 2010054259A1 US 2009063641 W US2009063641 W US 2009063641W WO 2010054259 A1 WO2010054259 A1 WO 2010054259A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
customer
information
authorization request
mobile device
Prior art date
Application number
PCT/US2009/063641
Other languages
English (en)
Inventor
Todd Russell Coulter
Mordechai E. Kaplinsky
Christopher Ethan Lewis
Original Assignee
Fonwallet Transaction Solutions, Inc.
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
Priority claimed from US12/557,453 external-priority patent/US8244643B2/en
Application filed by Fonwallet Transaction Solutions, Inc. filed Critical Fonwallet Transaction Solutions, Inc.
Publication of WO2010054259A1 publication Critical patent/WO2010054259A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • Convenience is also a major concern for consumers.
  • the average consumer may pay for purchases using multiple payment instruments, such as credit cards, debit cards, and gift cards.
  • Each payment instrument has a separate card or token and a separate set of identifying information, such as credit/debit card numbers, that must be tracked.
  • Managing multiple payment instruments can therefore be complicated and cumbersome. Thus, it would be useful to consumers to be able to manage multiple payment instruments in a simple fashion.
  • Figure 1 is a block diagram of a representative environment for processing financial transaction data according to prior art methods.
  • Figure 2A is a block diagram that illustrates communication steps for sending an authorization request to an intermediary service.
  • Figure 2B is a block diagram that illustrates a two-step authorization process performed by the intermediary service.
  • Figure 2C is a block diagram that illustrates a process for authorizing a transaction using a modified authorization request.
  • Figures 3A-3D are representative user interfaces presented to a customer of a mobile device during a financial transaction.
  • Figure 4 is a block diagram of a representative server architecture.
  • Figure 5 is a logical block diagram of the intermediary service.
  • Figures 6A and 6B are a flow chart of a process for processing financial transaction data executed by an intermediary service.
  • Figure 7 is a flowchart of a process for processing financial transaction data executed by an acquirer.
  • Figure 8 is a logical block diagram of the acquirer.
  • Figure 9 is a block diagram of encrypted message routing through the intermediary service.
  • a transaction processing service that operates as an intermediary between acquirers of financial transaction requests and issuing institutions that process the financial transaction requests is disclosed (hereinafter referred to as “the intermediary service” or “the service”).
  • the intermediary service utilizes a customer's mobile device as an out-of-band communication channel to notify a customer of a received financial transaction request.
  • the service must first receive the customer's confirmation of the transaction.
  • the disclosed intermediary service thereby significantly reduces the occurrence of fraud without changing or otherwise burdening standard merchant payment processes.
  • a customer presents a card or token containing unique identifying information to a merchant in order to pay for a purchase.
  • the token may be, for example, an RFID tag or other contactless device for providing the unique identifying information and may be contained in or attached to the customer's mobile device.
  • the merchant transmits the unique identifying information to an acquirer (i.e., a financial institution that provides a clearinghouse service for consolidating financial transactions) in an initial authorization request.
  • the acquirer recognizes that the initial authorization request is associated with the intermediary service based on the unique identifying information, and transmits at least part of the initial authorization request to the intermediary service.
  • the intermediary service authenticates the request and retrieves stored customer information from a
  • the stored customer information includes an address of the customer's mobile device, a reference to one or more payment instruments associated with the customer, and a verification code associated with the customer's intermediary service account.
  • the intermediary service uses the retrieved address of the device to transmit a transaction notification message to the customer's mobile device.
  • the transaction notification message may include the name or location of the point of purchase, the transaction amount, a listing of payment instruments that may be used to pay for the transaction, and/or other pertinent characteristics of the transaction.
  • the transaction notification message may also specify a required response from the customer. The required response may vary depending on the requesting merchant, the type of transaction, the amount of the transaction, or other factor associated with the transaction (e.g., the type of goods or services being sold, an assessment of the likelihood of fraud, etc.).
  • a low-price transaction may require no response
  • a higher value transaction may require that the customer confirm the transaction
  • a still higher value transaction may require that the customer confirm the transaction and provide a verification code in response to the transaction notification message.
  • the transaction notification message is presented to the customer on the mobile device.
  • the intermediary service may also support fallback methods for transmitting the transaction notification message to the customer in the event that the primary method of sending the message to the customer is not available.
  • the customer's response is received by the mobile device and transmitted to the intermediary service.
  • the intermediary service continues processing of the initial authorization request based on the customer's response. If the customer fails to respond to the transaction notification message, rejects the transaction, or provides an incorrect verification code, the intermediary service sends a denial message to the acquirer and the transaction fails.
  • the intermediary service transmits an information request to the issuing institution of a payment instrument that is to be used to complete the transaction. In response to the
  • the issuing institution provides account information for the selected payment instrument.
  • the intermediary service forwards the account information to the acquirer, which generates a modified authorization request based on the received account information.
  • the acquirer then sends the modified request to the associated payment association in accordance with its standard practices.
  • the intermediary service allows a customer to easily select among multiple payment instruments while using a single token or identifier at the time of payment.
  • the provided account information may include additional verification that enables the payment association to process the transaction with a lower fee.
  • the intermediary service may maintain a record of a set of payment instruments that are available to each customer for purposes of a transaction.
  • One or more payment instruments may be automatically selected for each transaction based on rules that are defined by the intermediary service, by the customer, or by the merchant.
  • a customer may be allowed to select a payment instrument from a list of payment instruments that are provided in a transaction notification message that is transmitted by the service to the customer.
  • the selected payment instrument or payment instruments determine the issuing institution or institutions to which the intermediary service sends the information request.
  • a customer may provide the unique identifying information to an online merchant via a computer interface, such as via a checkout process implemented on a web site.
  • the online merchant transmits the unique identifying information to an acquirer (i.e., a financial institution that provides a clearinghouse service for consolidating financial transactions) in an initial authorization request.
  • the transaction is then processed by the intermediary service in a similar manner to transactions received from a brick-and-mortar merchant.
  • the online merchant may bypass the acquirer by transmitting the information directly to the intermediary service.
  • the transaction may then be processed by the intermediary service as discussed above, with the online merchant acting in the acquirer's role.
  • the account information may be transmitted through the intermediary service from a financial institution to an acquirer.
  • the intermediary service may allow customers to request payment with a debit card that requires a PIN or other unique code. Rather than having the customer enter the PIN or unique code, the PIN or code is transmitted by a financial institution across the intermediary service in an encrypted manner such that it cannot be utilized by the service. Only the intended receiving party has the necessary information to decrypt and use the received PIN or code. In this manner, customers are able to utilize the intermediary service for transactions like debit purchases. Such transactions are normally not available in certain environments because of rules pertaining to the handling and processing of PINs.
  • FIG. 1 is a block diagram of a representative environment 100 in which various parties process financial transaction data according to prior art methods.
  • a transaction is initiated in step 1 when a customer 102 tenders a credit or debit card 104 at a point of purchase associated with a merchant 106.
  • point of purchase refers to any point where a card is used to pay for a good or service.
  • a point of purchase may include, for example, a store, a vending machine, an online retailer, a restaurant, a contractor, a provider of services, etc.
  • the customer 102 or the merchant 106 may swipe the card 104 through a card reader and, if required, enter a PIN or code.
  • the customer 102 may provide a card number, associated name, and/or other identifying
  • the identifying information that is obtained from the card depends on the type of transaction and the available systems for reading the card.
  • Standard credit and debit cards include several sets of information referred to as Track 1 and Track 2.
  • Track 1 is considered public, while the data on Track 2 is considered private and must be transmitted using special security protections dictated by the issuing bank or the payment association (e.g., Visa, MasterCard, etc.). However, transaction fees are lower if data from Track 2 is also provided. Because of the security restrictions and the lack of a reader that can read the tracks, data from Track 2 is generally not available for online, mail order, or telephone transactions (generally referred to as "card not present transactions").
  • the merchant 106 in step 2 sends an authorization request to an acquirer 108.
  • the authorization request includes transaction information such as the identifying information, point of purchase information (e.g., a merchant's name or identifier), and the transaction details (e.g., price, products, quantities, fees and taxes).
  • the acquirer 108 is generally a separate financial institution that functions as a clearinghouse for many electronic transactions.
  • the acquirer 108 in step 3 forwards the authorization request to a payment association 112, which forwards the request to an issuing institution 110 in step 4.
  • the issuing institution 110 may be, for example, a bank or other institution that provided the credit or debit card.
  • the issuing institution 110 After receiving the authorization request, the issuing institution 110 evaluates the request by verifying the identifying information and the transaction amount. The issuing institution 110 then authorizes the transaction in step 5 by transmitting an authorization message to the payment association 112, which forwards the message to the acquirer 108 in step 6. In step 7, the acquirer 108 forwards the authorization message to the point of purchase 106, which records the completed transaction. At a later time, the issuing institution 110 provides payment for the transaction by transmitting the funds in step 8 to the payment association 112, which forwards the payment to the acquirer 108 in step 9. In the final step, the acquirer forwards the funds to the point of purchase 106 in step 10.
  • Figures 2A, 2B, and 2C illustrate an environment 200 in which an intermediary service 204 operates and depicts the order in which various service and system modules involved in the transaction communicate in order to authorize and
  • FIG. 2A illustrates the communication steps for sending an initial authorization request to the intermediary service.
  • a transaction begins in step 1 when a customer 102 uses a token 202 to provide unique identifying information to the merchant 106 at a point of purchase (POP) in order to make a purchase.
  • POP point of purchase
  • token is a generic term that refers to various means for providing the unique identifying information to the merchant 106.
  • a token may be a magnetic strip on a credit or debit card, a radio frequency identification (RFID) tag embedded in a card or mobile device, an optical pattern that is scanned by a scanner (e.g., a bar code) or similar or different technologies for conveying identifying information to the merchant.
  • RFID radio frequency identification
  • the identifying information may be provided at the point of purchase by swiping a card or by the customer 102 providing the information such as by typing identifying information using a keyboard (e.g., when purchasing at a website).
  • the point of purchase may alternatively receive the information by detecting, through the use of a radio frequency identification (RFID) reader, an RFID token or other identification token associated with the card or with the customer's mobile device.
  • RFID radio frequency identification
  • the token 202 may be issued by the intermediary service 204 and is generally not associated with the customer's credit or debit cards.
  • the unique identifying information may be an alpha-numeric code, a sixteen digit number similar to a credit card number, or one or more pieces of data that uniquely identifies the customer.
  • the point of purchase 106 then generates the initial authorization request based on the received identifying information, point of purchase information, and transaction information and transmits the initial authorization request to the acquirer 108 in step 2.
  • the initial authorization request includes a unique transaction identifier. The transaction identifier may be retained throughout the authorization process such that every participant can use it to identify the transaction.
  • the acquirer 108 in step 3 sends at least part of the data from the initial authorization request to the intermediary service 204.
  • the acquirer is able to route the initial authorization request to the intermediary service 204 because the identifying information transmitted in the authorization request identifies the initial authorization request as being associated with a customer 102 having an account
  • the intermediary service 204 After receiving the data from the initial authorization request from the acquirer 108, as will be discussed in additional detail herein, the intermediary service 204 authenticates the request to ensure that the request has been issued from a valid acquirer and the transaction is valid. Among other steps, the intermediary service 204 also retrieves customer information associated with the transaction.
  • the customer information includes an address of a mobile device that is associated with the customer, one or more payment instruments (e.g., credit cards, debit cards, bank accounts, etc.) that are associated with the token 202, and a verification code that is associated with the customer, the token, or with a particular payment instrument.
  • the customer information may also include any customer-defined rules on how such payment instruments are to be applied to the transaction.
  • FIG. 2B illustrates a two-step authorization process performed by the intermediary service.
  • the intermediary service 204 After authenticating the initial authorization request from the acquirer 108, at a step 4a the intermediary service 204 transmits a transaction notification message to a mobile device 206 that is associated with the customer.
  • the mobile device may be a mobile phone, a smart phone, a media player (e.g., an Apple iPod, or iTouch), a mobile game device (e.g. a Nintendo GameBoy, a Sony PSP), a personal digital assistant (PDA), an email device (e.g., a Blackberry), or any other device that may send and receive wireless transmissions.
  • the transaction notification message is transmitted to the mobile device via an XMPP message using the retrieved address of the mobile device.
  • the XMPP message may be sent using a data channel, such as a data network implementing TCP/IP provided by a wireless service provider.
  • the message may be sent to a standard TCP port, such as port 5222.
  • the retrieved address may be, for example, a telephone number, network address, or e-mail address associated with the mobile device.
  • the transaction notification message includes transaction information such as the amount, time, or location of the transaction.
  • the transaction notification message may also request the customer 102 to provide information to continue the transaction, such as to provide a transaction confirmation, a customer-specific, token-specific, or payment instrument specific) verification code, and/or a selection of a payment instrument to use for the transaction.
  • the intermediary service may support fallback methods for transmitting a transaction notification message to the customer. For example, in the event that the intermediary service is unable to communicate with the mobile device using an XMPP-formatted message, the service may also send the transaction notification message to the device using a short message service (SMS) message, an email message, or through another messaging channel.
  • SMS short message service
  • the intermediary service may call the mobile device (if the mobile device has voice capability) and may use an Interactive Voice Response (IVR) system to solicit the confirmation from the customers.
  • IVR Interactive Voice Response
  • the intermediary service 204 transmits the transaction notification message to a different device capable of receiving data messages that is associated with the customer, such as a personal computer.
  • the intermediary service may attempt to communicate with the user through a land-line telephone.
  • the intermediary service may maintain a prioritized list of fallback methods to use, and may proceed through the list until the transaction notification message is delivered to the customer or until a certain period has elapsed and the service declares a delivery failure.
  • Figures 3A-3D are representative screenshots of a transaction notification message that may appear to a customer of a mobile device. Although the figures depict each example message separately, portions of the messages shown in Figures 3A-3D may in some cases be combined in a single message.
  • Figure 3A depicts a representative screenshot 220 associated with a first notification message.
  • the notification message includes a region 222 that contains details of the financial transaction, such as a vendor (in the depicted example, a Barnes & Noble bookstore), a total amount being charged ($21.36), and a financial instrument that is being used to complete the transaction (a personal Visa card, automatically selected as a result of a service, customer, or merchant rule).
  • the service may not require a customer to confirm that the transaction should take place.
  • the notification message therefore includes a message 224 to the customer indicating that no response is required to approve the transaction. If, however, the customer is unaware of the transaction and therefore believes that the transaction may be a fraudulent one, the customer is
  • FIG. 3B depicts a representative screenshot 228 associated with a second notification message.
  • the notification message includes a region 222 that contains details of the financial transaction, such as a vendor (in the depicted example, a restaurant), a total amount being charged ($75.24), and a financial instrument that is being used to complete the transaction (a debit card, automatically selected as a result of a service, customer, or merchant rule).
  • a financial instrument that is being used to complete the transaction (a debit card, automatically selected as a result of a service, customer, or merchant rule).
  • the service may require a customer to confirm that the transaction should take place.
  • the notification message therefore includes a message 230 to the customer indicating that the customer must confirm or deny the transaction.
  • the customer may select a "confirm" button 232.
  • the customer By selecting the confirm button, the customer is able to notify the intermediary service that the transaction should proceed.
  • the customer selects the "deny" button 226. Selecting the deny button notifies the intermediary service that the transaction is fraudulent or in error and thereby cause the intermediary service to terminate the transaction.
  • FIG. 3C depicts a representative screenshot 234 associated with a third notification message.
  • the notification message includes a region 222 that contains details of the financial transaction, such as a vendor (in the depicted example, Office Depot), a total amount being charged ($132.16), and a financial instrument that is being used to complete the transaction (a business American Express card, automatically selected as a result of a service, customer, or merchant rule).
  • a financial instrument that is being used to complete the transaction (a business American Express card, automatically selected as a result of a service, customer, or merchant rule).
  • the service may require a customer to confirm that the transaction should take place by entering the customer's verification code.
  • the notification message therefore includes a message 236 to the customer indicating that the customer must enter the verification code.
  • a text entry box 238 is provided, which displays a default character (e.g., " * ”) as an additional security measure as the customer keys in their verification code.
  • a default character e.g., " * ”
  • the customer selects an "enter” button 240 to confirm the transaction. By selecting the enter button, the customer notifies the intermediary
  • Figure 3D depicts a representative screenshot 242 associated with a fourth notification message.
  • the notification message includes a region 222 that contains details of the financial transaction, such as a vendor (in the depicted example, a restaurant) and a total amount being charged ($75.24).
  • the fourth notification message includes a drop-down menu 244 that allows the customer to affirmatively select the desired payment instrument that the customer would like to use for the transaction. For example, the customer may select a direct transfer from a checking account (depicted), or any debit, credit, gift certificate, or other holder of value that is associated with the account of the customer at the intermediary service.
  • the customer then confirms that the transaction should proceed by selecting the "confirm" button 232.
  • the confirm button By selecting the confirm button, the customer is able to notify the intermediary service that the transaction should proceed using the selected financial instrument.
  • the customer selects the "deny" button 226. Selecting the deny button notifies the intermediary service that the transaction is fraudulent or in error and thereby cause the intermediary service to terminate the transaction.
  • the customer 102 uses the mobile device 206 to send a confirmation message.
  • a confirmation message is sent in a step 4b, and may confirm the transaction or deny the transaction in the transaction notification message. If the customer denies the transaction, the intermediary service ends further processing of the first authorization request and notifies the acquirer 108 that the request has been denied. The acquirer, in turn, notifies the merchant who then cancels the transaction.
  • the intermediary service 204 If, however, the customer confirms the transaction in the notification message from the mobile device 206, or if the notification message does not require a confirmation receipt from the customer (such as in the transaction notification message in Figure 3A) the intermediary service 204 generates an information request, which is used to obtain account information for a selected payment instrument. As described below, the account information is used to complete the process of authorizing the transaction. The information request is based on the initial authorization request, the customer's verification message, and the stored customer information. The information request is to be sent to the appropriate issuing institution with sufficient information to allow the issuing institution to provide the correct account information in response to the request.
  • the intermediary service 204 may automatically determine which payment instrument is to be used for the transaction. The determination may be based on default rules that are maintained by the service. For example, the service may require that all transactions below a certain dollar value be processed as a debit transaction, and all transactions above the certain dollar value be processed as a credit card transaction. The determination may be based on rules that are specified by the merchant associated with the transaction. For example, a merchant may only accept a certain type of charge card and the customer may be required to use the charge card that is accepted by the merchant.
  • the determination may also be based on rules that are defined by the customer, such as the use of one payment instrument for charges at restaurants and the use of another payment instrument for charges everywhere else.
  • the customer may define processing rules based on many different factors, such as the location of the purchase, the point of purchase, and the day or date of the purchase.
  • a customer might specify that a business credit card should be used for transactions occurring during regular business hours on weekdays, while a personal credit card should be used for transactions occurring on a weekend or after normal business hours on a weekday.
  • the transaction notification may be used for transactions occurring during regular business hours on weekdays, while a personal credit card should be used for transactions occurring on a weekend or after normal business hours on a weekday.
  • the intermediary service 204 transmits the information request to an issuing institution 110 associated with the selected payment instrument. If the intermediary service is integrated with the issuing institution, the request may be directly sent to the issuing institution 110 in step 5a.
  • the issuing institution 110 responds to the information request by providing account information associated with the selected payment instrument.
  • the account information is encrypted such that the information can be decrypted by the acquirer 108 but not by the intermediary service 204. This provides additional security by reducing the number of entities that have access to the account information.
  • the intermediary service 204 decrypts the account information after receiving it from the issuing institution and provides the account information to the acquirer using its own encryption key. Because the account information is obtained directly from the issuing institution, it may also include Track 2 information for the payment instrument, which increases the security and reduces the cost of the transaction.
  • the intermediary service 204 After obtaining the account information from the issuing institution 110, the intermediary service 204 in step 7 sends the account information to the acquirer 108. As discussed below, the acquirer 108 then generates a modified authorization request based on the initial authorization request and the received account information associated with the selected payment instrument. In some embodiments, this is done by replacing the identifying information in the initial authorization request with the account information.
  • the intermediary service 204 may obtain the necessary account information from a secure storage provider 208.
  • the secure storage provider 208 is a data storage service that stores account information for payment instruments in a similar fashion to the issuing institution to enable the intermediary service to proceed with the transaction.
  • the account information may be provided to the secure storage
  • WO00/LEGAL17266250.1 -14- 11/6/09 provider 208 at any time prior to the transaction, such as when the customer initially registers with the intermediary service.
  • a request is made to the secure storage provider 208 for account information associated with the customer's selected payment instrument.
  • the secure storage provider responds with the account information.
  • the intermediary service 204 then provides the account information to the acquirer 108, which generates the modified authentication request as if the information had been obtained from the issuing institution 110.
  • FIG. 2C illustrates a process for authorizing a transaction using a modified authorization request.
  • the process is executed in a similar manner to the process in Figure 1.
  • the acquirer sends the modified authorization request to the payment association 112, which in step 9a sends the request to the issuing institution 110 associated with the selected payment instrument.
  • the issuing institution 110 authorizes the transaction based on the information in the modified authorization request (i.e., the account information provided through the intermediary service 204).
  • step 9b the issuing institution 110 transmits an authorization message to the payment association 112, which forwards the authorization message to the acquirer 108 in step 8b.
  • the acquirer 108 transmits the authorization message to the point of purchase 106, which records the transaction.
  • the acquirer 108 also sends a copy of the authorization message or other transaction information (e.g., items purchased) to the intermediary service 204.
  • the intermediary service 204 may then send a receipt message to the mobile device 206 to indicate that the transaction was authorized.
  • FIG. 4 is a high-level block diagram showing an example of the architecture of a server 300.
  • One or more servers 300 may be utilized by, for example, the intermediary service 204 or the acquirer 108 to implement the transaction processing depicted in Figures 2A-2C.
  • the server 300 includes one or more processors 302 and memory 304 coupled to an interconnect 306.
  • the interconnect 306 shown in Figure 4 is an abstraction that represents any one or more separate physical buses, point-to-point connections, or both connected by appropriate bridges, adapters, or controllers.
  • the interconnect 306, therefore, may include, for example, a system bus, a Peripheral Component Interconnect (PCI) family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI family bus, a PCI
  • ISA industry standard architecture
  • SCSI small computer system interface
  • USB universal serial bus
  • MC (12C) bus or an Institute of Electrical and Electronics Engineers (IEEE) standard 1394 bus, sometimes referred to as "Firewire”.
  • IEEE Institute of Electrical and Electronics Engineers
  • the processor(s) 302 may include central processing units (CPUs) of the server 300 and, thus, control the overall operation of the server 300 by executing software or firmware.
  • the processor(s) 302 may be, or may include, one or more programmable general-purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application specific integrated circuits (ASICs), programmable logic devices (PLDs), or the like, or a combination of such devices.
  • the memory 304 represents any form of random access memory (RAM), read-only memory (ROM), flash memory, or the like, or a combination of such devices.
  • the software or firmware executed by the processor(s) may be stored in a storage area 310 and/or in memory 304, and typically includes an operating system 308 as well as one or more applications 318. Data 314 utilized by the software or operating system is also stored in the storage area or memory.
  • a network adapter 312 is connected to the processor(s) 302 through the interconnect 306. The network adapter 312 provides the server 300 with the ability to communicate with remote devices, such as clients, over a network 316 and may be, for example, an Ethernet adapter.
  • FIG. 5 illustrates a logical block diagram of the intermediary service 204.
  • the intermediary service 204 receives an initial authorization request from the acquirer 108 and executes additional steps to notify the customer of the transaction and receive the customer's verification of the transaction.
  • the intermediary service 204 also requests account information from the issuing institution 110 and provides the account information to the acquirer 108. Aspects of the service may be implemented as special purpose hard-wired circuitry, programmable circuitry, or as a combination of these.
  • the intermediary service 204 includes a number of modules to implement the functions of the service.
  • the modules and their underlying code and/or data may be implemented in a single physical device or distributed over multiple physical devices and the functionality implemented by calls to remote
  • the code to support the functionality of the service may be stored on a computer readable medium such as an optical drive, flash memory, or a hard drive.
  • a computer readable medium such as an optical drive, flash memory, or a hard drive.
  • ASICs application- specific integrated circuits
  • programmable logic programmable logic
  • general-purpose processor configured with software and/or firmware.
  • the intermediary service 204 receives an initial authorization request from the acquirer 108 and transmits an information request to the issuing institution 110.
  • the intermediary service 204 receives account information in response to the information request and provides the received account information to the acquirer 108.
  • the intermediary service 204 also communicates with a mobile device 206 to notify the customer of a requested transaction and receive the customer's verification of the transaction.
  • the intermediary service 204 also interacts with a storage component 402, which is configured to store configuration information and customer information.
  • the storage component 402 stores data linking the identifying information received from the acquirer 104 to customer-specific information, such as the address of the mobile device 206, one or more payment instruments associated with the customer, and a verification code or codes associated with the customer, the token, or the payment instruments.
  • the intermediary service 204 includes various modules to assist in processing authorization requests.
  • the intermediary service 204 includes a validation module 404, which is configured to receive initial authorization requests and validate that the requests are correctly formed. Validating initial authorization requests may include, for example, verifying that the request is correctly structured and includes all of the required data fields.
  • the authorization request is specified in extensible markup language (XML). In these embodiments, validation includes determining that the XML is well-formed.
  • the intermediary service 204 also includes an authentication module 406, which is configured to authenticate the sender of the authorization request. Authentication is used to avoid having an imposter pose as a legitimate acquirer for the purpose of submitting fraudulent requests for payment.
  • the authentication module 406 may authenticate the acquirer using methods well known in the art. For
  • the authentication module 406 may be configured to verify a digital signature associated with the acquirer and contained in an initial authorization request or in an authentication exchange completed prior to receiving an initial authorization request. Alternatively, the authentication module 406 may be configured to authenticate the acquirer by using a shared encryption key to decrypt a portion of the data in the authorization request. To do so, the authentication module 406 interacts with an encryption module 408, which is configured to execute an encryption algorithm that is complementary to an encryption algorithm that is used by the acquirer 108. The encryption module 408 is also used to encrypt messages sent from the intermediary service 204 to mobile devices 206, issuing institutions 110, and the data storage service 208. In some embodiments, the encryption module also decrypts messages received from the issuing institution and encrypts messages sent to the acquirer 108.
  • the intermediary service 204 includes a customer management module 410, which is configured to retrieve customer information associated with the initial authorization request.
  • the customer information is accessed from the storage component 402 based on the identifying information contained in the initial authorization request.
  • the identifying information may be an alpha-numeric code, a sixteen digit number similar to a credit card number, or one or more pieces of data that uniquely identifies the customer (e.g., a customer nickname).
  • the stored customer information include an address of a mobile device associated with the customer, information defining one or more payment instruments that may be utilized by the customer to complete a purchase transaction, and a verification code or codes that are associated with the customer, the token, or the payment instruments. If multiple payments instruments are defined, the customer information may also specify a default payment instrument or a set of parameters for determining which payment instrument should be used for a particular transaction.
  • a rules module 412 determines the service's response to the initial authorization request.
  • the rules module 412 is configured to determine the type of notification to provide to the customer's mobile device and the required level of customer response to the notification in order to confirm the transaction.
  • the rules module 412 may also determine a selected payment instrument to use in
  • the type of notification may vary depending on the type and amount of the transaction.
  • the service may require different responses from the customer depending on the total value of the purchase.
  • the service may be configured to send a transaction notification to the mobile device without requiring any response from the customer.
  • the service may require that the customer reply to the transaction notification with a response that either authorizes or rejects the transaction.
  • the service may require that the customer reply to the transaction notification with a response that either authorizes or rejects the transaction, as well as provide a verification code with the response.
  • Such rules may be defined by the operator of the service, by merchants that interact with the service, or by customers that use the service. While three levels are provided as an example, it will be appreciated that a greater or lesser number of levels may be utilized by the service. If existing service-, merchant-, or customer- defined rules do not already specify the payment instrument to use in the transaction, the rules module 412 will also require that the customer select a payment instrument to use for the transaction in the response.
  • the rules module 412 includes merchant-defined rules specifying that certain payment instruments are or are not accepted by a particular merchant. For example, a particular merchant may specify a rule indicating that it will not accept payment using American Express and will accept payment using the merchant's gift cards. The rules module 412 can then use this information in selecting the payment instrument or in limiting the number of payment instruments from which a customer can select for a transaction.
  • the intermediary service 204 also includes a mobile device communication module 414, which is configured to communicate with mobile devices 206.
  • the mobile device communication module 414 generates and transmits a transaction notification message in response to the initial authorization request.
  • the transaction notification message includes transaction information, such as the amount of the transaction and the name or location of the merchant requesting the authorization.
  • the transaction notification message may also specify a payment instrument to use for the transaction or specify a list of payment instruments and request a selection from the list.
  • the transaction notification may be sent to the mobile device in a
  • the transaction notification is transmitted to mobile devices 206 via an asynchronous XMPP message.
  • the mobile device includes a mobile device client 418 that runs in the background of the device.
  • the mobile device client 418 may be pre-installed on the mobile device 206, or may be downloaded to the mobile device 206 when a customer opens an account with the intermediary service.
  • the mobile device client 418 operates continuously, since it is impossible to predict when a customer might attempt to make a purchase.
  • the mobile device 206 remains in a state where it always can receive a transaction notification message. However, the mobile device 206 will often operate in a standby or low-power mode in order to preserve battery power. In these embodiments, the mobile device client 418 cannot be operated continuously. Instead, the intermediary service 204 sends a wake-up message to the mobile device client 418 before sending a transaction notification message.
  • the wake-up message may be transmitted on a different messaging channel, such as via a binary SMS message or via a WAP push message or other remote push service.
  • an issuing institution communication module 416 generates an information request based on the received initial authorization request, the customer information, and the information received from the mobile device 206 (if any).
  • the information request may include the desired payment instrument information, the transaction amount, transaction items, and information about the point of purchase.
  • the issuing institution communication module 414 encrypts the request using the encryption module 408 and transmits the message to the issuing institution 112 where the information request is processed.
  • the issuing institution communication module 414 receives an account information message from the issuing institution that includes account information associated with the selected payment instrument.
  • the account information may include, for example, the credit card number and expiration date of a credit card selected from the set of available payment instruments.
  • the intermediary service 204 forwards the information to the acquirer 106.
  • the account information is encrypted by the issuing institution 112 such that it can only be decrypted by the acquirer 106 (i.e., the account information cannot be interpreted by the intermediary service 204).
  • the account information may be decrypted by the intermediary service 204 and re-encrypted for transmission to the acquirer 106.
  • the acquirer 106 then proceeds according to the process discussed above in Figures 2A-C.
  • the acquirer 108 may also send information from the authorization message and/or other transaction information to the intermediary service 204.
  • the mobile device communication module 416 then generates a receipt message and transmits the receipt message to the mobile device 206 using the methods discussed above.
  • the mobile device client 418 provides a "dispute" button that may be selected by the customer to indicate that the transaction was erroneous or fraudulent such that the issuing institution 110 should initiate dispute proceedings.
  • FIGS. 6A and 6B illustrate a flowchart of a process 500 for processing financial transaction data executed by the intermediary service 204.
  • Processing begins in block 502, where the intermediary service 204 receives an initial authorization request from an acquirer 106.
  • the initial authorization request includes unique identifying information, transaction information (e.g., the amount of the transaction, the transaction identifier, etc.), and point of purchase information.
  • the service validates the request according to the methods discussed above.
  • the validation step may include, for example, verifying that the message is in a proper format and verifying that the message includes the essential data for handling the request.
  • Processing then proceeds to block 506, where the service authenticates the requester.
  • the authorization request may include a digital signature provided by the acquirer that can be cryptographically verified. Alternatively, the service may authenticate the acquirer by using a shared cryptographic key to decrypt a portion of the data in the message.
  • the service then proceeds to block 508, where it retrieves customer information corresponding to the information in the authorization request. Retrieving customer information may be executed by using some or all of the identifying
  • the stored customer information may include information defining one or more payment instruments that the customer has indicated can be used to pay for a transaction.
  • the customer information also includes an address of a mobile device, such as the mobile device's telephone number or IP address.
  • the customer information is provided by a customer during an initial registration process in which the customer registers with the service and enters the appropriate information.
  • the customer information may be provided by, for example, a financial institution that offers the intermediary service as an added benefit to a financial instrument provided to the customer.
  • the transaction notification message includes at least a minimum amount of information to enable the customer to confirm the transaction.
  • the transaction notification message may include the transaction time, the transaction amount, the point of purchase, and/or the purchase location.
  • the transaction notification message may also specify a payment instrument that will be used for the transaction, or a list of payment instruments that may be used and require that the customer select from the list.
  • the transaction notification message specifies a required response from the customer, such as an authorization/denial of the transaction or the submission of a verification code.
  • the service After generating the transaction notification message, the service proceeds to block 512, where it sends the message to the mobile device 206. Processing then proceeds to block 514, where the service receives a reply from the mobile device 206. As discussed above, this step is not executed if the transaction notification message did not require a response from the customer. The service then proceeds to decision block 516, where it uses the reply message to determine whether the transaction was verified by the customer. In some cases, the service may do so by detecting a verification indicator in the reply message, which could simply be a single bit or a "yes" or "no" received from the mobile device 206. Alternatively, if the reply message includes a verification code, the service compares the received verification code to a verification code in the stored customer information. In some embodiments, the verification code is encrypted by the mobile device 206 using a
  • the intermediary service then verifies the transaction by comparing the received hash value to a value generated by applying the same oneway hash function to the stored verification code. If the reply message indicates that the customer has denied the request or the customer's verification code does not match the stored verification code, processing proceeds to block 518, where the service rejects the authorization request. At this step, the service may transmit a rejection message to the acquirer to notify it of the rejected request.
  • processing proceeds to block 520 in Figure 6B, where the service generates an information request using information from the initial authorization request, the customer information, and/or the customer's reply message.
  • the information request may include identifying information from the initial authorization request or the customer information.
  • processing proceeds to block 522, where the service sends the message to the appropriate issuing institution.
  • Processing then proceeds to block 524, where the service receives an account information message from the issuing institution in response to the information request.
  • the account information includes information associated with the selected payment instrument that can be used to authorize payment.
  • the account information may be encrypted such that it can only be accessed by the acquirer 108.
  • processing proceeds to block 526, where the intermediary service sends the account information to the acquirer 108, which can then generate the modified authorization request.
  • Figure 7 is a flowchart of a process 700 for processing financial transaction data executed by an acquirer 108.
  • the process 700 is executed by the acquirer 108 in conjunction with the process 500 executed by the intermediary service of Figures 6A and 6B.
  • Processing begins at block 702, where the acquirer 108 receives an initial authorization request from the point of purchase 106.
  • the acquirer determines whether the initial authorization request should be routed to the intermediary service 204 based on the identifying information contained in the initial authorization request. The determination may include, for example, assessing whether an identifying number contained in the initial authorization request falls within a range of identifying numbers or has a particular prefix associated with the
  • the acquirer forwards the initial authorization request to the payment association 112 for processing in accordance with traditional processes as described in Figure 1. If, however, the identifying information contained in the initial authorization request indicates that the initial authorization request is associated with the intermediary service, processing continues to block 708. At block 708, the acquirer 108 sends at least part of the data from the initial authorization request to the intermediary service 204.
  • the intermediary service 204 determines the account information using the process 500 of Figures 6A and 6B.
  • the received account information may be received in encrypted or unencrypted form. If encrypted by the issuing institution or the intermediary service, the acquirer 108 may decrypt the account information using a locally-stored encryption key.
  • processing proceeds to block 712, where the acquirer 108 generates a modified authorization request based on the initial authorization request and the received account information. As discussed above, the acquirer 108 may generate the modified authorization request by replacing identifying information contained in the original request with the received account information.
  • the following is an example of an initial authorization request such as might be received from a point of purchase:
  • the identifying information results in the initial authorization request being sent to the intermediary service 204.
  • the acquirer may receive the following account information in response:
  • the acquirer 108 would then construct the following modified authorization request:
  • a transaction identifier may be assigned to each transaction and used by the acquirer and the intermediary server to ensure that all sent and received messages are correctly correlated.
  • the acquirer may store all initial authorization requests, received account information, and modified authorization requests in a data structure so that the acquirer or a third party may subsequently audit the information and confirm that transactions are being appropriately processed.
  • processing then proceeds to block 714 where the acquirer 108 sends the modified authorization request to the payment association 112.
  • the acquirer 108 receives an authorization or a denial in response to the modified authorization request.
  • the acquirer 108 then completes the authorization process by sending the authorization or denial message to the point of purchase 106 in block 718.
  • the acquirer 108 may also send the authorization or denial message to the intermediary service 204 so that the intermediary service 204 can send a receipt message to the customer's mobile device 206.
  • the acquirer 108 may also send transaction details, such as the list of transaction items, to the intermediary service 204 so that the receipt message can include additional transaction details.
  • process 700 has been described as being implemented by the acquirer 108, it will be appreciated that process 700 can be implemented by any combination thereof
  • the payment association 112 or an issuing institution 110 may forward initial authorization requests to the intermediary service 204 in lieu of the acquirer forwarding the request.
  • the account information is then returned to the payment association or issuing institution for further processing.
  • Figure 8 illustrates a logical block diagram of the acquirer 108 that implements the process 700 of Figure 7.
  • the acquirer 108 redirects certain authorization requests to the intermediary service 204 and generates modified authorization requests based on information provided by the intermediary service 204.
  • aspects of the acquirer 108 may be implemented as special-purpose circuitry, programmable circuitry, or as a combination of these.
  • the modules in the acquirer 108 may be implemented in a single physical device or distributed over multiple physical devices and the functionality implemented by calls to remote services.
  • the acquirer 108 receives an initial transaction authorization request from the point of purchase 106 and transmits a modified authorization request to the issuing institution 110 via the payment association 112.
  • the acquirer 108 also communicates with the intermediary service 204 to request account information associated with a particular authorization request and to receive the requested account information.
  • the acquirer 108 also interacts with a storage component 802, which is configured to store information used to integrate with the intermediary service 204.
  • the storage component 802 stores identifying information (such as ranges of account numbers or account number prefixes) that can be used to determine which authorization requests should be handled by the intermediary service 204.
  • the storage component 802 may also store historical transaction information to be used for auditing or if a transaction is disputed.
  • the acquirer 108 includes various modules to assist in processing authorization requests.
  • the acquirer 108 includes a point of purchase communication module 804, which is configured to communicate with the point of purchase 106 to receive initial authorization requests and transmit authorization or denial messages at the end of the transaction.
  • the acquirer 108 also includes an evaluation module 806, which is configured to evaluate initial authorization requests
  • the acquirer 108 also includes an intermediary service communication module 808, which is configured to communicate with the intermediary service 204 to send authorization requests and to receive account information.
  • the intermediary service communication module 808 then provides the account information to an authorization request generator module 810, which is configured to generate a modified authorization request based on the initial authorization request and the received account information.
  • the modified authorization request is then provided to a payment association communication module 812, which is configured to communicate with the payment association 112 to send the modified authorization requests to the issuing institution 110.
  • the payment association communication module 8 12 After the issuing institution 110 approves or denies a transaction, the payment association communication module 8 12 also receives an authorization or denial message from the payment association 112. The acquirer 108 then forwards the message to the point of purchase 106 and/or the intermediary service 204.
  • FIG. 8 is a block diagram depicting various message routing paths through the intermediary service 204.
  • Complementary encryption keys are depicted as being maintained by different parties that participate in the processing of a financial transaction. For example, a key A that is maintained by acquirer 108 allows the acquirer to encrypt messages and communicate in a secure fashion with the intermediary service 204, which maintains a complementary key A 1 for decoding the encrypted messages.
  • the intermediary service 204 maintains a key B 1 that allows it to communicate in a secure fashion with the mobile device 206, which maintains a complementary key B.
  • the intermediary service 204 also maintains a key C that allows it to communication in a secure fashion with the issuing institution 110, which maintains a key C.
  • a key C that allows it to communication in a secure fashion with the issuing institution 110, which maintains a key C.
  • portions of the point of purchase information from the initial authorization request may be encrypted by the acquirer 108 using an encryption key D.
  • the intermediary services 204 receives messages or portions of messages that are encrypted, the service copies the encrypted messages or portions of messages and forwards the copied messages to the issuing institution 110.
  • the issuing institution 110 is able to decrypt the encrypted message or portion of the message using key D 1 .
  • the issuing institution 110 may encrypt account information using key D so that the information may be read only by the acquirer 108.

Abstract

Un service de traitement de transaction fonctionne en tant qu’intermédiaire entre des acheteurs de demandes de transaction financière et des institutions d’émission qui traitent les demandes de transaction financière. Le service d’intermédiaire utilise un dispositif mobile du client comme voie de communication hors bande pour indiquer à un client une demande de transaction financière reçue. Pour envoyer la notification, le service d’intermédiaire récupère des informations stockées du client, notamment une adresse du dispositif mobile du client et une liste d’instruments de paiement qui peuvent être utilisés pour payer la transaction. Avant de poursuivre le traitement de la demande de transaction financière reçue, le service peut d’abord demander au client de confirmer la transaction par le biais du dispositif mobile. Le service d’intermédiaire récupère les informations de compte financier associées au client auprès des institutions d’émission, et, si la transaction est confirmée, fournit les informations de compte aux acquéreurs afin d’autoriser le traitement des transactions.
PCT/US2009/063641 2008-11-08 2009-11-06 Service d’intermédiaire et procédé pour traiter des données de transaction financière avec confirmation par dispositif mobile WO2010054259A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US11274908P 2008-11-08 2008-11-08
US61/112,749 2008-11-08
US12/557,453 US8244643B2 (en) 2008-11-08 2009-09-10 System and method for processing financial transaction data using an intermediary service
US12/557,453 2009-09-10
US12/557,457 US8099368B2 (en) 2008-11-08 2009-09-10 Intermediary service and method for processing financial transaction data with mobile device confirmation
US12/557,457 2009-09-10

Publications (1)

Publication Number Publication Date
WO2010054259A1 true WO2010054259A1 (fr) 2010-05-14

Family

ID=42153279

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/063641 WO2010054259A1 (fr) 2008-11-08 2009-11-06 Service d’intermédiaire et procédé pour traiter des données de transaction financière avec confirmation par dispositif mobile

Country Status (1)

Country Link
WO (1) WO2010054259A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019140056A1 (fr) * 2018-01-10 2019-07-18 Vatbox, Ltd. Système et procédé de génération d'un score de probabilité de ré-émission pour une preuve de transaction
WO2020209989A1 (fr) * 2019-04-10 2020-10-15 Mastercard International Incorporated Facilitation de transactions de réseau de paiement en temps réel
CN113516475A (zh) * 2021-05-14 2021-10-19 数字印记(北京)科技有限公司 数据交付方法、装置、系统、电子设备和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020143634A1 (en) * 2001-03-30 2002-10-03 Kumar K. Anand Wireless payment system
US20080010191A1 (en) * 2006-07-06 2008-01-10 Firethorn Holdings, Llc Methods and Systems For Providing a Payment in a Mobile Environment
US20080172317A1 (en) * 2007-01-09 2008-07-17 Doug Deibert Mobile phone payment with disabling feature

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020143634A1 (en) * 2001-03-30 2002-10-03 Kumar K. Anand Wireless payment system
US20080010191A1 (en) * 2006-07-06 2008-01-10 Firethorn Holdings, Llc Methods and Systems For Providing a Payment in a Mobile Environment
US20080172317A1 (en) * 2007-01-09 2008-07-17 Doug Deibert Mobile phone payment with disabling feature

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019140056A1 (fr) * 2018-01-10 2019-07-18 Vatbox, Ltd. Système et procédé de génération d'un score de probabilité de ré-émission pour une preuve de transaction
WO2020209989A1 (fr) * 2019-04-10 2020-10-15 Mastercard International Incorporated Facilitation de transactions de réseau de paiement en temps réel
US11663591B2 (en) 2019-04-10 2023-05-30 Mastercard International Incorporated Facilitation of real-time payment network transactions
CN113516475A (zh) * 2021-05-14 2021-10-19 数字印记(北京)科技有限公司 数据交付方法、装置、系统、电子设备和存储介质

Similar Documents

Publication Publication Date Title
US8099368B2 (en) Intermediary service and method for processing financial transaction data with mobile device confirmation
US8280776B2 (en) System and method for using a rules module to process financial transaction data
US8370265B2 (en) System and method for managing status of a payment instrument
US20230004947A1 (en) Device enrollment system and method
US9292852B2 (en) System and method for applying stored value to a financial transaction
CN110945554B (zh) 注册表区块链架构
US9530125B2 (en) Method and system for secure mobile payment transactions
CN104838399B (zh) 使用移动设备认证远程交易
AU2010295188B2 (en) Asset storage and transfer system for electronic purses
US20070063017A1 (en) System and method for securely making payments and deposits
US20120284187A1 (en) System and method for processing payment transactions
CN108292398A (zh) 利用增强的持卡人认证令牌
JP2009532814A (ja) 消費者の支払を強化する方法及びシステム
US8886932B2 (en) Message storage and transfer system
JP2013505487A (ja) 電子財布のための資産価値記憶、転送システム
KR20010087564A (ko) 개인 휴대단말기를 이용한 사용자 인증 처리 시스템 및 그방법
WO2010054259A1 (fr) Service d’intermédiaire et procédé pour traiter des données de transaction financière avec confirmation par dispositif mobile
US20180114201A1 (en) Universal payment and transaction system
KR20130052552A (ko) 메시지 저장 및 전송 시스템

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09825519

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09825519

Country of ref document: EP

Kind code of ref document: A1