US20150294296A1 - Systems and computer-implemented processes for providing electronic notifications - Google Patents
Systems and computer-implemented processes for providing electronic notifications Download PDFInfo
- Publication number
- US20150294296A1 US20150294296A1 US14/682,053 US201514682053A US2015294296A1 US 20150294296 A1 US20150294296 A1 US 20150294296A1 US 201514682053 A US201514682053 A US 201514682053A US 2015294296 A1 US2015294296 A1 US 2015294296A1
- Authority
- US
- United States
- Prior art keywords
- account data
- service provider
- financial service
- mobile device
- information
- 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.)
- Granted
Links
Images
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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3221—Access to banking information through M-devices
-
- 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
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F19/00—Complete 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/20—Automatic teller machines [ATMs]
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F19/00—Complete 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/20—Automatic teller machines [ATMs]
- G07F19/206—Software aspects at ATMs
Definitions
- the disclosed embodiments generally relate providing electronic notifications.
- disclosed embodiments may use low energy technology to activate a mobile application to check an account balance.
- An automated teller machine is an electronic device that allows banking customers to carry out financial transactions without the need for a human teller.
- customers may use an ATM to access their bank accounts, deposit, withdraw, or transfer funds, check account balances, or dispense items of value.
- the customer may insert a banking card containing magnetic strip information into the ATM's card reader, and authenticate the card by entering a personal identification number (PIN). After the card has been read and authenticated, the customer can carry out various transactions related to their account. Since the widespread adoption of ATMs, customer use of bank branches has declined. However, customers may still conduct similar activities (and often additional activities) at a bank branch with the assistance of a bank teller.
- Mobile devices e.g., smartphones, tablets, etc.
- these devices equipped with financial provider applications with balance checking functionality offer an alternative way for customers to check their account balances.
- current applications typically require the customer to request his account balance in a process involving unlocking his device, logging into an application, and requesting account information.
- Disclosed embodiments include methods, systems, and non-transitory computer-readable storage media for enabling a customer to automatically receive account balance or other notifications such as safe spending limit information on a mobile device based on a customer's detected proximity to an ATM, bank teller station, or bank branch equipped with a wireless transmitter.
- transmitters can provide more accurate location information than other technologies and is not dependent on manually provided information.
- one type of transmitter low energy (LE) transmitters allow for micro-location of a mobile device that is a more precise predictor of a customer's location and presence at an ATM terminal or bank branch teller station.
- LE transmitters may be used in locations where other locating technologies falter, such as inside buildings where GPS or cellular signals may not penetrate.
- a mobile device for providing account data may comprise a display device, a memory storing instructions, and at least one processor configured to execute the instructions in the memory.
- the instructions in the memory may include instructions for detecting an identification signal, determining identification data based on the identification signal, and transmitting a request for account data based on the identification data.
- the instructions may further provide for receiving the requested account data and displaying the requested account data via the display device.
- the identification signal is transmitted from a low energy transmitter, and in some embodiments, the low energy transmitter is a BluetoothTM LE transmitter.
- the requested account data is received as a push notification, a text message, or an e-mail, and in some embodiments, the account data is the account balance or a safe spend limit.
- a computer-implemented method for providing account data may comprise detecting, by at least one processor, an identification signal and determining, by the at least one processor, identification data based on the identification signal. The method may further comprise transmitting, by the at least one processor, a request for account data based on the identification data and receiving, by the at least one processor, the requested account data. The method may also comprise displaying, by the at least one processor, the requested account data via the display device.
- the identification signal is transmitted from a low energy transmitter, and in some embodiments, the low energy transmitter is a BluetoothTM LE transmitter.
- a non-transitory computer-readable medium storing instructions for providing account data.
- the instructions may be executable by at least one processor, and the instructions may provide for detecting an identification signal, determining identification data based on the identification signal, and transmitting a request for account data based on at least the identification data.
- the instructions may also provide for receiving the requested account data and displaying the requested account data via the display device.
- the identification signal is transmitted from a low energy transmitter, and in some embodiments, the low energy transmitter is a BluetoothTM LE transmitter.
- FIG. 1 is an exemplary system that may be used to implement the disclosed embodiments.
- FIG. 2 is an exemplary mobile device configured to provide one or more aspects of the disclosed embodiments.
- FIG. 3 is an exemplary financial service provider system configured to provide one or more aspects of the disclosed embodiments.
- FIG. 4 is a flowchart of an exemplary process for automatically requesting and receiving account information via a mobile device.
- FIG. 5 is a flowchart of exemplary process for receiving a request for account information at a financial service provider system and transmitting a response from a financial service provider system to a mobile device.
- FIG. 1 is an exemplary system 100 configured to provide one or more aspects of the disclosed embodiments.
- the components and arrangements shown in FIG. 1 are not intended to be limiting to any disclosed embodiments, as the components used to implement the processes and features disclosed here may vary.
- system 100 may include one or more ATMs 101 and one or more bank teller stations or bank branches 105 (hereinafter referred to as “bank branch 105 ” for ease of reference).
- ATM 101 and bank branch 105 may be provided by or operated on behalf of a financial service provider that provides financial service provider system 130 (e.g., ATM 101 , bank branch 105 , and financial service provider system 130 may be owned and/or operated by the same financial service provider).
- ATM 101 and bank branch 105 are not provided by the same financial service provider that provides financial service provider system, but ATM 101 and bank branch 105 are associated with the financial service provider that provides financial service provider system 130 such that a customer of the financial service provider is capable of accessing account information and/or conducting transactions via ATM 101 and bank branch 105 (e.g., financial service provider does not own ATM 101 or bank branch 105 , but customers of the financial service provider can still access their accounts via ATM 101 and bank branch 105 ).
- ATM 101 may be associated with transmitter 102 and bank branch 105 may be associated with a transmitter 106 .
- Transmitter 102 may be located, for example, attached to the housing of the ATM, near the ATM (e.g., affixed to a door leading to the room with the ATM if the ATM is indoors), within the housing of the ATM, integrated into the hardware of the ATM, etc.
- Transmitter 106 may be located, for example, on the exterior of a bank branch (e.g., on an outside wall near the door of the bank branch, etc.) or within the bank branch (e.g., on an inside wall of the bank branch, at one or more bank teller stations, affixed to one or more bank teller computer terminals, within the housing of a bank teller computer terminal, integrated into the hardware of the bank teller computer terminal, etc.).
- Transmitters 102 and 106 may be any device capable of transmitting an identification signal.
- transmitters 102 and 106 are low energy (LE) transmitters or ultra-low energy transmitters.
- transmitters 102 and 106 are LE transmitter devices configured to transmit BluetoothTM LE signals.
- transmitters 102 and 106 transmit identification signals according to IBEACONTM protocols and standards.
- transmitters utilizing IBEACONTM include iBks101 beacons, AIRcable IBEACONTM dongles, devices configured with AIRcable BLE modules, BlueCats beacons, Bluebar beacons, devices configured with BlueGiga BluetoothTM modules, Estimote beacons, GeLo beacons, GIMBALTM beacons, Victor beacons, devices configured with Laird BL600 of DVK-BL600 iBeacon applications, devices configured with RADIUS NETWORKSTM IBEACONTM software, Sonic Notification beacons, etc.
- the signal transmitted by transmitters 102 and 106 may include any identification signal that identifies the transmitter.
- identification signals used by BluetoothTM LE transmitters include Proximity Universally Unique Identifier (UUID) information, Major identifier information, Minor identifier information, or combinations thereof.
- UUID Proximity Universally Unique Identifier
- transmitters may generally use unique identification signals, in some embodiments, more than one transmitter may use the same identification information. For example, all ATMs and bank branches associated with the same financial institution may use transmitters that transmit the same identification information, allowing the ATMs and bank branches to be identified as associated with the financial institution but without distinguishing between the ATMs and bank branches.
- Mobile device 110 is associated with a customer of the financial service provider that provides financial service provider system 130 .
- the customer may have one or more accounts (e.g., checking or savings accounts) provided by the financial service provider.
- Mobile device 110 may be any device capable of receiving transmitter signals.
- Mobile device 110 may include smartphones, tablets, or other mobile devices.
- Mobile device 110 may use any appropriate operating system, such as iOS, Windows Phone, Android, or BlackBerry operating systems.
- mobile device 110 may be capable of receiving BluetoothTM LE signals, sometimes called Bluetooth SMARTTM devices.
- Mobile device 110 may also be a device with a BluetoothTM LE integrated circuit.
- Mobile device 110 may also be any other mobile device (e.g., Google GlassTM) capable of receiving transmitter signals.
- Mobile device 110 may be configured to transmit requests for customer account information to financial provider system 130 , for example, via network 120 .
- Mobile device 110 may also be configured to receive customer account information from financial provider system 130 , for example, via network 120 . Further details regarding mobile device 110 are provided in FIG. 2 and its description.
- Network 120 may be any type of network that provides communications, exchanges information, and/or facilitates the exchange of information between mobile device 110 and financial service provider system 130 .
- network 120 may be the Internet, a Local Area Network, 3G telecommunications network, 4G telecommunications network, or other suitable connection(s) that enables bidirectional communication between various components of system 100 .
- Financial service provider system 130 may be associated with a financial account provider, such as, for example, a bank, lender, merchant, credit card provider, and any other entity that provides financial accounts to customers.
- a financial account provider such as, for example, a bank, lender, merchant, credit card provider, and any other entity that provides financial accounts to customers.
- Financial service provider system 130 may be configured to receive requests for customer account information from mobile device 110 , for example, via network 120 . Financial service provider system 130 may also be configured to transmit customer account information to mobile device 110 , for example, via network 120 . Further details regarding financial service provider system 130 are provided with respect to FIG. 3 .
- FIG. 2 is an exemplary mobile device 110 , consistent with disclosed embodiments.
- mobile device 110 may include one or more processor(s) 211 , one or more memory devices, such as memory 212 and identification data database 217 , interface components 213 , receiver 214 , and antenna 215 .
- Processor(s) 211 may be configured to execute instructions to provide processes and functionality as disclosed herein.
- Processor(s) 211 may be one or more known processing devices, such as a microprocessor from the PentiumTM family manufactured by IntelTM or the TurionTM family manufactured by AMDTM.
- Processor(s) 211 may include a single core or multiple core processor system that provides the ability to perform parallel processes simultaneously.
- processor(s) 211 may be a single core processor that is configured with virtual processing technologies known to those skilled in the art.
- processor(s) 211 may use logical processors to simultaneously execute and control multiple processes.
- Processor(s) 211 may implement virtual machine technologies, or other similar known technologies to provide the ability to execute, control, run, manipulate, store, etc.
- processor(s) 211 may include a multiple-core processor arrangement (e.g., dual or quad core) that is configured to provide parallel processing functionalities to allow mobile device 110 to execute multiple processes simultaneously.
- processor arrangement e.g., dual or quad core
- processor arrangements could be implemented that provide for the capabilities disclosed herein.
- Mobile device 110 may include one or more storage devices configured to store information used by processor(s) 211 (or other components) to perform certain functions related to the disclosed embodiments.
- mobile device 110 may include memory 212 that includes instructions to enable processor(s) 211 to execute one or more processes, such as mobile applications, network communication processes, and any other type of application or software known to be available on mobile device systems.
- the instructions, mobile application programs, etc. may be stored in an external storage or available from a memory over a network (e.g., network 120 ).
- the one or more storage devices may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, nonremovable, or other type of storage device or tangible computer-readable medium.
- memory 212 may store instructions that, when executed by processor(s) 211 , cause mobile device 110 to perform one or more processes consistent with the functionalities disclosed herein. Methods, systems, and articles of manufacture consistent with disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks.
- mobile device 110 may include a memory that may include one or more programs to perform one or more functions of interface components 213 and receiver 214 .
- processor(s) 211 may execute one or more programs located remotely from mobile device 110 . For example, mobile device 110 may access one or more remote programs, that, when executed, perform functions related to disclosed embodiments.
- Memory 212 may include or be associated with one or more memory devices that store data and instructions used to perform one or more features of the disclosed embodiments, and memory 212 may also include any combination of one or more databases controlled by memory controller devices (e.g., server(s), etc.) or software, such as document management systems, Microsoft SQL databases, SharePoint databases, OracleTM databases, SybaseTM databases, or other relational databases (see, e.g., identification data database 217 , described below).
- Mobile device 110 may also be communicatively connected to one or more memory devices (e.g., other databases not shown) locally or through a network.
- the remote memory devices may be configured to store information and may be accessed and/or managed by mobile device 110 .
- the remote memory devices may be document management systems, Microsoft SQL databases, SharePoint databases, OracleTM databases, SybaseTM databases, or other relational databases. Systems and methods of disclosed embodiments, however, are not limited to separate databases or even to the use of a database.
- Mobile device 110 may include identification data database 217 , which may include identification information for identifying transmitters associated with ATMs and/or bank branches associated with financial service provider system 130 .
- identification data database 217 may include one or more tables that link each unique identification information to its respective transmitter, the location (e.g., address) of the transmitter, and the ATM or bank branch with which it is associated.
- Identification data database 217 may be controlled by a memory controller device or software, such as document management systems, Microsoft SQL databases, SharePoint databases, OracleTM databases, SybaseTM databases, or other relational databases.
- identification data database 217 may be a remote memory device that may be accessed and/or managed by mobile device 110 .
- Mobile device 110 may also include one or more I/O devices that may comprise one or more interfaces for receiving signals or input from input devices and providing signals or output to one or more output devices that allow data to be received and/or transmitted by mobile device 110 .
- mobile device 110 may include interface components 213 that may provide interfaces to one or more input devices such as one or more display screens, on-screen keyboards, fingerprint recognition devices, and the like, that enable mobile device 110 to receive data from the customer and provide notifications to the customer.
- interface components 213 may include components configured to send and receive information between components of system 100 , such as between mobile device 110 , transmitters 102 and 106 , and financial service provider system 130 , for example, via network 120 .
- Mobile device 110 may also include antenna 215 .
- Antenna 115 may be any type of known antenna capable of detecting transmitter signals.
- antenna 215 may be any type of commercially available antenna.
- antenna 215 may be an LE antenna.
- antenna 215 may be a BluetoothTM LE antenna.
- antenna 215 may be integrated with receiver 214 and/or with other components of mobile device 110 .
- Mobile device 110 may also include receiver 214 .
- Receiver 214 may be any type of receiver that can receive one or more frequencies of transmitted signals (e.g., from antenna 215 ), and may be configured in hardware, software and/or some combination of hardware and software. Receiver 214 may also convert the received signals into digital data, and send the digital data to other components of mobile device 110 . Receiver 214 may also transmit the identification data using any known transmission method such as, for example, using one or more data packets. In some configurations, receiver 214 may be capable of simultaneously listening for a plurality of differently modulated signals at once. In certain embodiments, receiver 214 may be an LE receiver. In certain embodiments, receiver 214 may be a BluetoothTM LE antenna. In some embodiments, receiver 214 may be integrated with antenna 115 and/or other components of mobile device 110 .
- memory 212 may include software components that, when executed by processor(s) 211 , perform one or more processes consistent with the disclosed embodiments.
- memory 212 may include financial service provider application 216 , which may include software instructions executable by one or more processors, such as processor(s) 211 .
- the software instructions for financial service provider application 216 may provide features relating to receiving identification data (e.g., from receiver 214 ) and/or notification that identification data for an ATM and/or bank branch associated with financial provider system 130 has been received (e.g., from the operating system of mobile device 110 ), optionally confirming identification data is associated with a transmitting device associated with financial service provider system 130 , transmitting a request for the customer's account balance, safe spending limit, or other account data to financial service provider system 130 (e.g., via network 120 ), receiving requested account data from financial service provider system 130 (e.g., via network 120 ), and receiving a push notification for display on mobile device 110 (e.g., from financial service provider system 130 ).
- receiving identification data e.g., from receiver 214
- notification that identification data for an ATM and/or bank branch associated with financial provider system 130 has been received e.g., from the operating system of mobile device 110
- optionally confirming identification data is associated with a transmitting device associated with financial service provider system 130
- financial service provider application 216 may be running (either actively being used by the customer or passively running in the background) when mobile device 110 is on and transmitter signals are received. In some embodiments, financial service provider application 216 may receive the transmitter identification data and check whether the identification data matches identification data for ATMs and/or bank branches associated with financial service provider 130 (e.g., in identification data database 217 ). In some embodiments, financial service provider application 216 may not be running when mobile device 110 is on and transmitter identification signals are received.
- the operating system of mobile device 110 may be configured to receive and check transmitter identification data (translated and/or determined from the identification signals by receiver 214 or detected based on the received identification signals) against identification data database 217 , start financial service provider application 216 when the identification data matches identification information for ATMs and/or bank branches associated with financial service provider system 130 , and transmit the matched identification data or notification that a match has been found to financial service provider application 216 for subsequent processing.
- transmitter identification data may first be processed and matched by the operating system before the identification data (or notification of match identification data) is transmitted to financial service provider application 216 for subsequent processing.
- Financial service provider app 216 may further be configured to transmit a request to financial service provider system 130 for the customer's account data after matched identification data is found (e.g., after received identification data is matched to identification information in identification data database 217 associated with financial service provider system 130 ).
- the request may be an encrypted application programming interface (API) request transmitted via network 120 .
- the request may include one or more of the identifier for mobile device 110 , customer information (e.g., customer name, account number, etc.), identification data, customer notification preferences, and/or the type of request (e.g., requesting account balance information, safe spending limit information, other account information, or any combination thereof).
- the request may also include information such as the location of the customer, location of the ATM/bank branch associated with the transmitter identification data, or other information that may be used by the financial service provider for purposes other than providing account data to the customer.
- the request may include information that allows the financial service provider to better understand the travel habits of its customers.
- One of ordinary skill in the art would understand information desirable to include in a request.
- Customer notification preferences may include information entered by the customer and stored by financial service provider application 216 regarding the customer's preferred method of notification for received account information.
- financial service provider system 130 may be configured to transmit the requested account information as a push notification, a text, an e-mail, or other type of notification that can be received and displayed to the customer via mobile device 110 , and the customer may pre-select the form in which the financial service provider system 130 will transmit the requested information. If the customer does not pre-select a notification method, financial service provider system 130 may be configured to send the notification via a default method (e.g., all notifications would be push notifications unless another method were selected by the customer).
- a default method e.g., all notifications would be push notifications unless another method were selected by the customer.
- notification options may not be available, and financial service provider system may be configured to transmit the notification via one method.
- financial service provider system 130 may transmit the requested account data to financial service provider application 216 , and financial service provider application transmits the information via the method selected by the customer or via a default method.
- financial service provider application transmits the information via the method selected by the customer or via a default method.
- the customer may also be able to set preferences for the type of request transmitted by financial service provider application 216 .
- financial service provider application 216 may be configured to allow the customer to choose what type of information (e.g., account balance information, safe spending limit information, etc.) should be requested when identification data is matched.
- financial service provider application 216 may be configured for a default safe spending limit, or it may be configured to allow the customer to set a safe spending limit amount.
- the default safe spending limit amount may be the account balance minus any pending transactions, and a customer may be able to set the safe spending limit amount may be the account balance minus $1,000.
- One of ordinary skill in the art would understand desirable configurations for the types of request that may be sent by financial service provider application 116 and parameters desirable for a customer to configure.
- FIG. 3 is an exemplary financial service provider system 130 , consistent with disclosed embodiments.
- Financial service provider system 130 may include processor(s) 331 .
- Processor(s) 331 may be one or more known processing devices, such as a microprocessor from the PentiumTM family manufactured by IntelTM or the TurionTM family manufactured by AMDTM.
- Processor(s) 331 may include a single core or multiple core processor system that provides the ability to perform parallel processes simultaneously.
- processor(s) 331 may be a single core processor that is configured with virtual processing technologies known to those skilled in the art.
- processor(s) 331 may use logical processors to simultaneously execute and control multiple processes.
- Processor(s) 331 may implement virtual machine technologies, or other similar known technologies to provide the ability to execute, control, run, manipulate, store, etc. multiple software processes, applications, programs, etc.
- processor(s) 331 may include a multiple-core processor arrangement (e.g., dual or quad core) that is configured to provide parallel processing functionalities to allow financial service provider system 130 to execute multiple processes simultaneously.
- processor arrangement e.g., dual or quad core
- processor arrangements could be implemented that provide for the capabilities disclosed herein.
- Financial service provider system 130 may also include one or more I/O devices that may comprise one or more interfaces for receiving signals or input from input devices and providing signals or output to one or more output devices that allow data to be received and/or transmitted by financial service provider system 130 .
- financial service provider system 130 may include interface components 332 that may include components configured to send and receive information between components of financial service provider system 130 and mobile device 110 , via networks such as network 120 .
- Financial service provider system 130 may include one or more storage devices configured to store information used by processor(s) 331 (or other components) to perform certain functions related to the disclosed embodiments.
- financial service provider system 130 may include a memory 333 that includes instructions to enable processor(s) 331 to execute one or more applications, such as server applications, network communication processes, and any other type of application or software known to be available on computer systems.
- the instructions, application programs, etc. may be stored in an external storage or available from a memory over a network.
- the one or more storage devices may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, nonremovable, or other type of storage device or tangible computer-readable medium.
- financial service provider system 130 includes a memory 333 that includes instructions that, when executed by processor(s) 331 , perform one or more processes consistent with the functionalities disclosed herein. Methods, systems, and articles of manufacture consistent with disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks.
- financial service provider system 130 may include a memory that may include one or more programs to perform one or more functions of interface components 332 .
- processor(s) 331 may execute one or more programs located remotely from financial service provider system 130 .
- financial service provider system 130 may access one or more remote programs, that, when executed, perform functions related to disclosed embodiments.
- Memory 333 may include one or more memory devices that store data and instructions used to perform one or more features of the disclosed embodiments.
- Memory 333 may also include any combination of one or more databases controlled by memory controller devices (e.g., server(s), etc.) or software, such as document management systems, Microsoft SQL databases, SharePoint databases, OracleTM databases, SybaseTM databases, or other relational databases (see, e.g., customer account database 335 , described below).
- Financial service provider system 130 may also be communicatively connected to one or more memory devices locally or through a network.
- the remote memory devices may be configured to store information and may be accessed and/or managed by financial service provider system 130 .
- the remote memory devices may be document management systems, Microsoft SQL database. SharePoint databases, OracleTM databases, SybaseTM databases, or other relational databases. Systems and methods of disclosed embodiments, however, are not limited to separate databases or even to the use of a database.
- Financial service provider system 130 may include customer account database 335 .
- customer account database 335 may be configured to store information about customers' financial accounts such as account balances.
- customer account database 335 may be configured to store information about the customer's preferences, such as the customer's notification preferences.
- memory 333 may include software components that, when executed by processor(s) 331 , perform one or more processes consistent with the disclosed embodiments.
- memory 333 may include request module 334 , which may include software instructions executable by one or more processors, such as processor(s) 331 .
- the software instructions for request module 334 may provide features related to receiving a request for account information (e.g., from financial service provider application 216 via network 120 ), retrieving requested information (e.g., from customer account database 335 ), calculating requested information (e.g., calculating a safe spend limit), and/or transmitting the requested information (e.g., to mobile device 110 via network 120 ).
- Request module 334 may be stored in one or more memory devices remote from financial service provider system 130 and retrieved or executed remotely, with results of the execution being provided to financial service provider system 130 for subsequent processing.
- request module 334 of financial service provider system 130 may provide information responsive to the request from financial service provider application 216 in various formats (e.g., as a push notification, as a text message, as an e-mail, or in any format that can be received and displayed via mobile device 110 ).
- Financial service provider system 130 e.g., request module 334
- Financial service provider system 130 may also be configured to receive information on a customer's preferred notification method and to send account information using the customer's preferred method.
- the customer's preferences may be stored by financial service provider system 130 (e.g., in customer account database 335 ). For example, when the customer first installs financial service provider application 216 on mobile device 110 , the customer may be asked to set his preferences, including notification preferences, and these preferences may be transmitted to financial service provider system 130 and stored (e.g., in customer account database 335 ) for use when a customer is near transmitters 102 or 106 .
- the customer's preferences may be transmitted with the request, and request module 334 may be configured to receive the preferences and generate the response in the appropriate format.
- request module 334 transmits the response to financial service provider application 216
- financial service provider application 216 transmits the response for display on mobile device 110 .
- FIG. 4 is a flowchart of an exemplary process 400 for automatically requesting and receiving account information via a mobile device.
- mobile device 110 may download financial service provider application 216 .
- the customer may access an application store, select financial service provider application 216 , and download financial service provider application 216 onto mobile device 110 .
- the automatic provision of account data as disclosed herein may be one set of functions within several sets of functions provided by financial service provider application 216 .
- the customer may be invited to enter customer information (e.g., customer name, account number, etc.). The customer information, which may be used to link the device to the customer's financial account.
- financial service provider application 216 may be configured to transmit an identifier for mobile device 110 with the customer information to financial service provider system 130 , and the identifier may be linked to and stored with the customer's account information so that future requests from the same device will be automatically associated with the customer's account.
- the customer information may be stored by financial service provider application 216 of mobile device 110 for later transmission with account information requests.
- the customer may be invited to enter customer preferences, such as the customer's preferred type of request and the customer's preferred type of notification.
- customer preferences such as the customer's preferred type of request and the customer's preferred type of notification.
- Information on these preferences may be transmitted to financial service provider system 130 (e.g., stored with the customer's account information in customer account database 335 , so that responses are of the type and via the notification method preferred by the user) and/or may be stored by financial service provider application 216 on mobile device 110 for later transmission with requests.
- antenna 115 may receive or detect the identification signals transmitted by transmitter 102 and/or 106 .
- Receiver 214 may translate the signal into digital data for processing by the operating system of mobile device 110 . In some embodiments, receiver 214 may detect digital data included within the signal.
- the operating system may compare the digital identification data to identification data database 217 (step 403 ). If there is no match (“no” in step 403 ), the process may end. If there is a match (“yes” in step 403 ), the operating system checks if the financial service provider application 216 is already running (step 404 ).
- step 404 the operating starts financial service provider application 216 (step 405 ).
- the operating system may then notify financial service provider application 216 of the match (step 406 ), for example, by transmitting an indication that a match was found or by transmitting the identification data to financial service provider 216 .
- step 406 the operating system may notify financial service provider application 216 of the match.
- financial service provider application 216 may be running in the background and may directly receive the digital identification data from receiver 214 . In such cases, financial service provider application 216 may compare the received identification data to the identification data database 217 to determine if there is a match. In some embodiments, the operating system may receive identification data from receiver 214 , start financial service provider application 216 (if not already running), and transmit the identification data to financial service provider application 216 without first comparing the identification data to the identification data database 217 (wherein financial service provider application 216 would then conduct the comparison).
- One of ordinary skill in the art would understand desirable configurations for determining that the identification data matched identification information associated with financial provider system 130 and beginning the process of requesting account information via financial service provider application 216 .
- financial service provider application 216 may transmit a request for account data to financial service provider system 130 , e.g., via network 120 .
- the request may be an encrypted application programming interface (API) request.
- the request may include one or more of the identifier of mobile device 110 , customer information (e.g., customer name, account number, etc.), identification data, customer notification preferences, and/or the type of request (e.g., a request for account balance information, safe spending limit information, other account information, or any combination thereof).
- the request may include information sufficient for financial service provider system to find the requested account information. For example, if mobile device 110 is already linked to the customer's information at financial service provider system 130 (e.g., in customer account database 335 ) such that any request from mobile device 110 would be associated with the customer's account information, the request may include the identifier of mobile device 110 without additional customer information. In some embodiments, if customer information was stored on mobile device 110 by financial service provider application 216 , one or more pieces of customer information may be transmitted with the request. In some embodiments, the matched identification data is transmitted in the request.
- customer notification preferences may be transmitted with the request, for example, if such preferences had not previously been transmitted to or stored by financial service provider system 130 .
- customer notification preferences may not be transmitted, for example, if only default notifications are available (e.g., the customer cannot select options), if the customer has not yet provided notification preferences, or if financial service provider system 130 transmits the response to financial service provider application 216 and financial service provider application 216 ultimately transmits the notification for display on mobile device 110 .
- information on the type of account data requested is transmitted.
- this information may be transmitted as customer preferences for financial service provider system 130 to process (e.g., a general request for account information is transmitted along with a list of the customer's preferences, and financial service provider system 130 combines the two to obtain the customer's preferred type of information).
- the customer preferences on the type of account data to request is processed by financial service provider application 216 and dictates the type of request sent to financial service provider system 130 (e.g., financial service provider application 216 requests only account balance account information).
- information on the type of account data requested is not transmitted, for example, if the system is configured to transmit default account data or if the customer has not set up preferences for the type of account data to request.
- the request may also include information such as the location of the customer, location of the ATM/bank branch associated with the identification data.
- the request may include other information that may be used by the financial service provider for purposes other than providing account data to the customer.
- the request may include information that allows the financial service provider to better understand the travel habits of its customers.
- One of ordinary skill in the art would understand information desirable to include in a request.
- mobile device 110 may receive the response from financial service provider system 130 , for example, via network 120 and interface components 232 .
- the response may be identical to the account data retrieved by financial service provider system 130 (e.g., the customer's account balance) or it may be derived from the account data retrieved (e.g., the customer's safe spending limit derived from the customer's current account balance).
- the response may be in the form of a push notification, a text message, an e-mail, or any form that may be received by mobile device 110 and displayed for the customer review.
- the form of the notification may be set, for example, by customer preferences that are previously received and stored by financial service provider system 130 , by customer preferences transmitted in the request, or by default settings.
- the response may be in a form that allows notification to be displayed (step 409 ) without being handled by financial service provider application 216 (e.g., text message, e-mail).
- the response may be in a form that can be received by financial service provider application 216 , wherein financial service provider application 216 may translate the response into a notification for step 409 (e.g., a push notification).
- FIG. 5 is a flowchart of exemplary process 500 for receiving a request for account information at a financial service provider system and transmitting a response from a financial service provider system to a mobile device.
- financial service provider system 130 may receive and store information for accessing a customer's account information and on the customer's preferences. For example, financial service provider system 130 may receive an identifier for mobile device 110 that may be linked to and stored with the customer's account information so that future requests from the same device will be automatically associated with the customer's account. As another example, financial service provider system 130 may receive account access information such as the customer's name, account number, password, PIN, an identifier of financial service application 116 , etc., which may be received with or without an identifier for mobile device 110 .
- Financial service provider system 130 may also receive customer preferences for one or more of the type of information requested (e.g., account balance information, safe spending limit information), how to derive requested information (e.g., customer's preferred calculation for safe spending limit), notification format (e.g., push notification, text message, etc.), etc.
- type of information requested e.g., account balance information, safe spending limit information
- how to derive requested information e.g., customer's preferred calculation for safe spending limit
- notification format e.g., push notification, text message, etc.
- the information may be received and stored by financial service provider system 130 before the first request for account information is received from financial service provider application 216 .
- financial service provider application 216 After downloading financial service provider application 216 , the customer may be invited to enter customer preferences, and the information on these preferences may be transmitted to financial service provider system 130 .
- the receipt of the information is optional (e.g., the customer may not be required to transmit information or financial service provider system 130 may not be configured to receive such information in advance of a request).
- financial service provider system 130 receives the request, for example, via network 120 and interface components 332 .
- request module 334 may access the customer's account information, for example, in customer account database 335 (step 503 ).
- request module 334 may determine if a preferred type of information has been specified by retrieving previously stored customer preference information and/or reviewing the preferences transmitted with the request (e.g., decision 504 ).
- decision 504 may be omitted, for example, if financial service provider system 130 is not configured to provide various types of account information and is instead configured to provide default information (e.g., configured to go from step 503 to step 505 ).
- financial service provider system 130 may be configured to obtain the preferred type of account information (e.g., step 506 ), for example, by retrieving the preferred information from customer account database 335 (e.g., account balance information) or by deriving the preferred information from data stored in customer account database 335 (e.g., deriving safe spend information from account balance information).
- customer account database 335 e.g., account balance information
- financial service provider system 130 may be configured to recognize a hierarchy in request preferences. For example, financial service provider system 130 may be configured to first check any information type preferences transmitted with the request and follow those instructions if available, but if those instructions are not available, financial service provider system 130 may then check for any information type preferences stored in customer account database 335 .
- financial service provider system 130 may be configured to obtain the default type of account information (e.g., step 505 ), for example, by retrieving the default information from customer account database 335 (e.g., account balance information) or by deriving the default information from data stored in customer account database 335 (e.g., deriving safe spend information from account balance information).
- customer account database 335 e.g., account balance information
- deriving the default information from data stored in customer account database 335 e.g., deriving safe spend information from account balance information.
- financial service provider system 130 may be configured to determine if a preferred format for the response has been specified by retrieving previously stored customer notification preferences and/or reviewing the notification preferences transmitted with the request (e.g., step 507 ). In certain embodiments, step 507 may be omitted, for example, if financial service provider system 130 is not be configured to provide various formats for the response and is instead be configured to provide a default response (e.g., configured to go from step 505 or 506 directly to step 508 ).
- response format preferences are available (“yes” in step 507 )
- financial service provider system 130 may be configured to format the obtained information into the preferred response format.
- financial service provider system 130 may be configured to recognize a hierarchy in response format preferences. For example, financial service provider system 130 may be configured to first check any format preferences transmitted with the request and follow those instructions if available, but if those instructions are not available, financial service provider system 130 may then check for any format preferences stored in customer account database 335 .
- financial service provider may be configured to format the obtained information in a default format (e.g., step 508 ).
- the default format may be to send the response as a push notification.
- financial service provider application 216 is configured to format the information for display
- financial service provider system 130 may not be configured to format the response for display and may only format it (if any additional formatting is needed) for receipt by financial service provider application 216 .
- financial service provider system may be configured to transmit the response to mobile device 110 (e.g., to financial service provider application 216 ).
- financial service provider system 130 may also be configured to reformat the response in a second format if financial service provider system 130 receives information that there was an error in the transmission or receipt of the response formatted in the first format. For example, if the response was first sent as an e-mail, but financial service provider system 130 receives a notice that the e-mail could not be delivered, or “bounced back,” financial service provider system 130 may be configured to reformat the response as a text message and transmit the text message.
- financial service provider system 130 may be configured to reformat the response as a text message and transmit the text message.
- any financial service provider may employ systems, methods, and articles of manufacture consistent with certain principles related to the disclosed embodiments.
- any merchant may also employ systems, methods, and articles of manufacture consistent with certain disclosed embodiments.
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
- This application claims priority from U.S. Provisional Application No. 61/977,379, filed Apr. 9, 2014, which is hereby incorporated by reference in the present application.
- The disclosed embodiments generally relate providing electronic notifications. In particular, disclosed embodiments may use low energy technology to activate a mobile application to check an account balance.
- An automated teller machine (ATM) is an electronic device that allows banking customers to carry out financial transactions without the need for a human teller. For example, customers may use an ATM to access their bank accounts, deposit, withdraw, or transfer funds, check account balances, or dispense items of value. Generally, to use an ATM, the customer may insert a banking card containing magnetic strip information into the ATM's card reader, and authenticate the card by entering a personal identification number (PIN). After the card has been read and authenticated, the customer can carry out various transactions related to their account. Since the widespread adoption of ATMs, customer use of bank branches has declined. However, customers may still conduct similar activities (and often additional activities) at a bank branch with the assistance of a bank teller.
- The most common activities that customers conduct at ATMs and bank branches are withdrawing funds from a financial account and checking an account balance. Before withdrawing funds, a customer might check his account balance to ensure that the intended withdrawal does not overdraw the account.
- Currently, to obtain balance information, a customer using an ATM must use the check balance function of the ATM, wait for the ATM to transmit the request, and receive the desired information. Similarly, a customer at a bank branch must ask the teller to look up the customers account balance and wait for the teller to request and relay the desired information. Furthermore, there are often substantial waiting lines at both ATMs and bank branches. Moreover, the time needed for customers to check their account balances before withdrawing funds increases the length of each transaction and exacerbates the delay.
- Mobile devices (e.g., smartphones, tablets, etc.) are ubiquitous and these devices equipped with financial provider applications with balance checking functionality offer an alternative way for customers to check their account balances. However, current applications typically require the customer to request his account balance in a process involving unlocking his device, logging into an application, and requesting account information. Furthermore, if there is no line at the ATM or bank teller, or if the customer does not remember to use the application before approaching the ATM or bank teller, it is difficult for the customer to use the check balance functionality while interacting with the ATM or bank teller.
- It is therefore desirable to provide systems and processes that more effectively provides the customer's account balance or other account notifications. It is also desirable for institutions to improve computer system performance by decreasing the time it takes to conduct a transaction by automatically providing account information.
- Disclosed embodiments include methods, systems, and non-transitory computer-readable storage media for enabling a customer to automatically receive account balance or other notifications such as safe spending limit information on a mobile device based on a customer's detected proximity to an ATM, bank teller station, or bank branch equipped with a wireless transmitter. Although other locating technologies, such as geofencing and GPS-based technologies or even user-provided check-ins, may also be used, transmitters can provide more accurate location information than other technologies and is not dependent on manually provided information. For example, one type of transmitter, low energy (LE) transmitters allow for micro-location of a mobile device that is a more precise predictor of a customer's location and presence at an ATM terminal or bank branch teller station. Additionally, LE transmitters may be used in locations where other locating technologies falter, such as inside buildings where GPS or cellular signals may not penetrate.
- In some embodiments, a mobile device for providing account data is provided. The mobile device may comprise a display device, a memory storing instructions, and at least one processor configured to execute the instructions in the memory. The instructions in the memory may include instructions for detecting an identification signal, determining identification data based on the identification signal, and transmitting a request for account data based on the identification data. The instructions may further provide for receiving the requested account data and displaying the requested account data via the display device. In some embodiments the identification signal is transmitted from a low energy transmitter, and in some embodiments, the low energy transmitter is a Bluetooth™ LE transmitter. In some embodiments the requested account data is received as a push notification, a text message, or an e-mail, and in some embodiments, the account data is the account balance or a safe spend limit.
- In some embodiments, a computer-implemented method for providing account data is provided. The method may comprise detecting, by at least one processor, an identification signal and determining, by the at least one processor, identification data based on the identification signal. The method may further comprise transmitting, by the at least one processor, a request for account data based on the identification data and receiving, by the at least one processor, the requested account data. The method may also comprise displaying, by the at least one processor, the requested account data via the display device. In some embodiments, the identification signal is transmitted from a low energy transmitter, and in some embodiments, the low energy transmitter is a Bluetooth™ LE transmitter.
- In some embodiments, a non-transitory computer-readable medium storing instructions for providing account data is provided. In some embodiments, the instructions may be executable by at least one processor, and the instructions may provide for detecting an identification signal, determining identification data based on the identification signal, and transmitting a request for account data based on at least the identification data. The instructions may also provide for receiving the requested account data and displaying the requested account data via the display device. In some embodiments, the identification signal is transmitted from a low energy transmitter, and in some embodiments, the low energy transmitter is a Bluetooth™ LE transmitter.
- 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 disclosed embodiments.
- 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 the disclosed principles. In the drawings:
-
FIG. 1 is an exemplary system that may be used to implement the disclosed embodiments. -
FIG. 2 is an exemplary mobile device configured to provide one or more aspects of the disclosed embodiments. -
FIG. 3 is an exemplary financial service provider system configured to provide one or more aspects of the disclosed embodiments. -
FIG. 4 is a flowchart of an exemplary process for automatically requesting and receiving account information via a mobile device. -
FIG. 5 is a flowchart of exemplary process for receiving a request for account information at a financial service provider system and transmitting a response from a financial service provider system to a mobile device. - Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings and disclosed herein. Wherever convenient, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
-
FIG. 1 is anexemplary system 100 configured to provide one or more aspects of the disclosed embodiments. The components and arrangements shown inFIG. 1 are not intended to be limiting to any disclosed embodiments, as the components used to implement the processes and features disclosed here may vary. - In accordance with certain disclosed embodiments,
system 100 may include one ormore ATMs 101 and one or more bank teller stations or bank branches 105 (hereinafter referred to as “bank branch 105” for ease of reference). ATM 101 andbank branch 105 may be provided by or operated on behalf of a financial service provider that provides financial service provider system 130 (e.g., ATM 101,bank branch 105, and financialservice provider system 130 may be owned and/or operated by the same financial service provider). In certain embodiments, ATM 101 andbank branch 105 are not provided by the same financial service provider that provides financial service provider system, but ATM 101 andbank branch 105 are associated with the financial service provider that provides financialservice provider system 130 such that a customer of the financial service provider is capable of accessing account information and/or conducting transactions via ATM 101 and bank branch 105 (e.g., financial service provider does not ownATM 101 orbank branch 105, but customers of the financial service provider can still access their accounts via ATM 101 and bank branch 105). - ATM 101 may be associated with
transmitter 102 andbank branch 105 may be associated with atransmitter 106. - Each transmitter transmits an identification signal, and by reading the identification signal of the transmitter, the associated
ATM 101 orbank branch 105 can be identified.Transmitter 102 may be located, for example, attached to the housing of the ATM, near the ATM (e.g., affixed to a door leading to the room with the ATM if the ATM is indoors), within the housing of the ATM, integrated into the hardware of the ATM, etc.Transmitter 106 may be located, for example, on the exterior of a bank branch (e.g., on an outside wall near the door of the bank branch, etc.) or within the bank branch (e.g., on an inside wall of the bank branch, at one or more bank teller stations, affixed to one or more bank teller computer terminals, within the housing of a bank teller computer terminal, integrated into the hardware of the bank teller computer terminal, etc.). -
Transmitters transmitters transmitters transmitters - The signal transmitted by
transmitters -
Mobile device 110 is associated with a customer of the financial service provider that provides financialservice provider system 130. The customer may have one or more accounts (e.g., checking or savings accounts) provided by the financial service provider.Mobile device 110 may be any device capable of receiving transmitter signals.Mobile device 110 may include smartphones, tablets, or other mobile devices.Mobile device 110 may use any appropriate operating system, such as iOS, Windows Phone, Android, or BlackBerry operating systems. In some embodiments,mobile device 110 may be capable of receiving Bluetooth™ LE signals, sometimes called Bluetooth SMART™ devices.Mobile device 110 may also be a device with a Bluetooth™ LE integrated circuit.Mobile device 110 may also be any other mobile device (e.g., Google Glass™) capable of receiving transmitter signals. -
Mobile device 110 may be configured to transmit requests for customer account information tofinancial provider system 130, for example, vianetwork 120.Mobile device 110 may also be configured to receive customer account information fromfinancial provider system 130, for example, vianetwork 120. Further details regardingmobile device 110 are provided inFIG. 2 and its description. -
Network 120 may be any type of network that provides communications, exchanges information, and/or facilitates the exchange of information betweenmobile device 110 and financialservice provider system 130. In one embodiment,network 120 may be the Internet, a Local Area Network, 3G telecommunications network, 4G telecommunications network, or other suitable connection(s) that enables bidirectional communication between various components ofsystem 100. - Financial
service provider system 130 may be associated with a financial account provider, such as, for example, a bank, lender, merchant, credit card provider, and any other entity that provides financial accounts to customers. - Financial
service provider system 130 may be configured to receive requests for customer account information frommobile device 110, for example, vianetwork 120. Financialservice provider system 130 may also be configured to transmit customer account information tomobile device 110, for example, vianetwork 120. Further details regarding financialservice provider system 130 are provided with respect toFIG. 3 . -
FIG. 2 is an exemplarymobile device 110, consistent with disclosed embodiments. In one embodiment,mobile device 110 may include one or more processor(s) 211, one or more memory devices, such asmemory 212 andidentification data database 217,interface components 213,receiver 214, and antenna 215. - Processor(s) 211 may be configured to execute instructions to provide processes and functionality as disclosed herein. Processor(s) 211 may be one or more known processing devices, such as a microprocessor from the Pentium™ family manufactured by Intel™ or the Turion™ family manufactured by AMD™. Processor(s) 211 may include a single core or multiple core processor system that provides the ability to perform parallel processes simultaneously. For example, processor(s) 211 may be a single core processor that is configured with virtual processing technologies known to those skilled in the art. In certain embodiments, processor(s) 211 may use logical processors to simultaneously execute and control multiple processes. Processor(s) 211 may implement virtual machine technologies, or other similar known technologies to provide the ability to execute, control, run, manipulate, store, etc. multiple software processes, applications, programs, etc. In another embodiment, processor(s) 211 may include a multiple-core processor arrangement (e.g., dual or quad core) that is configured to provide parallel processing functionalities to allow
mobile device 110 to execute multiple processes simultaneously. One of ordinary skill in the art would understand that other types of processor arrangements could be implemented that provide for the capabilities disclosed herein. -
Mobile device 110 may include one or more storage devices configured to store information used by processor(s) 211 (or other components) to perform certain functions related to the disclosed embodiments. In one example,mobile device 110 may includememory 212 that includes instructions to enable processor(s) 211 to execute one or more processes, such as mobile applications, network communication processes, and any other type of application or software known to be available on mobile device systems. In some embodiments, the instructions, mobile application programs, etc. may be stored in an external storage or available from a memory over a network (e.g., network 120). The one or more storage devices may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, nonremovable, or other type of storage device or tangible computer-readable medium. - In one embodiment,
memory 212 may store instructions that, when executed by processor(s) 211, causemobile device 110 to perform one or more processes consistent with the functionalities disclosed herein. Methods, systems, and articles of manufacture consistent with disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example,mobile device 110 may include a memory that may include one or more programs to perform one or more functions ofinterface components 213 andreceiver 214. Moreover, processor(s) 211 may execute one or more programs located remotely frommobile device 110. For example,mobile device 110 may access one or more remote programs, that, when executed, perform functions related to disclosed embodiments.Memory 212 may include or be associated with one or more memory devices that store data and instructions used to perform one or more features of the disclosed embodiments, andmemory 212 may also include any combination of one or more databases controlled by memory controller devices (e.g., server(s), etc.) or software, such as document management systems, Microsoft SQL databases, SharePoint databases, Oracle™ databases, Sybase™ databases, or other relational databases (see, e.g.,identification data database 217, described below).Mobile device 110 may also be communicatively connected to one or more memory devices (e.g., other databases not shown) locally or through a network. The remote memory devices may be configured to store information and may be accessed and/or managed bymobile device 110. By way of example, the remote memory devices may be document management systems, Microsoft SQL databases, SharePoint databases, Oracle™ databases, Sybase™ databases, or other relational databases. Systems and methods of disclosed embodiments, however, are not limited to separate databases or even to the use of a database. -
Mobile device 110 may includeidentification data database 217, which may include identification information for identifying transmitters associated with ATMs and/or bank branches associated with financialservice provider system 130. For example,identification data database 217 may include one or more tables that link each unique identification information to its respective transmitter, the location (e.g., address) of the transmitter, and the ATM or bank branch with which it is associated.Identification data database 217 may be controlled by a memory controller device or software, such as document management systems, Microsoft SQL databases, SharePoint databases, Oracle™ databases, Sybase™ databases, or other relational databases. In some embodiments,identification data database 217 may be a remote memory device that may be accessed and/or managed bymobile device 110. -
Mobile device 110 may also include one or more I/O devices that may comprise one or more interfaces for receiving signals or input from input devices and providing signals or output to one or more output devices that allow data to be received and/or transmitted bymobile device 110. For example,mobile device 110 may includeinterface components 213 that may provide interfaces to one or more input devices such as one or more display screens, on-screen keyboards, fingerprint recognition devices, and the like, that enablemobile device 110 to receive data from the customer and provide notifications to the customer. Further,interface components 213 may include components configured to send and receive information between components ofsystem 100, such as betweenmobile device 110,transmitters service provider system 130, for example, vianetwork 120. -
Mobile device 110 may also include antenna 215.Antenna 115 may be any type of known antenna capable of detecting transmitter signals. For example, antenna 215 may be any type of commercially available antenna. In certain embodiments, antenna 215 may be an LE antenna. In certain embodiments, antenna 215 may be a Bluetooth™ LE antenna. In some embodiments, antenna 215 may be integrated withreceiver 214 and/or with other components ofmobile device 110. -
Mobile device 110 may also includereceiver 214.Receiver 214 may be any type of receiver that can receive one or more frequencies of transmitted signals (e.g., from antenna 215), and may be configured in hardware, software and/or some combination of hardware and software.Receiver 214 may also convert the received signals into digital data, and send the digital data to other components ofmobile device 110.Receiver 214 may also transmit the identification data using any known transmission method such as, for example, using one or more data packets. In some configurations,receiver 214 may be capable of simultaneously listening for a plurality of differently modulated signals at once. In certain embodiments,receiver 214 may be an LE receiver. In certain embodiments,receiver 214 may be a Bluetooth™ LE antenna. In some embodiments,receiver 214 may be integrated withantenna 115 and/or other components ofmobile device 110. - In certain embodiments,
memory 212 may include software components that, when executed by processor(s) 211, perform one or more processes consistent with the disclosed embodiments. For example,memory 212 may include financialservice provider application 216, which may include software instructions executable by one or more processors, such as processor(s) 211. When executed, the software instructions for financialservice provider application 216 may provide features relating to receiving identification data (e.g., from receiver 214) and/or notification that identification data for an ATM and/or bank branch associated withfinancial provider system 130 has been received (e.g., from the operating system of mobile device 110), optionally confirming identification data is associated with a transmitting device associated with financialservice provider system 130, transmitting a request for the customer's account balance, safe spending limit, or other account data to financial service provider system 130 (e.g., via network 120), receiving requested account data from financial service provider system 130 (e.g., via network 120), and receiving a push notification for display on mobile device 110 (e.g., from financial service provider system 130). - In some embodiments, financial
service provider application 216 may be running (either actively being used by the customer or passively running in the background) whenmobile device 110 is on and transmitter signals are received. In some embodiments, financialservice provider application 216 may receive the transmitter identification data and check whether the identification data matches identification data for ATMs and/or bank branches associated with financial service provider 130 (e.g., in identification data database 217). In some embodiments, financialservice provider application 216 may not be running whenmobile device 110 is on and transmitter identification signals are received. In such cases, the operating system ofmobile device 110 may be configured to receive and check transmitter identification data (translated and/or determined from the identification signals byreceiver 214 or detected based on the received identification signals) againstidentification data database 217, start financialservice provider application 216 when the identification data matches identification information for ATMs and/or bank branches associated with financialservice provider system 130, and transmit the matched identification data or notification that a match has been found to financialservice provider application 216 for subsequent processing. In some embodiments, even when financialservice provider application 216 is running, transmitter identification data may first be processed and matched by the operating system before the identification data (or notification of match identification data) is transmitted to financialservice provider application 216 for subsequent processing. - Financial
service provider app 216 may further be configured to transmit a request to financialservice provider system 130 for the customer's account data after matched identification data is found (e.g., after received identification data is matched to identification information inidentification data database 217 associated with financial service provider system 130). The request may be an encrypted application programming interface (API) request transmitted vianetwork 120. The request may include one or more of the identifier formobile device 110, customer information (e.g., customer name, account number, etc.), identification data, customer notification preferences, and/or the type of request (e.g., requesting account balance information, safe spending limit information, other account information, or any combination thereof). The request may also include information such as the location of the customer, location of the ATM/bank branch associated with the transmitter identification data, or other information that may be used by the financial service provider for purposes other than providing account data to the customer. For example, the request may include information that allows the financial service provider to better understand the travel habits of its customers. One of ordinary skill in the art would understand information desirable to include in a request. - Customer notification preferences may include information entered by the customer and stored by financial
service provider application 216 regarding the customer's preferred method of notification for received account information. For example, financialservice provider system 130 may be configured to transmit the requested account information as a push notification, a text, an e-mail, or other type of notification that can be received and displayed to the customer viamobile device 110, and the customer may pre-select the form in which the financialservice provider system 130 will transmit the requested information. If the customer does not pre-select a notification method, financialservice provider system 130 may be configured to send the notification via a default method (e.g., all notifications would be push notifications unless another method were selected by the customer). In certain embodiments, notification options may not be available, and financial service provider system may be configured to transmit the notification via one method. In certain embodiments, financialservice provider system 130 may transmit the requested account data to financialservice provider application 216, and financial service provider application transmits the information via the method selected by the customer or via a default method. One of ordinary skill in the art would understand desirable configurations for the notification for account information and parameters desirable for a customer to configure. - The customer may also be able to set preferences for the type of request transmitted by financial
service provider application 216. For example, financialservice provider application 216 may be configured to allow the customer to choose what type of information (e.g., account balance information, safe spending limit information, etc.) should be requested when identification data is matched. For a request for the safe spending limit, financialservice provider application 216 may be configured for a default safe spending limit, or it may be configured to allow the customer to set a safe spending limit amount. For example, the default safe spending limit amount may be the account balance minus any pending transactions, and a customer may be able to set the safe spending limit amount may be the account balance minus $1,000. One of ordinary skill in the art would understand desirable configurations for the types of request that may be sent by financial service provider application 116 and parameters desirable for a customer to configure. -
FIG. 3 is an exemplary financialservice provider system 130, consistent with disclosed embodiments. Financialservice provider system 130 may include processor(s) 331. Processor(s) 331 may be one or more known processing devices, such as a microprocessor from the Pentium™ family manufactured by Intel™ or the Turion™ family manufactured by AMD™. Processor(s) 331 may include a single core or multiple core processor system that provides the ability to perform parallel processes simultaneously. For example, processor(s) 331 may be a single core processor that is configured with virtual processing technologies known to those skilled in the art. In certain embodiments, processor(s) 331 may use logical processors to simultaneously execute and control multiple processes. Processor(s) 331 may implement virtual machine technologies, or other similar known technologies to provide the ability to execute, control, run, manipulate, store, etc. multiple software processes, applications, programs, etc. In another embodiment, processor(s) 331 may include a multiple-core processor arrangement (e.g., dual or quad core) that is configured to provide parallel processing functionalities to allow financialservice provider system 130 to execute multiple processes simultaneously. One of ordinary skill in the art would understand that other types of processor arrangements could be implemented that provide for the capabilities disclosed herein. - Financial
service provider system 130 may also include one or more I/O devices that may comprise one or more interfaces for receiving signals or input from input devices and providing signals or output to one or more output devices that allow data to be received and/or transmitted by financialservice provider system 130. For example, financialservice provider system 130 may includeinterface components 332 that may include components configured to send and receive information between components of financialservice provider system 130 andmobile device 110, via networks such asnetwork 120. - Financial
service provider system 130 may include one or more storage devices configured to store information used by processor(s) 331 (or other components) to perform certain functions related to the disclosed embodiments. In one example, financialservice provider system 130 may include amemory 333 that includes instructions to enable processor(s) 331 to execute one or more applications, such as server applications, network communication processes, and any other type of application or software known to be available on computer systems. In some embodiments, the instructions, application programs, etc. may be stored in an external storage or available from a memory over a network. The one or more storage devices may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, nonremovable, or other type of storage device or tangible computer-readable medium. - In one embodiment, financial
service provider system 130 includes amemory 333 that includes instructions that, when executed by processor(s) 331, perform one or more processes consistent with the functionalities disclosed herein. Methods, systems, and articles of manufacture consistent with disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example, financialservice provider system 130 may include a memory that may include one or more programs to perform one or more functions ofinterface components 332. Moreover, processor(s) 331 may execute one or more programs located remotely from financialservice provider system 130. For example, financialservice provider system 130 may access one or more remote programs, that, when executed, perform functions related to disclosed embodiments.Memory 333 may include one or more memory devices that store data and instructions used to perform one or more features of the disclosed embodiments.Memory 333 may also include any combination of one or more databases controlled by memory controller devices (e.g., server(s), etc.) or software, such as document management systems, Microsoft SQL databases, SharePoint databases, Oracle™ databases, Sybase™ databases, or other relational databases (see, e.g.,customer account database 335, described below). Financialservice provider system 130 may also be communicatively connected to one or more memory devices locally or through a network. The remote memory devices may be configured to store information and may be accessed and/or managed by financialservice provider system 130. By way of example, the remote memory devices may be document management systems, Microsoft SQL database. SharePoint databases, Oracle™ databases, Sybase™ databases, or other relational databases. Systems and methods of disclosed embodiments, however, are not limited to separate databases or even to the use of a database. - Financial
service provider system 130 may includecustomer account database 335. In certain embodiments,customer account database 335 may be configured to store information about customers' financial accounts such as account balances. In some embodiments,customer account database 335 may be configured to store information about the customer's preferences, such as the customer's notification preferences. - In certain embodiments,
memory 333 may include software components that, when executed by processor(s) 331, perform one or more processes consistent with the disclosed embodiments. For example,memory 333 may includerequest module 334, which may include software instructions executable by one or more processors, such as processor(s) 331. When executed, the software instructions forrequest module 334 may provide features related to receiving a request for account information (e.g., from financialservice provider application 216 via network 120), retrieving requested information (e.g., from customer account database 335), calculating requested information (e.g., calculating a safe spend limit), and/or transmitting the requested information (e.g., tomobile device 110 via network 120).Request module 334 may be stored in one or more memory devices remote from financialservice provider system 130 and retrieved or executed remotely, with results of the execution being provided to financialservice provider system 130 for subsequent processing. - As noted above,
request module 334 of financialservice provider system 130 may provide information responsive to the request from financialservice provider application 216 in various formats (e.g., as a push notification, as a text message, as an e-mail, or in any format that can be received and displayed via mobile device 110). Financial service provider system 130 (e.g., request module 334) may be configured to provide the information via one or more default methods (e.g., send all responses via text message, or attempt to send information as a text message first, then follow with an e-mail if the text message is undeliverable). Financialservice provider system 130 may also be configured to receive information on a customer's preferred notification method and to send account information using the customer's preferred method. In some embodiments, the customer's preferences may be stored by financial service provider system 130 (e.g., in customer account database 335). For example, when the customer first installs financialservice provider application 216 onmobile device 110, the customer may be asked to set his preferences, including notification preferences, and these preferences may be transmitted to financialservice provider system 130 and stored (e.g., in customer account database 335) for use when a customer is neartransmitters request module 334 may be configured to receive the preferences and generate the response in the appropriate format. In some embodiments,request module 334 transmits the response to financialservice provider application 216, and financialservice provider application 216 transmits the response for display onmobile device 110. -
FIG. 4 is a flowchart of anexemplary process 400 for automatically requesting and receiving account information via a mobile device. - At
step 401,mobile device 110 may download financialservice provider application 216. For example, the customer may access an application store, select financialservice provider application 216, and download financialservice provider application 216 ontomobile device 110. As would be readily apparent to one of ordinary skill in the art, the automatic provision of account data as disclosed herein may be one set of functions within several sets of functions provided by financialservice provider application 216. Upon downloading financialservice provider application 216 or before the first automatic request for account information, the customer may be invited to enter customer information (e.g., customer name, account number, etc.). The customer information, which may be used to link the device to the customer's financial account. For example, upon receipt of the customer's information, financialservice provider application 216 may be configured to transmit an identifier formobile device 110 with the customer information to financialservice provider system 130, and the identifier may be linked to and stored with the customer's account information so that future requests from the same device will be automatically associated with the customer's account. In some embodiments, the customer information may be stored by financialservice provider application 216 ofmobile device 110 for later transmission with account information requests. - After downloading financial
service provider application 216 or before the first automatic request for account information, the customer may be invited to enter customer preferences, such as the customer's preferred type of request and the customer's preferred type of notification. Information on these preferences may be transmitted to financial service provider system 130 (e.g., stored with the customer's account information incustomer account database 335, so that responses are of the type and via the notification method preferred by the user) and/or may be stored by financialservice provider application 216 onmobile device 110 for later transmission with requests. - When
mobile device 110 comes in close enough proximity toATM 101 and/orbank branch 105 withtransmitters 102 and/or 106, respectively,antenna 115 may receive or detect the identification signals transmitted bytransmitter 102 and/or 106.Receiver 214 may translate the signal into digital data for processing by the operating system ofmobile device 110. In some embodiments,receiver 214 may detect digital data included within the signal. After receiving the identification data from receiver 214 (step 402), the operating system may compare the digital identification data to identification data database 217 (step 403). If there is no match (“no” in step 403), the process may end. If there is a match (“yes” in step 403), the operating system checks if the financialservice provider application 216 is already running (step 404). If financialservice provider application 216 is not already running (“no” in step 404), the operating starts financial service provider application 216 (step 405). The operating system may then notify financialservice provider application 216 of the match (step 406), for example, by transmitting an indication that a match was found or by transmitting the identification data tofinancial service provider 216. If financialservice provider application 216 is already running (“yes” in step 404),process 400 may proceed to step 406, where the operating system may notify financialservice provider application 216 of the match. - As discussed above with respect to
FIG. 2 , in some embodiments, financialservice provider application 216 may be running in the background and may directly receive the digital identification data fromreceiver 214. In such cases, financialservice provider application 216 may compare the received identification data to theidentification data database 217 to determine if there is a match. In some embodiments, the operating system may receive identification data fromreceiver 214, start financial service provider application 216 (if not already running), and transmit the identification data to financialservice provider application 216 without first comparing the identification data to the identification data database 217 (wherein financialservice provider application 216 would then conduct the comparison). One of ordinary skill in the art would understand desirable configurations for determining that the identification data matched identification information associated withfinancial provider system 130 and beginning the process of requesting account information via financialservice provider application 216. - At
step 407, financialservice provider application 216 may transmit a request for account data to financialservice provider system 130, e.g., vianetwork 120. The request may be an encrypted application programming interface (API) request. The request may include one or more of the identifier ofmobile device 110, customer information (e.g., customer name, account number, etc.), identification data, customer notification preferences, and/or the type of request (e.g., a request for account balance information, safe spending limit information, other account information, or any combination thereof). - The request may include information sufficient for financial service provider system to find the requested account information. For example, if
mobile device 110 is already linked to the customer's information at financial service provider system 130 (e.g., in customer account database 335) such that any request frommobile device 110 would be associated with the customer's account information, the request may include the identifier ofmobile device 110 without additional customer information. In some embodiments, if customer information was stored onmobile device 110 by financialservice provider application 216, one or more pieces of customer information may be transmitted with the request. In some embodiments, the matched identification data is transmitted in the request. - In some embodiments, customer notification preferences may be transmitted with the request, for example, if such preferences had not previously been transmitted to or stored by financial
service provider system 130. In some embodiments, customer notification preferences may not be transmitted, for example, if only default notifications are available (e.g., the customer cannot select options), if the customer has not yet provided notification preferences, or if financialservice provider system 130 transmits the response to financialservice provider application 216 and financialservice provider application 216 ultimately transmits the notification for display onmobile device 110. - In some embodiments, information on the type of account data requested is transmitted. In some embodiments, this information may be transmitted as customer preferences for financial
service provider system 130 to process (e.g., a general request for account information is transmitted along with a list of the customer's preferences, and financialservice provider system 130 combines the two to obtain the customer's preferred type of information). In some embodiments, the customer preferences on the type of account data to request is processed by financialservice provider application 216 and dictates the type of request sent to financial service provider system 130 (e.g., financialservice provider application 216 requests only account balance account information). In some embodiments, information on the type of account data requested is not transmitted, for example, if the system is configured to transmit default account data or if the customer has not set up preferences for the type of account data to request. - The request may also include information such as the location of the customer, location of the ATM/bank branch associated with the identification data. The request may include other information that may be used by the financial service provider for purposes other than providing account data to the customer. For example, the request may include information that allows the financial service provider to better understand the travel habits of its customers. One of ordinary skill in the art would understand information desirable to include in a request.
- At
step 408,mobile device 110 may receive the response from financialservice provider system 130, for example, vianetwork 120 and interface components 232. The response may be identical to the account data retrieved by financial service provider system 130 (e.g., the customer's account balance) or it may be derived from the account data retrieved (e.g., the customer's safe spending limit derived from the customer's current account balance). The response may be in the form of a push notification, a text message, an e-mail, or any form that may be received bymobile device 110 and displayed for the customer review. The form of the notification may be set, for example, by customer preferences that are previously received and stored by financialservice provider system 130, by customer preferences transmitted in the request, or by default settings. The response may be in a form that allows notification to be displayed (step 409) without being handled by financial service provider application 216 (e.g., text message, e-mail). The response may be in a form that can be received by financialservice provider application 216, wherein financialservice provider application 216 may translate the response into a notification for step 409 (e.g., a push notification). -
FIG. 5 is a flowchart ofexemplary process 500 for receiving a request for account information at a financial service provider system and transmitting a response from a financial service provider system to a mobile device. - At
step 501, financialservice provider system 130 may receive and store information for accessing a customer's account information and on the customer's preferences. For example, financialservice provider system 130 may receive an identifier formobile device 110 that may be linked to and stored with the customer's account information so that future requests from the same device will be automatically associated with the customer's account. As another example, financialservice provider system 130 may receive account access information such as the customer's name, account number, password, PIN, an identifier of financial service application 116, etc., which may be received with or without an identifier formobile device 110. Financialservice provider system 130 may also receive customer preferences for one or more of the type of information requested (e.g., account balance information, safe spending limit information), how to derive requested information (e.g., customer's preferred calculation for safe spending limit), notification format (e.g., push notification, text message, etc.), etc. - The information may be received and stored by financial
service provider system 130 before the first request for account information is received from financialservice provider application 216. For example, after downloading financialservice provider application 216, the customer may be invited to enter customer preferences, and the information on these preferences may be transmitted to financialservice provider system 130. In certain embodiments, the receipt of the information is optional (e.g., the customer may not be required to transmit information or financialservice provider system 130 may not be configured to receive such information in advance of a request). - At
step 502, financial service provider system 130 (e.g., request module 334) receives the request, for example, vianetwork 120 andinterface components 332. Based on the information provided in the request (e.g., the identifier formobile device 110 and/or customer information),request module 334 may access the customer's account information, for example, in customer account database 335 (step 503). In certain embodiments,request module 334 may determine if a preferred type of information has been specified by retrieving previously stored customer preference information and/or reviewing the preferences transmitted with the request (e.g., decision 504). In certain embodiments,decision 504 may be omitted, for example, if financialservice provider system 130 is not configured to provide various types of account information and is instead configured to provide default information (e.g., configured to go fromstep 503 to step 505). Atdecision 504, if request preferences are available (“yes” in step 504), financialservice provider system 130 may be configured to obtain the preferred type of account information (e.g., step 506), for example, by retrieving the preferred information from customer account database 335 (e.g., account balance information) or by deriving the preferred information from data stored in customer account database 335 (e.g., deriving safe spend information from account balance information). In certain embodiments, financialservice provider system 130 may be configured to recognize a hierarchy in request preferences. For example, financialservice provider system 130 may be configured to first check any information type preferences transmitted with the request and follow those instructions if available, but if those instructions are not available, financialservice provider system 130 may then check for any information type preferences stored incustomer account database 335. - If request preferences are not available (“no” in step 504), financial
service provider system 130 may be configured to obtain the default type of account information (e.g., step 505), for example, by retrieving the default information from customer account database 335 (e.g., account balance information) or by deriving the default information from data stored in customer account database 335 (e.g., deriving safe spend information from account balance information). - After obtaining the account information, financial
service provider system 130 may be configured to determine if a preferred format for the response has been specified by retrieving previously stored customer notification preferences and/or reviewing the notification preferences transmitted with the request (e.g., step 507). In certain embodiments,step 507 may be omitted, for example, if financialservice provider system 130 is not be configured to provide various formats for the response and is instead be configured to provide a default response (e.g., configured to go fromstep step 509, if response format preferences are available (“yes” in step 507), financialservice provider system 130 may be configured to format the obtained information into the preferred response format. In certain embodiments, financialservice provider system 130 may be configured to recognize a hierarchy in response format preferences. For example, financialservice provider system 130 may be configured to first check any format preferences transmitted with the request and follow those instructions if available, but if those instructions are not available, financialservice provider system 130 may then check for any format preferences stored incustomer account database 335. - If response format preferences are not available (“no” in step 507), financial service provider may be configured to format the obtained information in a default format (e.g., step 508). For example, the default format may be to send the response as a push notification. As another example, if financial
service provider application 216 is configured to format the information for display, financialservice provider system 130 may not be configured to format the response for display and may only format it (if any additional formatting is needed) for receipt by financialservice provider application 216. - At
step 510, financial service provider system may be configured to transmit the response to mobile device 110 (e.g., to financial service provider application 216). In certain embodiments, financialservice provider system 130 may also be configured to reformat the response in a second format if financialservice provider system 130 receives information that there was an error in the transmission or receipt of the response formatted in the first format. For example, if the response was first sent as an e-mail, but financialservice provider system 130 receives a notice that the e-mail could not be delivered, or “bounced back,” financialservice provider system 130 may be configured to reformat the response as a text message and transmit the text message. One of ordinary skill in the art would understand advantageous configurations for the transmission and re-transmission of responses. - Other features and functionalities of the described embodiments are possible. For example, the processes shown in
FIGS. 4 and 5 and described above are not limited to the sequences described above. Variations of these sequences, such as the removal and/or the addition of other process steps may be implemented without departing from the spirit and scope of the disclosed embodiments. - Additionally, any financial service provider may employ systems, methods, and articles of manufacture consistent with certain principles related to the disclosed embodiments. In addition, any merchant may also employ systems, methods, and articles of manufacture consistent with certain disclosed embodiments.
- Furthermore, although aspects of the disclosed embodiments are described as being associated with data stored in memory and other tangible computer-readable storage mediums, one skilled in the art will appreciate that these aspects can also be stored on and executed from many types of tangible computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or CD-ROM, or other forms of RAM or ROM. Accordingly, the disclosed embodiments are not limited to the above described examples, but instead are defined by the appended claims in light of their full scope of equivalents.
Claims (20)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/682,053 US10387865B2 (en) | 2014-04-09 | 2015-04-08 | Systems and computer-implemented processes for providing electronic notifications |
US15/948,087 US10311422B2 (en) | 2014-04-09 | 2018-04-09 | Systems and computer-implemented processes for providing electronic notifications |
US16/460,678 US11023877B2 (en) | 2014-04-09 | 2019-07-02 | Systems and computer-implemented processes for providing electronic notifications |
US17/335,159 US11915223B2 (en) | 2014-04-09 | 2021-06-01 | Systems and computer-implemented processes for providing electronic notifications |
US18/583,814 US20240193575A1 (en) | 2014-04-09 | 2024-02-21 | Systems and computer-implemented processes for providing electronic notifications |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201461977379P | 2014-04-09 | 2014-04-09 | |
US14/682,053 US10387865B2 (en) | 2014-04-09 | 2015-04-08 | Systems and computer-implemented processes for providing electronic notifications |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/948,087 Continuation US10311422B2 (en) | 2014-04-09 | 2018-04-09 | Systems and computer-implemented processes for providing electronic notifications |
US16/460,678 Continuation US11023877B2 (en) | 2014-04-09 | 2019-07-02 | Systems and computer-implemented processes for providing electronic notifications |
Publications (2)
Publication Number | Publication Date |
---|---|
US20150294296A1 true US20150294296A1 (en) | 2015-10-15 |
US10387865B2 US10387865B2 (en) | 2019-08-20 |
Family
ID=54265397
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/682,053 Active 2036-07-24 US10387865B2 (en) | 2014-04-09 | 2015-04-08 | Systems and computer-implemented processes for providing electronic notifications |
US15/948,087 Active US10311422B2 (en) | 2014-04-09 | 2018-04-09 | Systems and computer-implemented processes for providing electronic notifications |
US16/460,678 Active US11023877B2 (en) | 2014-04-09 | 2019-07-02 | Systems and computer-implemented processes for providing electronic notifications |
US17/335,159 Active 2035-10-11 US11915223B2 (en) | 2014-04-09 | 2021-06-01 | Systems and computer-implemented processes for providing electronic notifications |
US18/583,814 Pending US20240193575A1 (en) | 2014-04-09 | 2024-02-21 | Systems and computer-implemented processes for providing electronic notifications |
Family Applications After (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/948,087 Active US10311422B2 (en) | 2014-04-09 | 2018-04-09 | Systems and computer-implemented processes for providing electronic notifications |
US16/460,678 Active US11023877B2 (en) | 2014-04-09 | 2019-07-02 | Systems and computer-implemented processes for providing electronic notifications |
US17/335,159 Active 2035-10-11 US11915223B2 (en) | 2014-04-09 | 2021-06-01 | Systems and computer-implemented processes for providing electronic notifications |
US18/583,814 Pending US20240193575A1 (en) | 2014-04-09 | 2024-02-21 | Systems and computer-implemented processes for providing electronic notifications |
Country Status (4)
Country | Link |
---|---|
US (5) | US10387865B2 (en) |
EP (1) | EP3129965A4 (en) |
CA (1) | CA2945171C (en) |
WO (1) | WO2015157460A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10311422B2 (en) | 2014-04-09 | 2019-06-04 | Capital One Services, Llc | Systems and computer-implemented processes for providing electronic notifications |
US10467842B2 (en) | 2017-03-17 | 2019-11-05 | Bank Of America Corporation | Portable item transfer container |
US20190347643A1 (en) * | 2018-05-11 | 2019-11-14 | Mastercard International Incorporated | Method and system for contactless withdrawal from an atm |
US20200005262A1 (en) * | 2018-06-27 | 2020-01-02 | Bank Of America Corporation | Frictionless Automated Teller Machine |
US20200005261A1 (en) * | 2018-06-27 | 2020-01-02 | Bank Of America Corporation | Frictionless Automated Teller Machine |
US20200005263A1 (en) * | 2018-06-27 | 2020-01-02 | Bank Of America Corporation | Frictionless Automated Teller Machine |
US11026043B1 (en) | 2014-11-07 | 2021-06-01 | Wells Fargo Bank, N.A. | Multi-channel geo-fencing systems and methods |
US20210319416A1 (en) * | 2020-04-10 | 2021-10-14 | Ncr Corporation | Wireless Device for Retrofitting ATMs |
US11354631B1 (en) * | 2016-04-01 | 2022-06-07 | Wells Fargo Bank, N.A. | Systems and methods for remote atm access |
US11432103B1 (en) | 2014-11-07 | 2022-08-30 | Wells Fargo Bank, N.A. | Real-time custom interfaces through multi-channel geo-fencing |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11037114B2 (en) | 2018-03-22 | 2021-06-15 | Diebold Nixdorf, Incorporated | System and method for financial transactions |
US11308476B1 (en) | 2018-12-28 | 2022-04-19 | United Services Automobile Association (Usaa) | Proximity peer to peer mobile navigation system and method |
US11416850B1 (en) * | 2018-12-28 | 2022-08-16 | United Services Automobile Association (Usaa) | Peer to peer navigation system and method |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020112014A1 (en) * | 2000-08-15 | 2002-08-15 | Simon Bennett | Method and apparatus for a network independent short message delivery system |
US20040204078A1 (en) * | 2002-09-30 | 2004-10-14 | Ncr Corporation | Self-service system and method of loading an executable transaction application program from a self-service terminal to a portable electronic device |
US7374079B2 (en) * | 2003-06-24 | 2008-05-20 | Lg Telecom, Ltd. | Method for providing banking services by use of mobile communication system |
US7920849B2 (en) * | 2007-07-13 | 2011-04-05 | Pop Adrian | Method and system for providing advertisements/messages based on wireless data communication technology |
US8548912B2 (en) * | 2010-04-02 | 2013-10-01 | Bank Of America Corporation | Transaction pre-processing with mobile device for a currency dispensing device |
US20130297422A1 (en) * | 2012-04-24 | 2013-11-07 | Qualcomm Incorporated | Retail proximity marketing |
US8598810B2 (en) * | 2011-05-05 | 2013-12-03 | Excelliance Mos Corporation | Constant current driving circuit of light emitting diode and lighting apparatus |
US8646060B1 (en) * | 2013-07-30 | 2014-02-04 | Mourad Ben Ayed | Method for adaptive authentication using a mobile device |
US8751316B1 (en) * | 2010-02-05 | 2014-06-10 | Intuit Inc. | Customer-controlled point-of-sale on a mobile device |
US20140278994A1 (en) * | 2013-03-14 | 2014-09-18 | Richard J. Greenwood | Interactive Mobile Engagement Recharging Terminal System and Device |
US20150120541A1 (en) * | 2013-10-25 | 2015-04-30 | Bank Of America Corporation | Contribution Destination Identification and Processing |
US20150186872A1 (en) * | 2014-01-01 | 2015-07-02 | Bank Of America Corporation | Temporary virtual card |
US20150213405A1 (en) * | 2014-01-30 | 2015-07-30 | Xerox Corporation | Methods and systems for facilitating document transactions |
US9356687B2 (en) * | 2012-12-03 | 2016-05-31 | Samsung Electronics Co., Ltd. | Information providing method and mobile terminal therefor |
US9386416B1 (en) * | 2014-01-29 | 2016-07-05 | Microstrategy Incorporated | Mobile customer presence detection |
Family Cites Families (122)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6064990A (en) * | 1998-03-31 | 2000-05-16 | International Business Machines Corporation | System for electronic notification of account activity |
US8955743B1 (en) * | 1998-04-17 | 2015-02-17 | Diebold Self-Service Systems Division Of Diebold, Incorporated | Automated banking machine with remote user assistance |
US8032453B2 (en) * | 2000-04-14 | 2011-10-04 | Citicorp Development Center, Inc. | Method and system for notifying customers of transaction opportunities |
US6732101B1 (en) * | 2000-06-15 | 2004-05-04 | Zix Corporation | Secure message forwarding system detecting user's preferences including security preferences |
US7000001B2 (en) * | 2000-09-12 | 2006-02-14 | Research In Motion Limited | Bookmark beacon system and method |
EP1382022A2 (en) * | 2001-01-20 | 2004-01-21 | Ncr International Inc. | Self-service terminal |
US8738024B1 (en) * | 2008-03-29 | 2014-05-27 | Nexrf, Corp. | Delivering content within a boundary with beacons |
GB0106681D0 (en) * | 2001-03-19 | 2001-05-09 | Philips Electronics Uk Ltd | Arrangement comprising beacon device and portable device |
US7283846B2 (en) * | 2002-02-07 | 2007-10-16 | Sap Aktiengesellschaft | Integrating geographical contextual information into mobile enterprise applications |
US6959285B2 (en) * | 2002-02-28 | 2005-10-25 | Palmsource, Inc. | Method and a system for computer software distribution using networked software dispensing vending machines |
US9355530B1 (en) * | 2002-03-18 | 2016-05-31 | Diebold Self-Service Systems Division Of Diebold, Incorporated | Processing automated banking transactions requiring approval |
US20040019564A1 (en) * | 2002-07-26 | 2004-01-29 | Scott Goldthwaite | System and method for payment transaction authentication |
US20040127256A1 (en) * | 2002-07-30 | 2004-07-01 | Scott Goldthwaite | Mobile device equipped with a contactless smart card reader/writer |
GB2396472A (en) * | 2002-12-18 | 2004-06-23 | Ncr Int Inc | System for cash withdrawal |
US8321346B2 (en) * | 2002-12-19 | 2012-11-27 | International Business Machines Corporation | Automated teller machine for use with computing devices |
US7136661B2 (en) * | 2003-07-08 | 2006-11-14 | Lucent Technologies Inc. | Weather alert notification to mobile station upon weather alert occurrence during a time period |
US7062256B2 (en) * | 2003-10-16 | 2006-06-13 | Lucent Technologies Inc. | Network supported new feature notification and trial |
US7230629B2 (en) * | 2003-11-06 | 2007-06-12 | Behr Process Corporation | Data-driven color coordinator |
US7269431B1 (en) * | 2004-01-16 | 2007-09-11 | Cingular Wireless Ii, Llc | System for forwarding SMS messages to other devices |
GB0421743D0 (en) * | 2004-09-30 | 2004-11-03 | Ncr Int Inc | An automated teller machine |
US8836580B2 (en) * | 2005-05-09 | 2014-09-16 | Ehud Mendelson | RF proximity tags providing indoor and outdoor navigation and method of use |
US8559350B2 (en) * | 2005-12-20 | 2013-10-15 | Microsoft Corporation | Mechanism to convey discovery information in a wireless network |
US20070203835A1 (en) * | 2006-02-27 | 2007-08-30 | Yigang Cai | Automated teller service using wireless telephony |
US20080182591A1 (en) * | 2006-12-13 | 2008-07-31 | Synthesis Studios, Inc. | Mobile Proximity-Based Notifications |
US20080245863A1 (en) * | 2007-04-03 | 2008-10-09 | Buchheit Brian K | Shopper and item aware storefront that provides an enhanced shopping experience through automated storefront interactions |
US8249935B1 (en) * | 2007-09-27 | 2012-08-21 | Sprint Communications Company L.P. | Method and system for blocking confidential information at a point-of-sale reader from eavesdropping |
US8126806B1 (en) * | 2007-12-03 | 2012-02-28 | Sprint Communications Company L.P. | Method for launching an electronic wallet |
US8055184B1 (en) * | 2008-01-30 | 2011-11-08 | Sprint Communications Company L.P. | System and method for active jamming of confidential information transmitted at a point-of-sale reader |
DE102008011192A1 (en) * | 2008-02-26 | 2009-08-27 | Wincor Nixdorf International Gmbh | Method and service calculator and system for the transaction of a sum of money |
US20120047070A1 (en) * | 2008-04-02 | 2012-02-23 | Jennifer Pharris | ATM/KIOSK Cash Acceptance |
US20090327135A1 (en) * | 2008-06-26 | 2009-12-31 | Loc Duc Nguyen | Credit card paired with location identifiable device for point of service fraud detection |
US8707319B2 (en) * | 2008-06-26 | 2014-04-22 | Visa International Service Association | Resource location verification by comparing and updating resource location with a location of a consumer device after a threshold of location mismatches is exceeded |
US8090616B2 (en) * | 2008-09-08 | 2012-01-03 | Proctor Jr James Arthur | Visual identification information used as confirmation in a wireless communication |
US9854505B2 (en) * | 2009-02-06 | 2017-12-26 | Avago Technologies General Ip (Singapore) Pte. Ltd. | Service advertisement in a communication device |
US20100173585A1 (en) * | 2009-01-08 | 2010-07-08 | Microsoft Corporation | Seamless data communication experience |
US8083141B1 (en) * | 2009-07-17 | 2011-12-27 | United Services Automobile Association (Usaa) | Systems and methods for transactions with a headless automated teller machine or point of sale device |
US8332320B2 (en) * | 2009-08-31 | 2012-12-11 | Novell, Inc. | Techniques for remote controlled physical transactions with dynamic key generation and authentication |
US8396888B2 (en) * | 2009-12-04 | 2013-03-12 | Google Inc. | Location-based searching using a search area that corresponds to a geographical location of a computing device |
US9544143B2 (en) * | 2010-03-03 | 2017-01-10 | Duo Security, Inc. | System and method of notifying mobile devices to complete transactions |
US20110238573A1 (en) * | 2010-03-25 | 2011-09-29 | Computer Associates Think, Inc. | Cardless atm transaction method and system |
US9210528B2 (en) * | 2010-07-21 | 2015-12-08 | Tksn Holdings, Llc | System and method for control and management of resources for consumers of information |
US8396485B2 (en) * | 2010-11-09 | 2013-03-12 | Apple Inc. | Beacon-based geofencing |
US20120143707A1 (en) * | 2010-12-07 | 2012-06-07 | Deepak Jain | Executing Reader Application |
EP2656292A4 (en) * | 2010-12-23 | 2014-07-02 | Paydiant Inc | Mobile phone atm processing methods and systems |
US9639901B2 (en) * | 2011-01-03 | 2017-05-02 | David Montoya | Geo-location systems and methods |
US11182661B2 (en) * | 2011-01-06 | 2021-11-23 | Maplebear Inc. | Reader network system for presence management in a physical retail environment |
US20120197797A1 (en) * | 2011-01-31 | 2012-08-02 | Bank Of America Corporation | Pending atm transactions |
US20120197798A1 (en) * | 2011-01-31 | 2012-08-02 | Bank Of American Corporation | Pending atm authentications |
US20120209685A1 (en) * | 2011-02-15 | 2012-08-16 | Microsoft Corporation | Check-ins to commercial venues |
US20120239570A1 (en) * | 2011-03-15 | 2012-09-20 | Ing Bank, Fsb (Dba Ing Direct) | Systems and methods for performing ATM transactions using active authentication |
WO2012127095A1 (en) * | 2011-03-18 | 2012-09-27 | Nokia Corporation | Non-networked wireless communication |
US8618932B2 (en) * | 2011-03-18 | 2013-12-31 | Microsoft Corporation | Device location detection |
US9098961B1 (en) * | 2011-04-26 | 2015-08-04 | Diebold Self-Service Systems Division Of Diebold, Incorporated | Automated banking machine that employs a virtual person for assisting customers |
US8353448B1 (en) * | 2011-04-28 | 2013-01-15 | Amazon Technologies, Inc. | Method and system for using machine-readable codes to perform automated teller machine transactions through a mobile communications device |
US20120303448A1 (en) * | 2011-05-26 | 2012-11-29 | Cardtronics, Inc. | Method and apparatus for determining and alerting availability of preferred automated teller machines |
US8413891B2 (en) * | 2011-06-02 | 2013-04-09 | Talaris Holdings Limited | System and method for facilitating banking transactions |
US20130006663A1 (en) * | 2011-06-29 | 2013-01-03 | Mckesson Specialty Arizona Inc. | Location-based services for patients |
US8554671B2 (en) * | 2011-07-18 | 2013-10-08 | Rabih Salem Ballout | System and associated method and service for providing a platform that allows for the exchange of cash between members in a mobile environment |
WO2013025770A1 (en) * | 2011-08-15 | 2013-02-21 | Connectquest | Close proximity notification system |
US9445305B2 (en) * | 2011-09-12 | 2016-09-13 | Microsoft Corporation | Low energy beacon encoding |
WO2013059716A2 (en) * | 2011-10-19 | 2013-04-25 | Ran Margalit | Automated purchasing system |
US9922370B2 (en) * | 2011-11-15 | 2018-03-20 | Ncr Corporation | Techniques for automated teller machine (ATM) transactions |
US8972297B2 (en) * | 2011-11-15 | 2015-03-03 | Citibank, N.A. | System and method for conducting a transaction at a financial transaction terminal using a mobile device |
US20130178233A1 (en) * | 2012-01-10 | 2013-07-11 | Bank Of America Corporation | Dynamic Geo-Fence Alerts |
US20130205133A1 (en) * | 2012-02-07 | 2013-08-08 | David K. Hess | Strongly authenticated, third-party, out-of-band transactional authorization system |
US9544075B2 (en) * | 2012-02-22 | 2017-01-10 | Qualcomm Incorporated | Platform for wireless identity transmitter and system using short range wireless broadcast |
US10586251B2 (en) * | 2012-02-24 | 2020-03-10 | Netclearance Systems, Inc. | Consumer interaction using proximity events |
US9004353B1 (en) * | 2012-03-12 | 2015-04-14 | Diebold Self-Service Systems Division Of Diebold, Incorporated | Check cashing automated banking machine |
US20130262303A1 (en) * | 2012-03-27 | 2013-10-03 | Ebay Inc. | Secure transactions with a mobile device |
US20130282581A1 (en) * | 2012-04-18 | 2013-10-24 | Infosys Limited | Mobile device-based cardless financial transactions |
KR101214503B1 (en) * | 2012-05-18 | 2012-12-21 | (주)위니텍 | Indoor measuring service system using beacon nodes |
US8713638B2 (en) * | 2012-06-30 | 2014-04-29 | AT&T Intellectual Property I, L.L.P. | Managing personal information on a network |
US20140081858A1 (en) * | 2012-09-14 | 2014-03-20 | Diebold Self-Service Systems Division Of Diebold, Incorporated | Banking system controlled responsive to data read from data bearing records |
US10235692B2 (en) * | 2012-10-17 | 2019-03-19 | Groupon, Inc. | Consumer presence based deal offers |
US8972296B2 (en) * | 2012-12-31 | 2015-03-03 | Ebay Inc. | Dongle facilitated wireless consumer payments |
US20140207575A1 (en) * | 2013-01-22 | 2014-07-24 | Index Systems, Inc. | Electronic commerce network using mobile devices |
US20140222574A1 (en) * | 2013-02-04 | 2014-08-07 | Shopkick, Inc. | Presence detection using bluetooth and hybrid-mode transmitters |
CN105027148A (en) * | 2013-02-04 | 2015-11-04 | 肖普基克公司 | Presence detection using Bluetooth and hybrid-mode transmitters |
US9119055B2 (en) * | 2013-02-06 | 2015-08-25 | Facebook, Inc. | Grouping ambient-location updates |
US20140279009A1 (en) * | 2013-03-14 | 2014-09-18 | Bank Of America Corporation | Self-service intercept on or off premise |
US10275827B2 (en) * | 2013-03-14 | 2019-04-30 | Fexco | Systems and methods for transferring funds using a wireless device |
US9356416B2 (en) * | 2013-03-15 | 2016-05-31 | Ofs Fitel, Llc | Suppression of stimulated brillouin scattering in higher-order-mode optical fiber amplifiers |
US9341526B2 (en) * | 2013-04-01 | 2016-05-17 | Saris Cycling Group, Inc. | System for speed-based power calculation |
US9976860B2 (en) * | 2013-04-16 | 2018-05-22 | Apple Inc. | Seamless transition from outdoor to indoor mapping |
US20140324725A1 (en) * | 2013-04-24 | 2014-10-30 | Ebay Inc. | Delivery of goods to dynamically-located users |
US20140379480A1 (en) * | 2013-04-25 | 2014-12-25 | Readme Systems, Inc. | Systems, methods, and devices for interactive marketing with attribution using proximity sensors |
US20140324527A1 (en) * | 2013-04-25 | 2014-10-30 | Readme Systems, Inc. | Proximity detection using sensors based on a programmable multi-array structures |
US20140324614A1 (en) * | 2013-04-25 | 2014-10-30 | Readme Systems, Inc. | Systems, methods, and devices for providing a retail store platform for interacting with shoppers in real-time |
US20140379472A1 (en) * | 2013-04-25 | 2014-12-25 | Readme Systems, Inc. | Systems, methods, and devices for interactive marketing with attribution using proximity sensors |
US8922348B2 (en) * | 2013-06-03 | 2014-12-30 | The Boeing Company | Radio frequency identification notification system |
US20140365334A1 (en) * | 2013-06-07 | 2014-12-11 | Bby Solutions, Inc. | Retail customer service interaction system and method |
US9824545B2 (en) * | 2013-06-28 | 2017-11-21 | Ncr Corporation | Information provision |
GB201312398D0 (en) * | 2013-07-10 | 2013-08-21 | Powa Technologies Ltd | Electronic transaction validation |
US9362953B2 (en) * | 2013-08-02 | 2016-06-07 | Infineon Technologies Ag | Efficient error correction of multi-bit errors |
US9445220B2 (en) * | 2013-09-06 | 2016-09-13 | Paypal, Inc. | Systems and methods for enabling additional devices to check in to bluetooth low energy (BLE) beacons |
US9462357B2 (en) * | 2013-09-11 | 2016-10-04 | Michael Westick | Automated asset tracking system and method |
CA2924742A1 (en) * | 2013-09-20 | 2015-03-26 | Lucova Inc. | Systems and methods for facilitating mobile commerce interactions between customers and merchants |
US20150095161A1 (en) * | 2013-10-02 | 2015-04-02 | Anurag Goel | Universal Retail App and Auxiliary Methods |
US20150120504A1 (en) * | 2013-10-25 | 2015-04-30 | Michael Todasco | Systems and methods for completion of item delivery and transactions using a mobile beacon |
AU2014342341B2 (en) * | 2013-10-29 | 2019-07-25 | Cubic Corporation | Fare collection using wireless beacons |
US20150134374A1 (en) * | 2013-11-13 | 2015-05-14 | Egan Schulz | Systems and methods for multiple service check-in through a single service center check-in |
US10535027B2 (en) * | 2013-11-26 | 2020-01-14 | Paypal, Inc. | Merchant action recommendation system |
CN103903161A (en) * | 2013-12-02 | 2014-07-02 | 奇易科技有限公司 | Method and system with detecting, participating, payment processing and client rewarding functions |
US9760927B2 (en) * | 2013-12-02 | 2017-09-12 | Paypal, Inc. | Customer shopping help system |
US8856045B1 (en) * | 2013-12-18 | 2014-10-07 | PayRange Inc. | Mobile-device-to-machine payment systems |
US10102558B2 (en) * | 2013-12-18 | 2018-10-16 | Paypal, Inc. | Smart dressing rooms |
US9875473B2 (en) * | 2013-12-18 | 2018-01-23 | PayRange Inc. | Method and system for retrofitting an offline-payment operated machine to accept electronic payments |
US9820093B2 (en) * | 2013-12-20 | 2017-11-14 | Apple Inc. | Programmable beacon payloads |
US9407705B2 (en) * | 2014-01-02 | 2016-08-02 | Paypal, Inc. | Proxied push notifications based on user interaction |
US9881261B2 (en) * | 2014-02-25 | 2018-01-30 | Paypal, Inc. | Systems and methods for remote check-in |
US20150248702A1 (en) * | 2014-03-03 | 2015-09-03 | Ebay Inc. | Proximity-based visual notifications |
US20150278866A1 (en) * | 2014-03-26 | 2015-10-01 | Blue Calypso, Llc | System and method for geo-location based content delivery |
US9591570B2 (en) * | 2014-04-07 | 2017-03-07 | Aruba Networks, Inc. | Method and system for tracking devices |
US20150287014A1 (en) * | 2014-04-08 | 2015-10-08 | Ebay Inc. | Managing check in applications using protocol handlers |
CA2945171C (en) * | 2014-04-09 | 2023-10-03 | Capital One Financial Corporation | Systems and computer-implemented processes for providing electronic notifications |
US9588342B2 (en) * | 2014-04-11 | 2017-03-07 | Bank Of America Corporation | Customer recognition through use of an optical head-mounted display in a wearable computing device |
US20150294332A1 (en) * | 2014-04-15 | 2015-10-15 | Michael X. Burns | Sales process review platform |
US11429948B2 (en) * | 2014-04-15 | 2022-08-30 | Capital One Services, Llc | System and method for inter-bank and intra-bank mobile banking communications and transfers |
US9032498B1 (en) * | 2014-05-25 | 2015-05-12 | Mourad Ben Ayed | Method for changing authentication for a legacy access interface |
US9558503B2 (en) * | 2014-09-04 | 2017-01-31 | Sears Brands, L.L.C. | Matching mobile device to transaction and/or customer account |
US10154372B1 (en) * | 2014-11-07 | 2018-12-11 | Wells Fargo Bank, N.A. | Real-time custom interfaces through multi-channel geo-fencing |
US9471940B2 (en) * | 2014-11-26 | 2016-10-18 | Ncr Corporation | Real-time self-service terminal (SST) network awareness |
-
2015
- 2015-04-08 CA CA2945171A patent/CA2945171C/en active Active
- 2015-04-08 US US14/682,053 patent/US10387865B2/en active Active
- 2015-04-08 EP EP15777028.0A patent/EP3129965A4/en not_active Withdrawn
- 2015-04-08 WO PCT/US2015/024990 patent/WO2015157460A1/en active Application Filing
-
2018
- 2018-04-09 US US15/948,087 patent/US10311422B2/en active Active
-
2019
- 2019-07-02 US US16/460,678 patent/US11023877B2/en active Active
-
2021
- 2021-06-01 US US17/335,159 patent/US11915223B2/en active Active
-
2024
- 2024-02-21 US US18/583,814 patent/US20240193575A1/en active Pending
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020112014A1 (en) * | 2000-08-15 | 2002-08-15 | Simon Bennett | Method and apparatus for a network independent short message delivery system |
US20040204078A1 (en) * | 2002-09-30 | 2004-10-14 | Ncr Corporation | Self-service system and method of loading an executable transaction application program from a self-service terminal to a portable electronic device |
US7374079B2 (en) * | 2003-06-24 | 2008-05-20 | Lg Telecom, Ltd. | Method for providing banking services by use of mobile communication system |
US7920849B2 (en) * | 2007-07-13 | 2011-04-05 | Pop Adrian | Method and system for providing advertisements/messages based on wireless data communication technology |
US8751316B1 (en) * | 2010-02-05 | 2014-06-10 | Intuit Inc. | Customer-controlled point-of-sale on a mobile device |
US8548912B2 (en) * | 2010-04-02 | 2013-10-01 | Bank Of America Corporation | Transaction pre-processing with mobile device for a currency dispensing device |
US8598810B2 (en) * | 2011-05-05 | 2013-12-03 | Excelliance Mos Corporation | Constant current driving circuit of light emitting diode and lighting apparatus |
US20130297422A1 (en) * | 2012-04-24 | 2013-11-07 | Qualcomm Incorporated | Retail proximity marketing |
US9356687B2 (en) * | 2012-12-03 | 2016-05-31 | Samsung Electronics Co., Ltd. | Information providing method and mobile terminal therefor |
US20140278994A1 (en) * | 2013-03-14 | 2014-09-18 | Richard J. Greenwood | Interactive Mobile Engagement Recharging Terminal System and Device |
US8646060B1 (en) * | 2013-07-30 | 2014-02-04 | Mourad Ben Ayed | Method for adaptive authentication using a mobile device |
US20150120541A1 (en) * | 2013-10-25 | 2015-04-30 | Bank Of America Corporation | Contribution Destination Identification and Processing |
US20150186872A1 (en) * | 2014-01-01 | 2015-07-02 | Bank Of America Corporation | Temporary virtual card |
US9386416B1 (en) * | 2014-01-29 | 2016-07-05 | Microstrategy Incorporated | Mobile customer presence detection |
US20150213405A1 (en) * | 2014-01-30 | 2015-07-30 | Xerox Corporation | Methods and systems for facilitating document transactions |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10311422B2 (en) | 2014-04-09 | 2019-06-04 | Capital One Services, Llc | Systems and computer-implemented processes for providing electronic notifications |
US10387865B2 (en) * | 2014-04-09 | 2019-08-20 | Capital One Services, Llc | Systems and computer-implemented processes for providing electronic notifications |
US11023877B2 (en) * | 2014-04-09 | 2021-06-01 | Capital One Services, Llc | Systems and computer-implemented processes for providing electronic notifications |
US11915223B2 (en) | 2014-04-09 | 2024-02-27 | Capital One Services, Llc | Systems and computer-implemented processes for providing electronic notifications |
US11974188B1 (en) | 2014-11-07 | 2024-04-30 | Wells Fargo Bank, N.A. | Multi-channel geo-fencing systems and methods |
US11026043B1 (en) | 2014-11-07 | 2021-06-01 | Wells Fargo Bank, N.A. | Multi-channel geo-fencing systems and methods |
US11272317B1 (en) | 2014-11-07 | 2022-03-08 | Wells Fargo Bank, N.A. | Multi-channel geo-fencing systems and methods |
US11432103B1 (en) | 2014-11-07 | 2022-08-30 | Wells Fargo Bank, N.A. | Real-time custom interfaces through multi-channel geo-fencing |
US11729578B1 (en) | 2014-11-07 | 2023-08-15 | Wells Fargo Bank, N.A. | Real time custom interfaces through multi-channel geo-fencing |
US11570573B1 (en) | 2014-11-07 | 2023-01-31 | Wells Fargo Bank, N.A. | Multi-channel geo-fencing systems and methods |
US11715078B1 (en) * | 2016-04-01 | 2023-08-01 | Wells Fargo Bank, N.A. | Systems and methods for remote ATM access |
US20230376919A1 (en) * | 2016-04-01 | 2023-11-23 | Wells Fargo Bank, N.A. | Systems and methods for remote atm access |
US11354631B1 (en) * | 2016-04-01 | 2022-06-07 | Wells Fargo Bank, N.A. | Systems and methods for remote atm access |
US10467842B2 (en) | 2017-03-17 | 2019-11-05 | Bank Of America Corporation | Portable item transfer container |
US20190347643A1 (en) * | 2018-05-11 | 2019-11-14 | Mastercard International Incorporated | Method and system for contactless withdrawal from an atm |
US10990955B2 (en) * | 2018-05-11 | 2021-04-27 | Mastercard International Incorporated | Method and system for contactless withdrawal from an ATM |
US20200005261A1 (en) * | 2018-06-27 | 2020-01-02 | Bank Of America Corporation | Frictionless Automated Teller Machine |
US20200005263A1 (en) * | 2018-06-27 | 2020-01-02 | Bank Of America Corporation | Frictionless Automated Teller Machine |
US20200005262A1 (en) * | 2018-06-27 | 2020-01-02 | Bank Of America Corporation | Frictionless Automated Teller Machine |
US11521187B2 (en) * | 2020-04-10 | 2022-12-06 | Ncr Corporation | Wireless device for retrofitting ATMs |
US20210319416A1 (en) * | 2020-04-10 | 2021-10-14 | Ncr Corporation | Wireless Device for Retrofitting ATMs |
Also Published As
Publication number | Publication date |
---|---|
US10311422B2 (en) | 2019-06-04 |
US20210357904A1 (en) | 2021-11-18 |
US11023877B2 (en) | 2021-06-01 |
EP3129965A1 (en) | 2017-02-15 |
CA2945171C (en) | 2023-10-03 |
US11915223B2 (en) | 2024-02-27 |
US20240193575A1 (en) | 2024-06-13 |
CA2945171A1 (en) | 2015-10-15 |
WO2015157460A1 (en) | 2015-10-15 |
US20180225652A1 (en) | 2018-08-09 |
US20190325423A1 (en) | 2019-10-24 |
EP3129965A4 (en) | 2017-08-16 |
US10387865B2 (en) | 2019-08-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11915223B2 (en) | Systems and computer-implemented processes for providing electronic notifications | |
KR102238314B1 (en) | Identity authentication methods, devices and systems | |
US10776776B2 (en) | System and method of loading a transaction card and processing repayment on a mobile device | |
US11995634B2 (en) | Systems and methods for providing near field communications | |
US9038894B2 (en) | Payment or other transaction through mobile device using NFC to access a contactless transaction card | |
US11392926B2 (en) | System, method and computer program product for automatic and remote control of NFC transaction processing | |
US11494777B2 (en) | Enriching transaction request data for maintaining location privacy while improving fraud prevention systems on a data communication network with user controls injected to back-end transaction approval requests in real-time with transactions | |
US20170004499A1 (en) | Method and system for cross-border travel alerts | |
US11908286B2 (en) | Computer-based system for provisioning new accounts using location-based authentication | |
US20190197539A1 (en) | Method of providing service for setting condition of card use, card company server and user terminal | |
KR101485931B1 (en) | system and method for window transaction application | |
US20220005040A1 (en) | Using Augmented Reality Data as Part of a Fraud Detection Process | |
US20220188804A1 (en) | Method and system for facilitating mobile contactless payments |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CAPITAL ONE FINANCIAL CORPORATION, VIRGINIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KOEPPEL, ADAM R.;NIDERBERG, ALEX LEO;SIGNING DATES FROM 20150513 TO 20160505;REEL/FRAME:039946/0622 |
|
AS | Assignment |
Owner name: CAPITAL ONE SERVICES, LLC, VIRGINIA Free format text: CHANGE OF NAME;ASSIGNOR:CAPITAL ONE FINANCIAL CORPORATION;REEL/FRAME:047446/0290 Effective date: 20141118 |
|
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 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |