US20150199671A1 - Systems and methods for processing cardless transactions - Google Patents

Systems and methods for processing cardless transactions Download PDF

Info

Publication number
US20150199671A1
US20150199671A1 US14/154,111 US201414154111A US2015199671A1 US 20150199671 A1 US20150199671 A1 US 20150199671A1 US 201414154111 A US201414154111 A US 201414154111A US 2015199671 A1 US2015199671 A1 US 2015199671A1
Authority
US
United States
Prior art keywords
account
transaction
value
associated
payment network
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
US14/154,111
Inventor
Hitesh Bajaj
Douglas G. Brown
Robert Woodbury
Neil Marcous
Peter Gordon
Renee Goodheart
Mark Elliott
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fidelity National E-Banking Services Inc
Original Assignee
Fidelity National E-Banking Services 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
Application filed by Fidelity National E-Banking Services Inc filed Critical Fidelity National E-Banking Services Inc
Priority to US14/154,111 priority Critical patent/US20150199671A1/en
Assigned to Fidelity National E-Banking Services, Inc. reassignment Fidelity National E-Banking Services, Inc. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WOODBURY, ROBERT, ELLIOTT, MARK, BAJAJ, HITESH, MARCOUS, Neil, GORDON, PETER, BROWN, DOUGLAS G., GOODHEART, Renee
Publication of US20150199671A1 publication Critical patent/US20150199671A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/325Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/02Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108Remote banking, e.g. home banking
    • G06Q20/1085Remote banking, e.g. home banking involving automatic teller machines [ATMs]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/20Point-of-sale [POS] network systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/385Payment protocols; Details thereof using an alias or single-use codes
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F19/00Complete banking systems; Coded card-freed arrangements adapted for dispensing or receiving monies or the like and posting such transactions to existing accounts, e.g. automatic teller machines
    • G07F19/20Automatic teller machines [ATMs]

Abstract

Systems and methods are provided for processing cardless financial transactions at transaction devices such as Automated Teller Machines. An example method comprises receiving a transaction request including at least one transaction parameter and receiving a substitute value representing an account for processing the transaction request. The substitute value is distinct from an account number associated with the account. The method further comprises sending the at least one transaction parameter and the substitute value to a payment network associated with the substitute value and completing the transaction request. A second method comprises receiving a transaction request with at least one transaction parameter and a substitute value. The second method further comprises determining account credentials associated with the substitute value using the account credentials.

Description

    FIELD
  • Embodiments of this disclosure relate to processing cardless transactions utilizing transaction devices such as Automated Teller Machines.
  • BACKGROUND
  • Automated Teller Machines (ATMs) have been used for decades to enable round-the-clock access to financial institution accounts such as deposit accounts at banks. Using ATMs, account holders can withdraw funds, deposit funds, and access account information. Some ATMs also enable other transactions, such as bill pay, ticket purchases, and stamp purchases.
  • Many ATMs are associated with a particular financial institution. This limits ATMs from performing certain transactions. For example, if an account holder has an account with Bank A, he may be unable to use an ATM operated by or on behalf of Bank B to withdraw money from his Bank A account. And even if that account holder can withdraw money from the Bank B ATM, he may be charged a high fee (by Bank B or Bank A), unable to deposit funds into his account at Bank A, or unable to access other account functions such as requesting a balance inquiry. This problem is compounded when the account holder attempts to use an ATM in a foreign country. He may be unable to access his account because of a relationship between his bank and the foreign bank owning the ATM, or may be charged extra international fees.
  • Furthermore, ATMs generally require that an account holder present a card with a magnetic stripe to withdraw funds from an ATM. Thieves know this, and have created devices to steal the data stored on that magnetic stripe. Thus, new systems have been developed that enable account holders to utilize smartphones to access their accounts. However, the solutions that exist for enabling smartphone access to accounts do not allow account holders to access accounts using smartphones at an ATM other than one owned by the bank holding the account, even if the bank owning the ATM has a relationship with the bank holding the account.
  • Another drawback of existing solutions is their reliance on card credentials issued by a credit or debit card network. Thus even where these solutions offer the convenience of not requiring a physical card to be presented at the ATM, their use of the credentials associated with the physical card nevertheless subject the transaction to extraneous fees and routing requirements. Yet another disadvantage of existing solutions is that, in many systems, the ATM receives an account number associated with the account holder's account. If a thief is able to spoof the ATM's identity, he may be able to intercept the account number and use it to withdraw money without the account holder's permission.
  • It is accordingly a primary object of the disclosed embodiments to solve these problems as well as many others (e.g., similar problems associated with point-of-sale transactions).
  • SUMMARY
  • Embodiments of the present disclosure are directed to methods, systems, and computer-readable media for enabling financial transactions at transaction devices such as ATMs. An example method comprises receiving a transaction request including at least one transaction parameter and receiving a substitute value being associated with an account for processing the transaction request. The substitute value is distinct from an account number associated with the account. The method further comprises sending the at least one transaction parameter and the substitute value to a payment network associated with the substitute value and completing the transaction request by, for example, outputting funds, receiving funds, or displaying a balance.
  • Systems and computer-readable media (such as non-transitory computer-readable media) that implement the above method are also provided.
  • A second method comprises receiving a transaction request with at least one transaction parameter and a substitute value. The second method further comprises determining if the substitute value is associated with a payment network, and determining account credentials associated with the substitute value.
  • Systems and computer-readable media (such as non-transitory computer-readable media) that implement the above method are also provided.
  • Additional objects and advantages of the embodiments will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice. The objects and advantages will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
  • It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the claims.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments and together with the description, serve to explain some principles.
  • FIG. 1 is a system for use in implementing the disclosed embodiments.
  • FIG. 2A shows illustrations of user interfaces for initializing a transaction using a mobile device and a transaction device, consistent with disclosed embodiments.
  • FIG. 2B shows illustrations of user interfaces and operations for processing a transaction using a mobile device and a transaction device, consistent with disclosed embodiments.
  • FIG. 2C shows illustrations of a user interface for processing a transaction using a transaction device, consistent with disclosed embodiments.
  • FIG. 2D shows illustrations of a user interface for processing a transaction using a transaction device, consistent with disclosed embodiments.
  • FIG. 3A is an example process for initializing account registration using a mobile device, consistent with disclosed embodiments.
  • FIG. 3B is an example process for initializing a transaction using a mobile device, consistent with the disclosed embodiments.
  • FIG. 3C is an example process for initializing a transaction using a transaction device, consistent with the disclosed embodiments.
  • FIG. 3D is an example process for processing a transaction using a transaction device, consistent with disclosed embodiments.
  • FIG. 4 is an example of a computer system for use in implementing the disclosed systems, consistent with disclosed embodiments.
  • BRIEF OVERVIEW
  • Example embodiments of this disclosure are related to enabling account holders to effect cardless financial transactions at transaction devices such as ATMs. The ATMs can receive transaction requests which include transaction parameters. The transaction parameters can indicate a desire by an account holder to perform particular transactions, including withdrawals, deposits, balance inquires, ticket purchases, stamp purchases, balance transfers, or other transactions.
  • More specifically, some embodiments enable account holders to perform these types of transactions without having to utilize an ATM owned or operated by the same bank that holds their account, without having to use a debit or bank card with a magnetic strip, and without the ATMs receiving an actual card number or account number. Some embodiments also include ATMs receiving substitute values that refer to accounts (but do not include account numbers), constructed values (that resemble payment card numbers), or dynamic tokens (which correspond to substitute values or other credentials in a database).
  • DETAILED DESCRIPTION
  • Reference will now be made in detail to various embodiments, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
  • FIG. 1 is a system 100 for use in implementing the disclosed embodiments. System 100 comprises mobile device 101, transaction device 103, network 105, credential processor 107, credential issuer 108, domestic bank 111, payment network 113, receiver 115, and international institution 117. One of ordinary skill will understand that particular devices in system 100 can be duplicated, omitted, or modified, as appropriate.
  • In some embodiments, each device illustrated in FIG. 1 may be operated by separate parties. However, in other embodiments, one party may operate or administer more than one of the devices illustrated in FIG. 1. For example, a single entity may operate any or all of credential processor 107, credential issuer 108, and payment network 113. Additionally, in some embodiments, one of the illustrated devices in FIG. 1 may be combined with another illustrated device. For example, credential processor 107, credential issuer 108, and payment network 113 may be combined into a single system.
  • Mobile device 101 represents a portable device usable by a user for communication purposes. Mobile device 101 may be implemented as a cellular phone, smartphone, wearable computer, personal digital assistant (PDA), personal media player (PMP), or the like. Mobile device 101 may comprise, for example, a touchscreen display, a non-touchscreen display, a keyboard, a pointing device, or other input device. Mobile device 101 may communicate with network 105 using a wireless network, a mobile network, a satellite network, or the like. Mobile device 101 can communicate with other devices, such as credential processor 107, credential issue 108, or transaction device 103, over network 105.
  • Mobile device 101 may comprise storage for software that, when executed, causes mobile device 101 to send and/or receive information from devices such as transaction device 103. The software may be implemented in a variety of ways. In one example embodiment, the software may be operable to send and/or receive information from other devices using wireless protocols. For example, the software can be configured to enable mobile device 101 to send and/or receive information over a Bluetooth connection, over a wireless network connection (e.g., 802.11a/b/g/n), using Near-Field Communication (NFC), or other standard or proprietary communication protocol. The software may also be configured to enable the receipt of information visually. For example, mobile device 101 may have camera connected to it or scanner functionality, and may capture information encoded in an image or a visual symbol displayed on transaction device 103 (such as a barcode).
  • Mobile device 101 also enables a user to select an account from a list of accounts (e.g., accounts owned by the user) by presenting a list of available accounts. Mobile device 101 may receive a list of such accounts from another system, such as credential processor 107. After the selection of an account, mobile device 101 transmits the transaction data and an indication of the selected account to another device. The indication of the selected account may comprise, for example, an identifier for the account or an index value related to the account (e.g., the first presented account having an index value of “1” and the second presented account having an index value of “2”).
  • Transaction device 103 represents a device configured to perform one or more financial transactions. Transaction device 103 may be implemented as, for example, an Automated Teller Machine (ATM). Transaction device 103 may comprise a keypad 103B (also known as a “10-key”). Keypad 103B may comprise 10 or more keys enabling input of letters, numbers, symbols, or other characters. Keypad 103B may be implemented as a physical keypad or as a virtual keypad (e.g., presented on a touchscreen of transaction device 103).
  • Transaction device 103 may also comprise a touchscreen display or a non-touchscreen display. Transaction device 103 may also comprise a card slot 103C enabling, for example, insertion of magnetic-stripe cards. Transaction device 103 may be connected to network 105 via a wireless network, a wired network, a cellular network, a satellite network, or the like, and may communicate with other devices, such as mobile device 101, credential processor 107, or credential issuer 108, over network 105. Transaction device 103 may also comprise a cash drawer 103D. Cash drawer 103D is configured to permit users can retrieve funds withdrawn from a user account.
  • In some embodiments, transaction device 103 may perform operations for initiating transactions. For example, transaction device 103 may communicate directly with one or more of network 105, credential processor 107, or payment network 113. However, in other embodiments, transaction device 103 may communicate directly with drivers or switches (not pictured) which perform communications on behalf of transaction device 103. Such drivers and/or switches receive communication from one or more transaction devices 103, reformat the communication into instructions that comply with a protocol associated with payment network 113, and forward the reformatted communication to payment network 113, as appropriate. Drivers may also provide instructions to transaction device 103, provide images or other information for display, provide communications received from other systems (such as payment network 113) to transaction device 103, or the like.
  • Transaction device 103 comprises storage for software that, when executed, causes transaction device 103 to send and/or receive information from devices such as mobile device 101. In one example embodiment, the software may be operable to send and/or receive information from other devices using wireless protocols. For example, the software can be configured to enable transaction device 103 to send and/or receive information over a Bluetooth connection, over a wireless network connection (e.g., 802.11a/b/g/n), using Near-Field Communication (NFC), or other standard or proprietary communication protocol. The software may also be configured to enable sending information to mobile device 101 in a visual manner. For example, transaction device 103 may have functionality for displaying information encoded using a visual symbol displayed on transaction device 103 (such as a barcode), enabling mobile device 101 to capture an image and receive the encoded information.
  • Transaction device 103, in some embodiments, communicates with mobile device 101 using Near Field Communication (NFC) technology. NFC technology enables one- or two-way wireless communication between devices separated by a short distance. In some embodiments, NFC technology enables two devices to send data directly to each other. In other embodiments, NFC technology provides the devices the ability to set up, or “bootstrap,” a wireless connection between the devices. The connection can be, for example, a Bluetooth connection, a Wi-Fi Direct connection, a Wi-Fi connection, or the like. After the connection between the devices is set up, the devices can send data to each other over that connection.
  • Mobile device 101 and transaction device 103 are not limited to using NFC or other local wireless connections to communicate directly with one another. For example, transaction device 103 and mobile device 101 may be configured to exchange data by communicating with a separate device connected to network 105.
  • In some embodiments, a user may utilize keypad 103B to input data into transaction device 103, including user credentials associated with one or more accounts owned by the user. One of ordinary skill will appreciate that other input devices, such as biometric devices, also may be used to communicate data from the user to the transaction device.
  • Network 105 represents an electronic network for transmitting data between electronic devices. Network 105 may be implemented as one or more of the Internet, an intranet, a private link (such as a fiber optic network connecting remote sites), or the like.
  • Credential processor 107 represents one or more electronic devices that store data for processing transactions. For example, credential processor 107 stores user credentials associated with one or more accounts associated with the user, in a database associated with credential processor 107. The user credentials comprise, for example, username and password combinations associated with a user, email addresses associated with a user, phone numbers, tokens or identifiers associated with mobile device 101, a user, or a user account, biometric data associated with a user, or the like.
  • A database connected to credential processor 107 stores a substitute value associated with the user credentials. The substitute value may take any form, for example, alphanumeric, alphabetic, numeric, text, hash-based, or binary. In some embodiments, the substitute value may be formed such that transaction device 103 recognizes it as associated with a particular network (such as payment network 113). A substitute value corresponding to a user's account is distinct from the actual account credentials of the account.
  • For example, the substitute value may be in the form of a constructed value. A constructed value, in some embodiments, comprises a string of numbers formatted to resemble a payment card number (also known as a bank card number, PAN or a Primary Account Number). Some portion of the digits of the constructed value may serve as an indicator value that enables systems that are involved in financial transaction processing to determine a network, such as a payment network, for processing a financial transaction with that card number. For example, in some cases an indicator value may be the first few digits of such numbers contain a Bank Identification Number (BIN), also known as an Issuer Identification Number or IIN. For example, VISA cards typically have a “4” as the first digit.
  • For example, such a constructed value may contain a particular value as part of the indicator value, such as ‘59,’ which indicates that the constructed value is associated with a particular network (such as payment network 113). Although the constructed value does not represent a particular account, the constructed value's attribute of resembling a payment card enables payment network 113 to route a transaction that includes the constructed value as though it were a transaction that included an actual PAN.
  • Credential processor 107, in some embodiments, receives a request to generate credentials from a user (e.g., from mobile device 101, transaction device 103, or a personal computer). Credential processor 107 may forward the request to credential issuer, receive credentials in response, and forward them to credential issuer 108. In other embodiments, however, a user can request the generation of credentials directly from credential issuer 108.
  • Credential processor 107, in some embodiments, can receive a request for a substitute value corresponding to a particular account selected by a user (e.g., from mobile device 101 or transaction device 103). In some embodiments, credential processor 107 can determine the substitute value associated with a particular account and send the substitute value back to transaction device 103 for processing. In other embodiments, credential processor 107 may be configured to send a dynamic token in lieu of or in addition to the substitute value to transaction device 103, and may instead request a dynamic token associated with the substitute value by sending a request to credential issuer 108.
  • Credential issuer 108 represents one or more electronic devices that generate data for processing transactions. In some embodiments, credential issuer 108 generates one or more substitute values in response to a registration process conducted by the user using, e.g., mobile device 101, transaction device 103, credential processor 107, or payment network 113 (such as described more fully below with respect to FIG. 3A). In some embodiments, the generated substitute value is distinct from the actual account credentials of a user's account(s).
  • Credential issuer 108, in some embodiments, generates substitute values upon receiving a request from, for example, credential processor 107. The substitute values may be generated to resemble PANs.
  • Credential issuer 108 may perform a look-up or cross-reference to a database (or other data store) for the received substitute value. After receiving the substitute value, credential issuer 108 may return a dynamic token associated with the substitute value. The dynamic token, in some embodiments, may be an identifier or other piece of data that is usable for only a single transaction and represents a substitute value and/or account credentials stored at credential issuer 108. In this manner, the actual account credentials need not be communicated to mobile device 101 or transaction device 103 (or its associated switch/driver), and thus security is enhanced. This token is returned to credential processor 107.
  • One of ordinary skill will understand that the functionality of credential processor 107 and credential issuer 108 may be combined into a single device or set of electronic devices.
  • Payment network 113 represents one or more electronic devices that provide functionality for a variety of financial transactions, such as the electronic exchange of funds. Payment network 113 may interconnect financial institutions, such as banks, to one another. Payment network 113 may also comprise other interconnections, such as to merchants, terminal providers, other payment networks, or the like. In some embodiments, payment network 113 may comprise more than one payment network. In some embodiments, payment network 113 may connect one or more financial institutions (such as domestic bank 111) or receivers (such as receiver 115) to one another for financial purposes. These receivers can be, for example, financial institutions, merchants, other payment networks, other fund transfer networks, or the like.
  • In some embodiments, payment network 113 may comprise one or more interbank networks, sometimes called ATM networks, which may enable multiple banks to access information and funds of accounts held by one another. Examples of payment networks include, e.g., NYCE Payments Networks, LLC's NYCE®, PayNet Payment Networks, LLC's PayNet™, and Interac Association's Interac®. In some embodiments, payment network 113 may be implemented as described in U.S. Patent Application Publication No. 2013/0246274, filed Mar. 15, 2013, and entitled “Systems and Methods for Real-time Account Access.” Payment network 113 may also be implemented as a payment network as described in (not yet published) U.S. patent application Ser. No. 14/081,590, filed Nov. 15, 2013, and entitled “Systems and Methods for Real-time Account Access.” The contents of these applications are hereby incorporated by reference in their entirety.
  • Two entities that have relationships with payment network 113 are said to be “connected to” one another over payment network 113. As an example, if a user having an account with a bank connected to payment network 113 attempts to access an account at an ATM owned by another bank also connected to payment network 113, each bank may communicate with the other using payment network 113 to complete the transaction. Payment network 113 may operate domestically or internationally, across one or more countries, to allow communications between entities, such as banks, that are not located in the same country. This may be accomplished, for example, via connections through a gateway, other networks, or other payment networks.
  • Domestic bank 111 represents a bank or other deposit institution that may be located in the same country as payment network 113. Domestic bank 111 may have one or more accounts, such as deposit accounts, checking accounts, savings accounts, credit accounts, mortgages, Certificates of Deposit (CDs), or the like. These accounts may be located at domestic bank 111 who may hold them on behalf of one or more users. In some embodiments, users may utilize the disclosed systems and methods to effect deposit transactions. In these embodiments, receiver 115 can be configured to receive funds deposited by a user at transaction device 103. Receiver 115 may represent one or more of a financial institution, a merchant, another payment networks, a fund transfer network, or the like. In some embodiments, receiver 115 represents an entity that is not in the same country as payment network 113.
  • FIGS. 2A and 2B show illustrations of user interfaces for completing a transaction using mobile device 101 and transaction device 103. One of ordinary skill will understand that a variety of connections may be used to transmit data between transaction device 103 and mobile device 101, such as both devices communicating with a server connected to network 105, 802.11 wireless (Wi-Fi) connections, Bluetooth connections, Near-Field Communication (NFC), other types of wireless connections, or wired connections, may be used to transmit data between mobile device 101 and transaction device 103. One of ordinary skill will also understand that in some embodiments a visual symbol, such as a one- or two-dimensional barcode or other symbol, may be used to communicate data between transaction device 103 and mobile device 101 (e.g., by displaying such a symbol on a screen of transaction device 103 for capture by a camera attached to mobile device 101). Exemplary process flows using the interfaces depicted in FIGS. 2A and 2B are illustrated in FIG. 3B.
  • FIG. 2A shows exemplary illustrations of user interfaces 200A for performing a transaction using mobile device 101 and transaction device 103, consistent with disclosed embodiments.
  • In example FIG. 2A, a user has initiated a transaction request using mobile device 101. For example, the user may have pressed a button displayed on a touchscreen of mobile device 101, opened an application on mobile device 101, utilized a voice command system to initiate the transaction, or the like. In addition, the user may also have interacted with transaction device 103. For example, the user may have pressed buttons displayed on a touchscreen of transaction device 103 that represent a particular transaction and a desire to complete the transaction using mobile device 103.
  • Transaction device 101 and mobile device 103 may communicate with one another using a server (e.g., an electronic device) connected to network 105. As one example, mobile device 101 and transaction device 103 may both communicate with a device such as credential processor 107, in order to communicate information concerning the requested transaction from mobile device 101 to transaction device 103 and vice versa. In one example embodiment, the user may utilize mobile device 101 to identify the particular transaction device (here, transaction device 103) at which the user desires to accomplish the transaction. The user can identify transaction device 103 using, for example, location-based software, an identifier associated with transaction device 103 printed on the side of transaction device 103 or displayed on a screen of transaction device 103, a randomly-generated code displayed on a screen of transaction device 103, or the like. This enables the server (e.g., credential processor 107) to identify each of mobile device 101 and transaction device 103.
  • The requested transaction may comprise at least one of a cash withdrawal, a cash deposit, or a balance inquiry. Other transactions, such as purchases, payments, check-cashing, fund transfers (including loading or reloading a prepaid account), are possible as well.
  • Mobile device 101 may prompt the user to select an account. One of ordinary skill will understand that the one or more accounts displayed to the user on mobile device 101 may be based on the particular transaction requested by the user. For example, if the user initiates a withdrawal transaction, mobile device 101 may be configured to not display accounts that cannot have a withdrawal made against them (such as Certificates of Deposit). Alternatively, a prompt and account selection could be made available on the display of the transaction device in other embodiments not shown in the figures.
  • Transaction device 103 displays a message requesting the user to select an account on mobile device 101. As indicated above, prompts to the user may be made interchangeably upon the mobile device and the transaction device in various embodiments within the scope of the invention.
  • After selecting the account, mobile device 101 sends an identification of the selected account to credential processor 107.
  • FIG. 2B shows illustrations of user interfaces 200B for processing a transaction using a mobile device 101 and a transaction device 103, consistent with disclosed embodiments. Credential processor 107 receives an indication of the selected account and an identifier associated with transaction device 103.
  • In some embodiments, credential processor 107 determines a substitute value associated with the account selected by the user. Credential processor 107 sends the substitute value to transaction device 103. After receiving the substitute value from credential processor 107, transaction device 103 displays a message indicating that the transaction will be processed. For example, this could include transaction device 103 displaying a message to the user indicating that the transaction is being processed.
  • In other embodiments, credential processor 107 may be configured to send a dynamic token in lieu of or in addition to the substitute value to transaction device 103. In these embodiments, credential processor 107 sends a request for a dynamic token to credential issuer 108. The request includes, for example, the determined substitute value associated with the selected account, an identifier associated with transaction device 103, or the like. Credential issuer 108 generates a dynamic token that corresponds to the substitute value and stores it in a database for later look-up. The token may be in the form of a number, a string of letters, an alphanumeric string, or any identifier that enables credential issuer to determine an associated substitute value. In some embodiments, the dynamic token may conform to the format of a PAN, also known as a Primary Account Number. Credential issuer 108 then sends the token to credential processor 107 which may forward it to transaction device 103. After receiving the token from credential processor 107, transaction device 103 displays a message indicating that the transaction will be processed. For example, this could include transaction device 103 displaying a message to the user indicating that the transaction is being processed.
  • FIGS. 2C and 2D are illustrations of user interfaces for completing a transaction using transaction device 103. Exemplary process flows using the interfaces depicted in FIGS. 2C and 2D are illustrated in FIG. 3C.
  • FIG. 2C shows an illustration of a user interface 200C for processing a request to process a transaction using a transaction device 103. In FIG. 2C, a user interacts with transaction device 103 to provide user credentials. For example, the user may utilize keypad 103B to provide a username and password to transaction device 103. Any other type of credential may be provided including, for example, an identifier associated with mobile device, an e-mail address, biometric information, or the like, Transaction device 103 may then send the user credentials and a request for available accounts to credential processor 107, via network 105.
  • FIG. 2D shows an illustration of a user interface 200D for processing a transaction using a transaction device 103, consistent with disclosed embodiments. In FIG. 2D, the user has provided user credentials to transaction device 103, and transaction device 103 has sent the user credentials to credential processor. In response, transaction device 103 received the accounts associated with the received user credentials and presents them on a screen for selection by the user. The user is able to select an account for accomplishing the transaction, for example, by touching the screen. After the user selects an account, transaction device 103 sends an indication of that account to credential processor 107.
  • FIG. 3A is an example process 300A for initializing account registration using a mobile device, consistent with disclosed embodiments.
  • In step 301, mobile device 101 sends user credentials and account credentials to credential issuer 108 to register each set of credentials. (In some embodiments, mobile device 101 may send user credentials and account credentials to an intermediate device such as credential processor 107 for forwarding to credential issuer 108.) Account credentials include, for example, a bank account number (including, for example, a Routing Transit Number and account number), a payment card number (including, for example, a bank card number printed on a debit card), or other account details. User credentials include, for example, an identifier associated with mobile device 101, a username and password, an e-mail address, biometric information, or the like. In the embodiment illustrated in FIG. 3A, step 301 is performed by a user using mobile device 101. In other embodiments, the user may send account credentials and user credentials to credential issuer 108 using other devices, such a personal computer, a transaction system, or the like. Still in other embodiments, the user may send account credentials and user credentials to credential issuer 108 using postal or electronic mail, may record the account credentials and/or user credentials during a telephone call with an automated system, or through any other means.
  • In step 303, credential issuer 108 receives account credentials and user credentials from mobile device 101. (In some embodiments, credential issuer 108 may receive the account credentials and user credentials from an intermediate device such as credential processor 107.) Credential issuer 108 generates a substitute value corresponding to the received account credentials. The substitute value may take any form, for example, alphanumeric, alphabetic, numeric, text, hash-based, or binary. In some embodiments, the substitute value may be formed such that transaction device 103 recognizes it as associated with a particular network (such as payment network 113).
  • As one example, the substitute value may be in the form of a constructed value. A constructed value, in some embodiments, comprises a string of numbers formatted to resemble a payment card number. For example, such a constructed value may contain a particular value as part of the BIN (Bank Identification Number), such as ‘59,’ which indicates that the constructed value is associated with a particular network (such as payment network 113). Although the constructed value does not correspond to a particular account, the constructed value's attribute of resembling a payment card number facilitates routing a transaction that includes the constructed value via payment network 113, as though it were a traditional card-based transaction.
  • Credential issuer 108 sends the received account credentials and generated substitute value to payment network 113. In step 305, payment network 113 receives the account credentials and/or substitute value, and determines whether the account credentials or substitute value comprise a payment card number, also known as a PAN (Primary Account Number). If so, then, in step 309, payment network 113 validates the PAN. To validate the PAN, payment network 113 may communicate with a financial institution associated with the PAN (e.g., a bank that stores the account associated with the PAN), may make small monetary deposits into the account associated with the PAN and request the user to confirm the deposits, or the like. If the PAN is validated, payment network sends a confirmation to credential issuer 108. In step 311, credential issuer 108 stores the substitute value in association with the PAN received in step 303. Credential issuer 108 may store the substitute value in a look-up or cross-reference (“XREF”) database in association with the account credentials received in step 303. In some embodiments, credential issuer 108 sends the substitute value to credential processor 107 and in step 313, credential processor 107 stores the substitute value.
  • However, if in step 305, payment network 113 determines that the account credentials comprise something other than a PAN, such as a Routing Transit Number and account number, payment network 113 validates the received account credentials in step 307. To validate the account credentials, payment network 113 may communicate with a financial institution associated with the credentials (e.g., a bank that stores the account associated with the credentials), may make small monetary deposits into the account associated with the credentials and request the user to confirm the deposits, or the like. If the account credentials are validated, payment network 113 sends a confirmation to credential issuer 108.
  • FIG. 3B is an example process 300B for initializing a transaction using mobile device 101, consistent with some embodiments.
  • In step 314, mobile device 101 sends a request to credential processor 107, requesting a list of accounts associated with a particular user. For example, credential processor 107 may have a database containing user credentials (e.g., a username/password combination) associated with a user and/or one or more accounts associated with the user. In step 315, credential processor 107 determines accounts associated with received user credentials and sends a list of these accounts to mobile device 101. For example, credential processor 107 determines a list of such accounts by consulting a database which associates user credentials and account credentials or substitute values. Credential processor 107, in some embodiments, sends a list of the accounts associated with the received user credentials without sending any account credentials like account numbers or card numbers. The list sent by credential processor 107 may comprise titles (such as “Bank A Deposit Account #1”) or portions of account information (such as “Bank B Savings Account XXXXX3667”).
  • Mobile device 101 receives the account list and presents the list to the user. In step 317, mobile device 101 receives a selection of an account with which to accomplish a desired transaction, and sends that selection to credential processor 107. In some embodiments, in step 319, credential processor 107 determines a substitute value associated with the selected account based on the received user credentials and account selection. The process then continues to FIG. 3D for processing the transaction.
  • In other embodiments, credential processor 107 may be configured to send a dynamic token in lieu of or in addition to the substitute value to transaction device 103 or mobile device 101. In these embodiments, in step 320, credential processor 107 generates and sends a request for a dynamic token to credential issuer 108. The request includes, for example, the determined substitute value associated with the selected account, an identifier associated with transaction device 103 or mobile device 101, or the like. In step 322, credential issuer 108 generates a dynamic token that corresponds to the substitute value and stores it in a database for later look-up. The token may be in the form of a number, a string of letters, an alphanumeric string, or any identifier that enables credential issuer to determine an associated substitute value. In some embodiments, the dynamic token may conform to the format of a PAN, also known as a Primary Account Number. Credential issuer 108 then sends the token to credential processor 107.
  • FIG. 3C is another example process for initializing a transaction, using transaction device 103, consistent with the disclosed embodiments. One of ordinary skill will understand that FIG. 3C is an alternative process to that depicted in FIG. 3B. In step 321, transaction device 103 receives user credentials. For example, a user may use a keypad to enter user credentials at transaction device 103. As described above, any type of credential may be provided by the user including, for example, an identifier associated with mobile device, an e-mail address, phone number, biometric information (e.g., fingerprint scan, facial recognition, or retina scan) or the like. Transaction device can also receive user credentials from mobile device 101 (e.g., over a wired/wireless connection with mobile device 101).
  • In step 323, transaction device 103 sends the user credentials with a request for a listing of account associated with a particular user. For example, credential processor 107 may have one or more accounts associated with user credentials (e.g., a username/password combination). In step 325, credential processor 107 determines accounts associated with received user credentials and sends a list of these accounts to transaction device 103. For example, credential processor 107 determines a list of such accounts by consulting a database which associates user credentials and account credentials. Credential processor 107 then, in some embodiments, sends a list of the accounts associated with the received user credentials to transaction device 103 without sending any account credentials like account numbers or card numbers. The list sent by credential processor 107 may comprise titles (such as “Bank A Deposit Account #1”) or portions of account information (such as “Bank B Savings Account XXXXX3667”).
  • Transaction device 103 receives the account list and presents the list to the user. In step 327, the user selects one of the presented accounts using, for example, a touchscreen or a keypad on transaction device 103. Transaction device 103 then sends an indication of the selected account to credential processor 107. In some embodiments, in step 329, credential processor 107 determines a substitute value associated with the selected account based on the received user credentials and account selection. The process then continues to FIG. 3D for processing the transaction.
  • In other embodiments, credential processor 107 may be configured to send a dynamic token in lieu of or in addition to the substitute value to transaction device 103. In these embodiments, in step 330, credential processor 107 generates and sends a request for a dynamic token to credential issuer 108. The request includes, for example, the determined substitute value associated with the selected account, an identifier associated with transaction device 103, or the like. In step 332, credential issuer 108 generates a dynamic token that corresponds to the substitute value and stores it in a database for later look-up. The token may be in the form of a number, a string of letters, an alphanumeric string, or any identifier that enables credential issuer to determine an associated substitute value. Credential issuer 108 then sends the token to credential processor 107.
  • FIG. 3D is an example process 300D for processing a transaction using a transaction device 103 and a credential processor 107, consistent with disclosed embodiments.
  • In step 331, transaction device 103 receives the substitute value (which could be a constructed value or a dynamic token, as appropriate). Transaction device 103 also receives a transaction request. For example, a user may utilize a keypad or touchscreen on transaction device 103 to input the transaction type desired by a user, such as a withdrawal, deposit, balance inquiry, bill payment, fund transfer, or the like. The transaction type received by transaction device 103 may be a transaction parameter. In some embodiments, a transaction request may include more than one transaction parameter. For example, if a user wants to withdraw $20.00 and purchase a book of stamps, the transaction request can include two transaction parameters—a first indicating a withdrawal of $20.00 and a second indicating a purchase of a book of stamps.
  • In embodiments where the substitute value is a constructed value, transaction device 103 also may determine a payment network associated with the constructed value, such as payment network 113. In some embodiments, this may involve routing the transaction to another payment network within payment network 113 that is associated with the constructed value. As discussed previously, constructed values may contain an indicator value, such as a Bank Identification Number (BIN). Transaction device 103 may use the indicator value to determine the correct payment network. In this case, transaction device 103 may determine that the indicator value comprises the value ‘59’ and that an indicator value of ‘59’ corresponds to payment network 113. In such embodiments, in step 333, transaction device 103 may send the transaction request and the constructed value to payment network 113 and proceed to step 335, as discussed below.
  • In other embodiments, for example, where the substitute value is not a constructed value (being, for example, a username, phone number, or other identifier), transaction device 103 may recognize the substitute value as being associated with payment network 113. In such embodiments, in step 333, transaction device 103 may send the transaction request and the substitute value to payment network 113 and proceed to step 337, as discussed below.
  • Still in other embodiments, transaction device 103 may recognize that the substitute value is a dynamic token. Such tokens are associated with credential issuer 108. In such embodiments, in step 333, transaction device 103 may send the transaction and dynamic token to credential issuer 108 and proceed to step 334. Credential issuer 108 may store an association between a token and account credentials. When, at step 334, credential issuer 108 receives a dynamic token associated with a transaction request, credential issuer 108 can perform a lookup in a table to determine account credentials for processing the transaction (such as a substitute value). Based on the determined substitute value, credential issuer may forward the transaction request and substitute value to payment network 113.
  • Communications by transaction device at step 333 may, in some embodiments, comprise at least one of the received substitute value, information concerning the requested transaction, an identification associated with transaction device 103, the current time or date, or other information.
  • Continuing the description of the illustrative transaction flow, in step 335, payment network 113 may recognize the indicator value included in the received constructed value, and from the indicator value, determine a corresponding payment network. As described above, the corresponding payment network may be the same or a different payment network within payment network 113 and may be operated or controlled by the same or separate entities.
  • In step 337, payment network 113 may receive the transaction request and substitute value from credential issuer 108, or from the determination of an indicator value in step 335. Payment network 113 then performs a cross-reference in a database to determine account credentials corresponding to the received substitute value. As explained above with respect to FIG. 3A, the account credentials may include, for example, a bank account number (including, for example, a Routing Transit Number and account number), a payment card number (including, for example, a card number printed on a debit card), or other account details.
  • Once payment network 113 determines the account credentials corresponding to the received substitute value, the process continues to step 339. In step 339, payment network 113 determines whether the account credentials comprise a payment card number (also known as a PAN or Primary Account Number). If not, the process continues to step 345, where payment network 113 processes the transaction using the account credentials. Processing the transaction in step 345 comprises, for example, payment network 113 determining which financial institution contains the account corresponding to a determined Routing Transit Number, recording the effect of the transaction (e.g., a debit or a credit), and initiating communication with the determined financial institution 300.
  • Payment network 113 sends the transaction request to the financial institution associated with a determined Routing Transit Number, financial institution 300. Financial institution 300 contains the account associated with the received account credentials, and may be one of domestic bank 111 or receiver 115. In step 347, financial institution 300 receives the transaction and effects the transaction against the account requested by the user. For example, if the transaction indicates that the user wants to withdraw money from the account, financial institution 300 debits the account by the amount that the user wishes to withdraw. In some embodiments, financial institution 300 may add a fee to the amount debited from the user's account, to account for service fee(s) imposed by one of financial institution 300, payment network 113, or transaction device 103. As another example, if the transaction request indicates a desire to deposit funds, financial institution 300 credits the determined account.
  • After processing the transaction in step 347, financial institution 300 returns a confirmation message to payment network 113 indicating whether the transaction request succeeded or failed.
  • However, if in step 339, payment network 113 determines that the account credentials associated with the substitute value comprise a PAN, payment network 113 may process the transaction as a PAN transaction. Processing the transaction as a PAN transaction comprises, for example processing the transaction using processes utilized for card-based transactions. In some embodiments, this may involve routing the transaction to another payment network within payment network 113 that is associated with the PAN. Processing the transaction in step 341 comprises, for example, payment network 113 determining which financial institution contains the account corresponding to a received PAN, recording the effect of the transaction (e.g., a debit or a credit), and initiating communication with the determined financial institution 300.
  • Payment network 113 sends the transaction request to the financial institution associated with the PAN, financial institution 300. Financial institution 300 contains the account associated with the received account credentials, and may be one of domestic bank 111 or receiver 115. In step 347, financial institution 300 receives the transaction and effects the transaction against the account requested by the user. For example, if the transaction indicates that the user wants to withdraw money from the account, financial institution 300 debits the account by the amount that the user wishes to withdraw. In some embodiments, financial institution 300 may add a fee to the amount debited from the user's account, to account for service fee(s) imposed by one of financial institution 300, payment network 113, or transaction device 103. As another example, if the transaction request indicates a desire to deposit funds, financial institution 300 credits the determined account. Financial institution 300 then returns a confirmation message to payment network 113 indicating whether the transaction request succeeded or failed.
  • In some embodiments, financial institution 300 effects the transaction against the account based on the type of transaction (e.g., PAN transaction or account transaction). For example, if financial institution 300 receives a PAN for processing the transaction, financial institution 300 may consult a database to determine an account number that corresponds to the PAN, in order to determine which account the transaction should be effected against.
  • In step 349, payment network 113 receives a confirmation message from financial institution 300. Payment network 113 may record the confirmation message (e.g., for auditing purposes) and forward the confirmation message to transaction device 103. Transaction device 103 receives the confirmation message and completes the transaction request appropriately. For example, if the confirmation message from financial institution 300 indicates that a withdrawal transaction request was successful, transaction device 103 may complete the transaction request by dispensing funds to the user through cash drawer 103D. If the confirmation message from financial institution 300 indicates that a deposit transaction request was successful, transaction device 103 may complete the transaction request by receiving funds from the user through cash drawer 103D.
  • FIG. 4 illustrates example computer system 400 for implementing the disclosed embodiments. Each component depicted in these figures (e.g., mobile device 101, transaction device 103, credential processor 107, credential issuer 108, domestic bank 111, payment network 113, and receiver 115) may be implemented as illustrated in computer system 400. In some embodiments, the components in FIG. 4 may be duplicated, substituted, or omitted. In some embodiments, system 400 can be implemented, as appropriate, as a cellular phone, a mobile device, a POS (point-of-sale) device, a transaction device, an ATM, a cash-dispensing, pre-paid card loading or reload, check cashing or deposit, or other value-dispensing device, a server, a wireless device, or any other system that includes at least some of the components of FIG. 4. Each of the components in FIG. 4 can be connected to one another using, for example, a wired interconnection system such as a bus.
  • System 400 comprises power unit 401. Power unit 401 can be implemented as a battery, a power supply, or the like. Power unit 401 provides the electricity necessary to power the other components in system 400. For example, CPU 402 needs power to operate. Power unit 401 can provide the necessary electric current to power this component.
  • System 400 contains a Central Processing Unit (CPU) 402, which enables data to flow between the other components and manages the operation of the other components in computer system 400. CPU 402, in some embodiments, can be implemented as a general-purpose processor (such as an Intel- or AMD-branded processor), a special-purpose processor (for example, a graphics-card processor or a mobile processor), or any other kind of processor that enables input and output of data.
  • System 400 also comprises output device 403. Output device 403 can be implemented as a monitor, printer, speaker, plotter, or any other device that presents data processed, received, or sent by computer system 400.
  • System 400 also comprises network adapter 404. Network adapter 404, in some embodiments, enables communication with other devices that are implemented in the same or similar way as computer system 400. Network adapter 404, in some embodiments, may allow communication to and/or from a network such as the Internet. Network adapter 404 may be implemented using any or all of known or as-yet-unknown wired or wireless technologies (such as Ethernet, 802.11a/b/g/n (aka Wi-Fi), cellular (e.g. GSM, CDMA, LTE), or the like).
  • System 400 also comprises input device 405. In some embodiments, input device 405 may be any device that enables a user or other entity to input data. For example, input device 405 could be a keyboard, a mouse, or the like. Input device 405 can be used to control the operation of the other components illustrated in FIG. 4.
  • System 400 also includes storage device 406. Storage device 406 stores data that is usable by the other components in system 400. Storage device 406 may, in some embodiments, be implemented as a hard drive, temporary memory, permanent memory, optical memory, or any other type of permanent or temporary storage device. Storage device 406 may store one or more modules of computer program instructions and/or code that creates an execution environment for the computer program in question, such as, for example, processor firmware, a protocol stack, a database management system, an operating system, or a combination thereof.
  • The term “processor system,” as used herein, refers to one or more processors (such as CPU 402). The disclosed systems may be implemented in part or in full on various computers, electronic devices, computer-readable media (such as CDs, DVDs, flash drives, hard drives, or other storage), or other electronic devices or storage devices. The methods and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit). While disclosed processes include particular process flows, alternative flows or orders are also possible in alternative embodiments.
  • Certain features which, for clarity, are described in this specification in the context of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features which, for brevity, are described in the context of a single embodiment may also be provided in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
  • Particular embodiments have been described. Other embodiments are within the scope of the following claims.

Claims (28)

What is claimed is:
1. A method for processing a financial transaction, comprising:
receiving, at an electronic device, a transaction request including at least one transaction parameter;
receiving, at the electronic device, a substitute value, the substitute value being associated with an account for processing the transaction request and being distinct from an account number associated with the account;
determining, at the electronic device, whether the substitute value is associated with a payment network;
sending the at least one transaction parameter and the substitute value to the payment network; and
completing, at the electronic device, the transaction request based on a response received from the payment network.
2. The method of claim 1, wherein the at least one transaction parameter comprises an indication of at least one of a withdrawal, a deposit, a transfer, or a balance inquiry, and wherein completing the transaction request comprises at least one of providing funds, receiving funds, providing an indication of success or failure of the transaction request, providing a balance associated with the account, or declining the transaction request.
3. The method of claim 1, wherein the substitute value is a constructed value in the form of a payment card number containing an indicator value associated with the payment network, the indicator value not identifying a financial institution containing the account.
4. The method of claim 3, wherein the indicator value associates the constructed value with a second payment network.
5. The method of claim 1, wherein the substitute value comprises a dynamic token associated with account credentials, the dynamic token being usable for only one transaction.
6. The method of claim 1, wherein the step of receiving a response comprises receiving a response generated by the payment network.
7. The method of claim 1, wherein the electronic device is an Automated Teller Machine (ATM) or a point-of-sale (POS) device.
8. A method for processing a financial transaction, comprising:
receiving at a computer associated with a payment network, from an electronic device, a transaction request including at least one transaction parameter and a substitute value, the substitute value being associated with an account for processing the transaction request and being distinct from an account number associated with the account;
determining account credentials associated with the substitute value;
determining whether the determined account credentials comprise bank account information or a payment card number associated with the account; and
based on the account credentials determination, using the computer, processing the transaction request and sending the transaction request and determined account credentials to a financial institution.
9. The method of claim 8, further comprising:
determining, via the computer, whether the substitute value contains an indicator value that associates the substitute value with a second payment network.
10. The method of claim 8, further comprising:
generating the substitute value in response to receiving account credentials and user credentials from one of the electronic device or a mobile device; and
storing, in a database, the substitute value in association with the user credentials.
11. The method of claim 8, wherein the at least one transaction parameter comprises an indication of at least one of a withdrawal, a deposit, a transfer, or a balance inquiry.
12. The method of claim 8, wherein the substitute value is a constructed value in the form of a payment card number containing an indicator value associated with the payment network, the indicator value not identifying a financial institution containing the account.
13. The method of claim 12, wherein the indicator value associates the constructed value with a second payment network.
14. The method of claim 8, wherein the electronic device is an Automated Teller Machine (ATM) or a point-of-sale (POS) device.
15. A system for processing a financial transaction, comprising:
a processor system; and
storage containing computer-readable instructions, the instructions configured to, when executed by the processor system, cause the processor system to:
receive a transaction request including at least one transaction parameter;
receive a substitute value, the substitute value being associated with an account for processing the transaction request and being distinct from an account number associated with the account;
determine whether the substitute value is associated with a payment network;
send the at least one transaction parameter and the substitute value to the payment network; and
complete the transaction request based on a response received from the payment network.
16. The system of claim 15, wherein the at least one transaction parameter comprises an indication of at least one of a withdrawal, a deposit, a transfer, or a balance inquiry, and wherein completing the transaction request comprises at least one of providing funds, receiving funds, providing an indication of success or failure of the transaction request, providing a balance associated with the account, or declining the transaction request.
17. The system of claim 15, wherein the substitute value is a constructed value in the form of a payment card number containing an indicator value associated with the payment network, the indicator value not identifying a financial institution containing the account.
18. The system of claim 17, wherein the indicator value associates the constructed value with a second payment network.
19. The system of claim 15, wherein the substitute value comprises a dynamic token associated with account credentials, the dynamic token being usable for only one transaction.
20. The system of claim 15, wherein the step of receiving a response comprises receiving a response generated the payment network.
21. The system of claim 15, wherein the electronic device is an Automated Teller Machine (ATM) or point-of-sale (POS) device.
22. A system for processing a financial transaction, comprising:
a processor system associated with a payment network; and
storage containing computer-readable instructions, the instructions configured to, when executed by the processor system, cause the processor system to:
receive, from an electronic device, a transaction request including at least one transaction parameter and a substitute value, the substitute value being associated with an account for processing the transaction request and being distinct from an account number associated with the account;
determine account credentials associated with the substitute value;
determine whether the determined account credentials comprise bank account information or a payment card number associated with the account; and
based on the account credentials determination, process the transaction request and send the transaction request and the determined account credentials to a financial institution.
23. The system of claim 22, wherein the instructions are further configured to cause the processor system to: determine whether the substitute value contains an indicator value that associates the substitute value with a second payment network.
24. The system of claim 22, wherein the instructions are further configured to cause the processor system to:
generate the substitute value in response to receiving account credentials and user credentials from one of the electronic device or a mobile device; and
store, in a database, the substitute value in association with the user credentials.
25. The system of claim 22, wherein the at least one transaction parameter comprises an indication of at least one of a withdrawal, a deposit, a transfer, or a balance inquiry.
26. The system of claim 22, wherein the substitute value is a constructed value in the form of a payment card number containing an indicator value associated with the payment network, the indicator value not identifying a financial institution containing the account.
27. The system of claim 26, wherein the indicator value associates the constructed value with a second payment network.
28. The system of claim 22, wherein the electronic device is an Automated Teller Machine (ATM) or point-of-sale (POS) device.
US14/154,111 2014-01-13 2014-01-13 Systems and methods for processing cardless transactions Pending US20150199671A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/154,111 US20150199671A1 (en) 2014-01-13 2014-01-13 Systems and methods for processing cardless transactions

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US14/154,111 US20150199671A1 (en) 2014-01-13 2014-01-13 Systems and methods for processing cardless transactions
PCT/US2015/010454 WO2015105857A1 (en) 2014-01-13 2015-01-07 Systems and methods for processing cardless transactions
EP15735480.4A EP3095078A4 (en) 2014-01-13 2015-01-07 Systems and methods for processing cardless transactions
HK17105120.3A HK1231610A1 (en) 2014-01-13 2017-05-19 Systems and methods for processing cardless transactions

Publications (1)

Publication Number Publication Date
US20150199671A1 true US20150199671A1 (en) 2015-07-16

Family

ID=53521719

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/154,111 Pending US20150199671A1 (en) 2014-01-13 2014-01-13 Systems and methods for processing cardless transactions

Country Status (4)

Country Link
US (1) US20150199671A1 (en)
EP (1) EP3095078A4 (en)
HK (1) HK1231610A1 (en)
WO (1) WO2015105857A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150095130A1 (en) * 2013-09-30 2015-04-02 Capital One Financial Corporation Systems and methods for providing a customer service
WO2018005255A1 (en) * 2016-06-29 2018-01-04 Mastercard International Incorporated Method and system for cardless disbursement from an automated teller machine
US10475009B2 (en) 2015-10-29 2019-11-12 Mastercard International Incorporated Method and system for cardless use of an automated teller machine (ATM)
US10614442B2 (en) 2014-12-03 2020-04-07 Mastercard International Incorporated System and method of facilitating cash transactions at an ATM system without an ATM card using mobile

Citations (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020152180A1 (en) * 1999-09-10 2002-10-17 Paul Turgeon System and method for performing secure remote real-time financial transactions over a public communications infrastructure with strong authentication
US20030120936A1 (en) * 2001-08-01 2003-06-26 Eft Datalink Encryption of financial information
US20080082444A1 (en) * 2004-10-07 2008-04-03 International Business Machines Corporation Controlling Electronic Withdrawals
US7433845B1 (en) * 1999-04-13 2008-10-07 Orbis Patents Limited Data structure, method and system for generating person-to-person, person-to-business, business-to-person, and business-to-business financial transactions
US20090083191A1 (en) * 2006-06-19 2009-03-26 Ayman Hammad Track data encryption
US20100174620A1 (en) * 2009-01-08 2010-07-08 Visa Europe Limited Payment system
US20100185545A1 (en) * 2009-01-22 2010-07-22 First Data Corporation Dynamic primary account number (pan) and unique key per card
US20110106659A1 (en) * 2009-11-02 2011-05-05 Patrick Faith Encryption Switch Processing
US20110153496A1 (en) * 2009-12-18 2011-06-23 First Data Corporation Authentication of card-not-present transactions
US7979348B2 (en) * 2002-04-23 2011-07-12 Clearing House Payments Co Llc Payment identification code and payment system using the same
US20110258111A1 (en) * 2010-04-19 2011-10-20 Thanigaivel Ashwin Raj Alias management and off-us dda processing
US20120150687A1 (en) * 2010-12-13 2012-06-14 Hart Annmarie D Systems and methods for conducting contactless payments using a mobile device and a magstripe payment card
US20120209749A1 (en) * 2011-02-16 2012-08-16 Ayman Hammad Snap mobile payment apparatuses, methods and systems
US20120292389A1 (en) * 1998-04-17 2012-11-22 Diebold Self-Service Systems Division Of Diebold, Incorporated Banking System Controlled Responsive to Data Bearing Records
US20120303425A1 (en) * 2011-02-05 2012-11-29 Edward Katzin Merchant-consumer bridging platform apparatuses, methods and systems
US20120317035A1 (en) * 2009-01-22 2012-12-13 First Data Corporation Processing transactions with an extended application id and dynamic cryptograms
US20120317628A1 (en) * 2011-06-09 2012-12-13 Yeager C Douglas Systems and methods for authorizing a transaction
US20120316992A1 (en) * 2011-06-07 2012-12-13 Oborne Timothy W Payment privacy tokenization apparatuses, methods and systems
US20130024371A1 (en) * 2011-02-22 2013-01-24 Prakash Hariramani Electronic offer optimization and redemption apparatuses, methods and systems
US8496168B1 (en) * 1998-04-17 2013-07-30 Diebold Self-Service Systems Division Of Diebold, Incorporated Banking system controlled responsive to data bearing records
US20130218769A1 (en) * 2011-08-23 2013-08-22 Stacy Pourfallah Mobile Funding Method and System
US20130226799A1 (en) * 2011-08-23 2013-08-29 Thanigaivel Ashwin Raj Authentication process for value transfer machine
US20130246274A1 (en) * 2012-03-19 2013-09-19 Paynet Payments Network, Llc Systems and methods for real-time account access
US20130246199A1 (en) * 2012-03-14 2013-09-19 Mark Carlson Point-of-transaction account feature redirection apparatuses, methods and systems
US20140046842A1 (en) * 2012-08-09 2014-02-13 Diebold Self-Service Systems Division Of Diebold, Incorporated Accepting a check deposit from a mobile device in communication with an automated teller machine
US20140074724A1 (en) * 2012-03-19 2014-03-13 PayNet Payments Networks, LLC Systems and methods for real-time account access
US20140108249A1 (en) * 2011-04-11 2014-04-17 Ashish Kulpati Interoperable financial transactions via mobile devices
US20140164243A1 (en) * 2012-12-07 2014-06-12 Christian Aabye Dynamic Account Identifier With Return Real Account Identifier
US20140263618A1 (en) * 2013-03-14 2014-09-18 First Data Corporation Systems and methods for transferring funds using a wireless device
US8840016B1 (en) * 1998-04-17 2014-09-23 Diebold Self-Service Systems Division Of Diebold, Incorporated Banking system controlled responsive to data bearing records
US20140358777A1 (en) * 2013-05-31 2014-12-04 How Kiap Gueh Method for secure atm transactions using a portable device
US20150019443A1 (en) * 2013-07-15 2015-01-15 John Sheets Secure remote payment transaction processing
US20150032625A1 (en) * 2013-07-24 2015-01-29 Matthew Dill Systems and methods for communicating risk using token assurance data
US20150088756A1 (en) * 2013-09-20 2015-03-26 Oleg Makhotin Secure Remote Payment Transaction Processing Including Consumer Authentication
US20150120418A1 (en) * 2013-10-28 2015-04-30 Visa International Service Association Systems and methods to provide rewards based on purchased items
US20150127547A1 (en) * 2013-10-11 2015-05-07 Glenn Leon Powell Network token system
US20150154597A1 (en) * 2008-02-20 2015-06-04 Collective Dynamics LLC Method and System for Secure Transactions
US9251510B2 (en) * 2007-11-30 2016-02-02 U.S. Bank National Association Buyer routing arrangements and methods for disparate network systems
US9785944B2 (en) * 2003-07-01 2017-10-10 Visa U.S.A. Inc. Method and system for providing risk information in connection with transaction processing
US9881297B2 (en) * 2008-11-14 2018-01-30 Mastercard International Incorporated Methods and systems for secure mobile device initiated payments using generated image data
US10248949B2 (en) * 2012-05-29 2019-04-02 CardLab ApS. Method for encrypting transactions at a dynamic transaction card

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7146338B2 (en) * 2001-06-28 2006-12-05 Checkfree Services Corporation Inter-network financial service
EP1817735A4 (en) * 2004-10-19 2009-07-08 Apollo Entpr Solutions Llc System and method for resolving transactions
US7506804B2 (en) * 2005-05-27 2009-03-24 U.S. Bancorp Licensing, Inc. System and method for an integrated payment and reward card
US10275764B2 (en) * 2012-05-04 2019-04-30 Mastercard International Incorporated Transaction data tokenization
US9262755B2 (en) * 2012-06-20 2016-02-16 Intuit Inc. Mobile payment system

Patent Citations (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8840016B1 (en) * 1998-04-17 2014-09-23 Diebold Self-Service Systems Division Of Diebold, Incorporated Banking system controlled responsive to data bearing records
US8496168B1 (en) * 1998-04-17 2013-07-30 Diebold Self-Service Systems Division Of Diebold, Incorporated Banking system controlled responsive to data bearing records
US20120292389A1 (en) * 1998-04-17 2012-11-22 Diebold Self-Service Systems Division Of Diebold, Incorporated Banking System Controlled Responsive to Data Bearing Records
US7433845B1 (en) * 1999-04-13 2008-10-07 Orbis Patents Limited Data structure, method and system for generating person-to-person, person-to-business, business-to-person, and business-to-business financial transactions
US20020152180A1 (en) * 1999-09-10 2002-10-17 Paul Turgeon System and method for performing secure remote real-time financial transactions over a public communications infrastructure with strong authentication
US20030120936A1 (en) * 2001-08-01 2003-06-26 Eft Datalink Encryption of financial information
US20130262296A1 (en) * 2002-04-23 2013-10-03 George F. Thomas Payment identification code and payment system using the same
US20140164246A1 (en) * 2002-04-23 2014-06-12 The Clearing House Payments Company L.L.C. Payment identification code and payment system using the same
US20150324801A1 (en) * 2002-04-23 2015-11-12 The Clearing House Payments Company L.L.C. Payment identification code and payment system using the same
US7979348B2 (en) * 2002-04-23 2011-07-12 Clearing House Payments Co Llc Payment identification code and payment system using the same
US20110295746A1 (en) * 2002-04-23 2011-12-01 Thomas George E Payment identification code and payment system using the same
US9785944B2 (en) * 2003-07-01 2017-10-10 Visa U.S.A. Inc. Method and system for providing risk information in connection with transaction processing
US20080082444A1 (en) * 2004-10-07 2008-04-03 International Business Machines Corporation Controlling Electronic Withdrawals
US20090083191A1 (en) * 2006-06-19 2009-03-26 Ayman Hammad Track data encryption
US9251510B2 (en) * 2007-11-30 2016-02-02 U.S. Bank National Association Buyer routing arrangements and methods for disparate network systems
US20150154597A1 (en) * 2008-02-20 2015-06-04 Collective Dynamics LLC Method and System for Secure Transactions
US9881297B2 (en) * 2008-11-14 2018-01-30 Mastercard International Incorporated Methods and systems for secure mobile device initiated payments using generated image data
US20100174620A1 (en) * 2009-01-08 2010-07-08 Visa Europe Limited Payment system
US20100185545A1 (en) * 2009-01-22 2010-07-22 First Data Corporation Dynamic primary account number (pan) and unique key per card
US20120317035A1 (en) * 2009-01-22 2012-12-13 First Data Corporation Processing transactions with an extended application id and dynamic cryptograms
US20110106659A1 (en) * 2009-11-02 2011-05-05 Patrick Faith Encryption Switch Processing
US20110153496A1 (en) * 2009-12-18 2011-06-23 First Data Corporation Authentication of card-not-present transactions
US20110258111A1 (en) * 2010-04-19 2011-10-20 Thanigaivel Ashwin Raj Alias management and off-us dda processing
US20120150687A1 (en) * 2010-12-13 2012-06-14 Hart Annmarie D Systems and methods for conducting contactless payments using a mobile device and a magstripe payment card
US20120303425A1 (en) * 2011-02-05 2012-11-29 Edward Katzin Merchant-consumer bridging platform apparatuses, methods and systems
US20120209749A1 (en) * 2011-02-16 2012-08-16 Ayman Hammad Snap mobile payment apparatuses, methods and systems
US20130024371A1 (en) * 2011-02-22 2013-01-24 Prakash Hariramani Electronic offer optimization and redemption apparatuses, methods and systems
US20140108249A1 (en) * 2011-04-11 2014-04-17 Ashish Kulpati Interoperable financial transactions via mobile devices
US20120316992A1 (en) * 2011-06-07 2012-12-13 Oborne Timothy W Payment privacy tokenization apparatuses, methods and systems
US20120317628A1 (en) * 2011-06-09 2012-12-13 Yeager C Douglas Systems and methods for authorizing a transaction
US20130218769A1 (en) * 2011-08-23 2013-08-22 Stacy Pourfallah Mobile Funding Method and System
US20130226799A1 (en) * 2011-08-23 2013-08-29 Thanigaivel Ashwin Raj Authentication process for value transfer machine
US20130246199A1 (en) * 2012-03-14 2013-09-19 Mark Carlson Point-of-transaction account feature redirection apparatuses, methods and systems
US20130246274A1 (en) * 2012-03-19 2013-09-19 Paynet Payments Network, Llc Systems and methods for real-time account access
US20140074724A1 (en) * 2012-03-19 2014-03-13 PayNet Payments Networks, LLC Systems and methods for real-time account access
US10248949B2 (en) * 2012-05-29 2019-04-02 CardLab ApS. Method for encrypting transactions at a dynamic transaction card
US20140046842A1 (en) * 2012-08-09 2014-02-13 Diebold Self-Service Systems Division Of Diebold, Incorporated Accepting a check deposit from a mobile device in communication with an automated teller machine
US20140164243A1 (en) * 2012-12-07 2014-06-12 Christian Aabye Dynamic Account Identifier With Return Real Account Identifier
US20140263618A1 (en) * 2013-03-14 2014-09-18 First Data Corporation Systems and methods for transferring funds using a wireless device
US20140358777A1 (en) * 2013-05-31 2014-12-04 How Kiap Gueh Method for secure atm transactions using a portable device
US20150019443A1 (en) * 2013-07-15 2015-01-15 John Sheets Secure remote payment transaction processing
US20150032625A1 (en) * 2013-07-24 2015-01-29 Matthew Dill Systems and methods for communicating risk using token assurance data
US20150088756A1 (en) * 2013-09-20 2015-03-26 Oleg Makhotin Secure Remote Payment Transaction Processing Including Consumer Authentication
US20150127547A1 (en) * 2013-10-11 2015-05-07 Glenn Leon Powell Network token system
US20150120418A1 (en) * 2013-10-28 2015-04-30 Visa International Service Association Systems and methods to provide rewards based on purchased items

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150095130A1 (en) * 2013-09-30 2015-04-02 Capital One Financial Corporation Systems and methods for providing a customer service
US10453087B2 (en) * 2013-09-30 2019-10-22 Capital One Services, Llc Systems and methods for providing a customer service
US10614442B2 (en) 2014-12-03 2020-04-07 Mastercard International Incorporated System and method of facilitating cash transactions at an ATM system without an ATM card using mobile
US10475009B2 (en) 2015-10-29 2019-11-12 Mastercard International Incorporated Method and system for cardless use of an automated teller machine (ATM)
WO2018005255A1 (en) * 2016-06-29 2018-01-04 Mastercard International Incorporated Method and system for cardless disbursement from an automated teller machine

Also Published As

Publication number Publication date
EP3095078A4 (en) 2017-10-11
WO2015105857A1 (en) 2015-07-16
HK1231610A1 (en) 2017-12-22
EP3095078A1 (en) 2016-11-23

Similar Documents

Publication Publication Date Title
US10592903B2 (en) Authorization of cardless payment transactions
RU2702085C2 (en) Return by payment channel providing restricted use dynamic value authority
US9530125B2 (en) Method and system for secure mobile payment transactions
US10366387B2 (en) Digital wallet system and method
JP2016106317A (en) System and method for transaction payments using mobile device
US20190385144A1 (en) Processing a transaction using multiple application identifiers
US20170206524A1 (en) System and method using authorization and direct credit messaging
US9047600B2 (en) Mobile and wearable device payments via free cross-platform messaging service, free voice over internet protocol communication, free over-the-top content communication, and universal digital mobile and wearable device currency faces
US10147084B2 (en) Methods and systems for providing a payment account with adaptive interchange
US20160210626A1 (en) Secure processing of electronic payments
US20200090182A1 (en) Authenticating remote transactions using a mobile device
US8792861B2 (en) Switching functions for mobile payments system
US20170017958A1 (en) Secure processing of electronic payments
US20190354981A1 (en) Mobile Device Payments
US9767442B2 (en) Money transfer system gateway service
US8635157B2 (en) Mobile system and method for payments and non-financial transactions
US20200097962A1 (en) Systems and methods for real-time account access
EP2526517B1 (en) Token based transaction authentication
EP2637131B1 (en) Method of performing transactions with contactless payment devices using pre-tap and two-tap operations
RU2563163C2 (en) Remote variable authentication processing
AU2012242763B2 (en) Message routing using logically independent recipient identifiers
US8818868B2 (en) Foreign currency solution
JP5646083B2 (en) System and method for receiving payment at a point of service via wireless communication
US9779396B2 (en) Method of making mobile payments to a recipient lacking a wireless or contactless terminal
US9277390B2 (en) Mobile payment and identity verification system

Legal Events

Date Code Title Description
AS Assignment

Owner name: FIDELITY NATIONAL E-BANKING SERVICES, INC., FLORID

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAJAJ, HITESH;BROWN, DOUGLAS G.;WOODBURY, ROBERT;AND OTHERS;SIGNING DATES FROM 20140124 TO 20140317;REEL/FRAME:032504/0089

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STCB Information on status: application discontinuation

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: ADVISORY ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED