US20180218345A1 - Systems and methods for processing preauthorized automated banking machine-related transactions - Google Patents

Abstract

Embodiments of the disclosure enable a transaction to be preauthorized. A system receives a request for preauthorization of a transaction including a transaction amount and a cardholder identifier, identifies a cardholder account based on the cardholder identifier, determines a transaction timeframe and a machine identifier, and accesses the cardholder account to determine whether to process the transaction in accordance with a nonvisual communication program. On condition that the transaction is to be processed in accordance with the nonvisual communication program, the system generates an instruction to identify a capture time, determine whether the capture time satisfies the transaction timeframe, and dispense the transaction amount of cash in accordance with the nonvisual communication program on condition that the capture time satisfies the transaction timeframe. Aspects of the disclosure provide for preauthorizing the transaction in a secure and user-friendly manner.

Description

FIELD OF THE DISCLOSURE
• The subject matter described herein relates generally to information processing and, more specifically, to systems and methods for processing one or more preauthorized automated banking machine-related transactions.
BACKGROUND
• Automated banking machines have made great gains as a means to attract financial accounts to financial institutions. For example, at least some automated banking machines have made it easier for cardholders to enter into at least some financial transactions, such as deposit transactions, cash withdrawal transactions, and check cashing transactions. At least some cardholders, however, are deterred from using automated banking machines for various reasons. A cardholder who prefers to enter into a financial transaction using nonvisual communication, for example, may perceive that using at least some known automated banking machines is risky, tedious, and/or time-consuming.
SUMMARY
• Embodiments of the disclosure enable a computing system to preauthorize one or more financial transactions. The computing system includes a memory device storing data associated with one or more cardholder accounts and computer-executable instructions, and a processor. The processor executes the computer-executable instructions to receive a request for preauthorization of a financial transaction including a transaction amount and a cardholder identifier, identify a cardholder account based on the cardholder identifier, determine a transaction timeframe and a machine identifier associated with the financial transaction, and access the cardholder account to determine whether to process the financial transaction in accordance with a nonvisual communication program. On condition that the financial transaction is to be processed in accordance with the nonvisual communication program, the processor is configured to generate an instruction to identify a capture time associated with the financial transaction, determine whether the capture time satisfies the transaction timeframe, and dispense the transaction amount of cash in accordance with the nonvisual communication program on condition that the capture time satisfies the transaction timeframe.
• In another aspect, one or more computer storage media embodied with computer-executable instructions are provided. The computer storage media includes a preauthorization component, a detection component, and a dispenser component. The preauthorization component obtains a preauthorization message associated with a financial transaction, and analyzes the preauthorization message to identify a transaction amount and a cardholder account associated with the financial transaction. The detection component determines that a cardholder associated with the cardholder account is proximate to a cash machine, identifies a capture time associated with the financial transaction, and determines whether the capture time satisfies the transaction timeframe. The dispenser component dispenses the transaction amount of cash in accordance with a nonvisual communication program.
• In yet another aspect, a computer-implemented method is provided for preauthorizing one or more financial transactions. The computer-implemented method includes identifying a request for preauthorization of a financial transaction including a transaction amount and a cardholder identifier, determining a transaction timeframe associated with the financial transaction, identifying a cash machine associated with the financial transaction, and determining whether to process the financial transaction in accordance with a nonvisual communication program. On condition that the financial transaction is to be processed in accordance with the nonvisual communication program, the computer-implemented method includes generating a preauthorization instruction to dispense the transaction amount of cash in accordance with the nonvisual communication program upon determining that a capture time associated with the financial transaction satisfies the transaction timeframe.
• This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a block diagram illustrating an example environment for processing financial transactions.
• FIG. 2 is a block diagram illustrating an example ecosystem for processing financial transactions in an environment, such as the environment shown inFIG. 1.
• FIG. 3 is a block diagram illustrating an example computing system for processing preauthorized financial transactions in an ecosystem, such as the ecosystem shown inFIG. 2.
• FIG. 4 is a flowchart of an example method for processing preauthorized financial transactions using a computing system, such as the computing system shown inFIG. 3.
• FIG. 5 is a block diagram illustrating example components that may be used to process preauthorized financial transactions in an ecosystem, such as the ecosystem shown inFIG. 2.
• FIG. 6 is a sequence diagram of an example method for processing preauthorized financial transactions in an ecosystem, such as the ecosystem shown inFIG. 2.
• FIG. 7 is a flow diagram of an example dataflow for processing preauthorized financial transactions in an ecosystem, such as the ecosystem shown inFIG. 2.
• FIG. 8 is a block diagram illustrating an example operating environment in which financial transactions may be processed.
• Corresponding reference characters indicate corresponding parts throughout the drawings.
DETAILED DESCRIPTION
• The subject matter described herein relates to processing one or more automated banking machine-related financial transactions. Embodiments of the disclosure enable a cardholder to obtain authorization of a financial transaction prior to realizing or carrying out the financial transaction at an automated banking machine, such as an automated teller machine (ATM). The financial transaction may be preauthorized, for example, in a trusted environment. For example, a user device associated with the cardholder may be used to enter into the financial transaction and/or obtain authorization of the financial transaction. In this manner, the cardholder may approach the automated banking machine with increased confidence that the interaction with the automated banking machine will be favorable, quick, and efficient. At least some embodiments described herein preauthorize financial transactions and/or carry out the preauthorized financial transactions in accordance with a nonvisual communication program.
• While no personally identifiable information is tracked by the embodiments described herein, the embodiments have been described with reference to data being monitored and/or collected from one or more users (e.g., the cardholder). The data may be monitored and/or collected in accordance with applicable data privacy laws and regulations. For example, notice may be provided to the users (e.g., via a dialog box or preference setting), and/or users may be given the opportunity to give or deny consent for the monitoring and/or collection of the data. The consent may take the form of opt-in consent or opt-out consent.
• Aspects of the disclosure provide for a computing system that performs one or more operations in an environment including a plurality of devices coupled to each other via a network (e.g., a local area network (LAN), a wide area network (WAN), the Internet). For example, a cashier system may communicate with a user device and/or a financial transaction processing computing device to perform one or more operations in a financial transaction processing environment. In some embodiments, the cashier system facilitates dataflow between the user device and the financial transaction processing computing device to enable a cardholder to obtain preauthorization of a financial transaction and carry out the preauthorized financial transaction at an automated banking machine efficiently and effectively.
• The systems and processes described herein may be implemented using computer programming or engineering techniques including computer software, firmware, hardware or a combination or subset thereof. At least one technical problem with known computing systems is that it can be risky, tedious, and/or time-consuming to process at least some financial transactions. The embodiments described herein address at least this technical problem. By preauthorizing financial transactions and carrying out the preauthorized financial transactions in the manner described in this disclosure, some embodiments reduce fraud and/or processing costs, increase user efficiency and/or user confidence, and/or improve user experience and/or user interaction performance. Additionally, some embodiments improve data integrity, data transmission security, and/or communication between systems by allowing a financial transaction to be authorized in a trusted environment; and/or reduce error rate by automating at least a portion of the transaction authorization process. Moreover, some embodiments may facilitate improving processor speed, processor security, and/or operating system resource allocation.
• The technical effect of the systems and processes described herein is achieved by performing at least one of the following operations: a) analyzing a request for preauthorization of a financial transaction; b) determining a transaction timeframe and a machine identifier; c) analyzing user location data and machine location data to identify a transaction timeframe; d) analyzing user location data and time data to identify a cash machine; e) generating a prompt to select a set of cash machines; f) analyzing user input associated with a selection of the set of cash machines; g) determining whether to process the financial transaction in accordance with a nonvisual communication program; h) generating an instruction to identify a capture time associated with the financial transaction, i) generating an instruction to determine whether the capture time satisfies the transaction timeframe; j) generating an instruction to dispense the transaction amount of cash; k) determining whether a hold duration associated with the financial transaction exceeds a hold threshold; l) generating a request to modify the transaction timeframe and/or identify another cash machine; m) analyzing position data to determine whether a user device or access card is proximate to the cash machine; n) detecting a transmission associated with an object; o) scanning a predetermined scan area to generate scan data associated with an object; p) analyzing the scan data to identify an identifier associated with the object; q) determining whether the object is associated with the cardholder account; and r) identifying a notification indicative of the transaction amount of cash being dispensed.
• FIG. 1 is a block diagram illustrating anexample environment100 for processing one or more financial transactions. Theenvironment100 includes aprocessing network110, such as the MASTERCARD® brand payment processing network (MASTERCARD® is a registered trademark of MasterCard International Incorporated located in Purchase, N.Y.). The MASTERCARD® brand payment processing network is a propriety network for exchanging financial transaction data between members of the MASTERCARD® brand payment processing network.
• Theenvironment100 includes one ormore merchants120 that accept payment via theprocessing network110. To accept payment via theprocessing network110, themerchant120 establishes a financial account with anacquirer130 that is a member of theprocessing network110. Theacquirer130 is a financial institution that maintains a relationship with one ormore merchants120 to enable themerchants120 to accept payment via theprocessing network110. Theacquirer130 may also be known as an acquiring bank, a processing bank, or a merchant bank.
• Theenvironment100 includes one ormore issuers140 that issue or provide one ormore payment cards150 to one ormore cardholders160 or, more broadly, account holders (“cardholder” and “account holder” may be used interchangeably herein). Anissuer140 is a financial institution that maintains a relationship with acardholder160 to enable thecardholder160 to make a payment using apayment card150 via theprocessing network110. As described herein, the term “payment card” includes credit cards, debit cards, prepaid cards, key fobs, digital cards, smart cards, and any other payment product that is linked or associated with a corresponding cardholder account maintained by theissuer140.
• Thecardholder160 may use thepayment card150 to enter into one or more financial transactions with one ormore merchants120. Thepayment card150 may have any shape, size, or configuration that enables thecardholder160 to make a payment to amerchant120 using a cardholder account. For example, account information stored in a microchip or magnetic stripe on thepayment card150 may be used to identify a cardholder account associated with thepayment card150. In some embodiments, thepayment card150 uses mobile payment technology and/or contactless payment technology to facilitate communication between thecardholder160 and themerchant120. For example, thepayment card150 may include or be associated with a radio frequency identification (RFID)-enabled device, a BLUETOOTH® brand wireless technology-enabled device, a WI-FI® brand local area wireless computing network-enabled device, and/or a near field communication (NFC) wireless communication-enabled device. (BLUETOOTH® is a registered trademark of Bluetooth Special Interest Group, and WI-FI® is a registered trademark of the Wi-Fi Alliance).
• In some embodiments, thecardholder160 presents themerchant120 with thepayment card150 to make a payment to themerchant120 using the cardholder account in exchange for the good or service. Alternatively, thecardholder160 may provide themerchant120 with account information associated with thepayment card150 without physically presenting thepayment card150 to the merchant120 (e.g., for remote financial transactions, including e-commerce transactions, card-not-present transactions, or card-on-file transactions). Account information may include, for example, a name of thecardholder160, an account number, an expiration date, and/or a security code (e.g., a card verification value (CVV), a card verification code (CVC), a personal identification number (PIN)).
• Themerchant120 requests authorization from anacquirer130 for at least the amount of the purchase. Themerchant120 may request authorization using any financial transaction computing device configured to transmit account information of thecardholder160 to one or more financial transaction processing computing devices of theacquirer130. For example, themerchant120 may use a point-of-sale (POS) terminal that reads account information from the microchip or magnetic stripe on thepayment card150 and transmits the account information to a financial transaction processing computing device of theacquirer130. Additionally or alternatively, the POS terminal may receive the account information from a communication device using mobile payment technology and/or contactless payment technology, and transmit the account information to the financial transaction processing computing device of theacquirer130.
• Using theprocessing network110, the financial transaction processing computing device of theacquirer130 communicates with one or more financial transaction processing computing devices of anissuer140 to determine whether the account information of thecardholder160 matches or corresponds to the account information of theissuer140, whether the cardholder account is in good standing, and/or whether the purchase is covered by an available credit line or account balance associated with the cardholder account (e.g., a purchase amount is less than an account capacity). Based on these determinations, a financial transaction processing computing device of theissuer140 determines whether to approve or decline the request for authorization from themerchant120.
• If the request for authorization is declined, themerchant120 is notified (e.g., via the processing network110) as such, and may request authorization from theacquirer130 for a lesser amount or request an alternative form of payment (e.g., cash, another payment card150) from thecardholder160. If the request for authorization is approved, an authorization code is issued (e.g., via the processing network110) to themerchant120, and the available credit line or account balance associated with the cardholder account is decreased by at least the amount of the purchase. The financial transaction is then settled between themerchant120, theacquirer130, theissuer140, and/or thecardholder160. Settlement typically includes theacquirer130 reimbursing themerchant120 for selling the good or service, and theissuer140 reimbursing the acquirer for reimbursing themerchant120. When a credit card is used, theissuer140 may bill thecardholder160 to settle the cardholder account (e.g., a credit card account) with thecardholder160. When a debit or prepaid card is used, theissuer140 may automatically withdraw funds from the cardholder account (e.g., a checking account, a savings account) to settle the cardholder account.
• FIG. 2 is a block diagram illustrating anexample ecosystem200 for allowing a user202 (e.g., cardholder160) to obtain preauthorization of one or more financial transactions and/or carry out the preauthorized financial transactions in theenvironment100. Theuser202 may use a user device210 to enter into a financial transaction (e.g., a first financial transaction).
• The user device210 includes one or more memory devices or computer-readable media212 storing computer-executable instructions, and one ormore processors214 configured to execute the computer-executable instructions to perform one or more operations, such as obtain account information associated with theuser202. In some embodiments, aprocessor214 executes or runs one or more applications (apps) to perform the operations. A payment card app, for example, may be used to enter into a financial transaction. A global positioning system (GPS) app, for another example, may be used to identify a position of the user device210.
• The user device210 may use one ormore interfaces216 to present information to and/or receive user input from a user of the user device210 (e.g., user202). For example, aninterface216 may be used to receive user input indicative of the account information. Theinterfaces216 may also be used to transmit data to and/or receive data from one or more other computing systems. For example, aninterface216 may be used to transmit account information to acashier system220 for facilitating the financial transaction. The user device210 may include an instance of an application (e.g., a client-side application) that enables the user device210 to communicate with another computing system (e.g., a cloud-computing provider) that performs one or more backend operations using a counterpart application (e.g., server-side application) and/or through one or more server-side services.
• Thecashier system220 includes amerchant device230 configured to obtain the account information for facilitating the financial transaction. Themerchant device230 may be associated, for example, with a retailer or a financial institution. Themerchant device230 includes one or more memory devices or computer-readable media232 storing computer-executable instructions, and one ormore processors234 configured to execute the computer-executable instructions to perform one or more operations, such as generate a request for preauthorization of the financial transaction. In some embodiments, aprocessor234 executes or runs one or more applications to perform the operations. A payment card app, for example, may be used to facilitate the financial transaction.
• Themerchant device230 may use one ormore interfaces236 to present information to and/or receive user input from a user of the merchant device230 (e.g., merchant120). Theinterfaces236 may also be used to transmit data to and/or receive data from one or more other computing systems (e.g., user device210). For example, aninterface236 may be used to receive the account information from the user device210. For another example, aninterface236 may be used to transmit the request for preauthorization to a system server240 (e.g., a financial transaction processing computing device of an issuer140) for processing the financial transaction.
• Themerchant device230 may include a server-side application that enables one or more client-side services to be provided at one or more other computing systems (e.g., user device210). Additionally or alternatively, themerchant device230 may include a client-side application that enables themerchant device230 to communicate with a cloud-computing provider (e.g., the system server240) that performs one or more backend operations using a server-side application and/or through one or more server-side services.
• Thesystem server240 is configured to obtain the request for preauthorization for processing the financial transaction. Thesystem server240 includes one or more memory devices or computer-readable media242 storing computer-executable instructions, and one ormore processors244 configured to execute the computer-executable instructions to perform one or more operations, such as generate one or more preauthorization messages associated with the financial transaction. Preauthorization messages may include, for example, a notification, an instruction, a prompt, and the like. In some embodiments, aprocessor244 executes or runs one or more applications to perform the operations. A payment card app, for example, may be used to process the financial transaction.
• Thesystem server240 may use one ormore interfaces246 to present information to and/or receive user input from a user of the system server240 (e.g., issuer140). Theinterfaces246 may also be used to transmit data to and/or receive data from the other computing systems (e.g., user device210, merchant device230). For example, aninterface246 may be used to receive the request for preauthorization from thecashier system220. For another example, aninterface246 may be used to transmit a preauthorization message to the user device210 used to enter into the financial transaction, another user device210 associated with the user202 (e.g., a mobile device), and/or thecashier system220 for carrying out the financial transaction.
• Thesystem server240 may include a server-side application that enables one or more client-side services to be provided at one or more other computing systems (e.g., user device210, merchant device230). Additionally or alternatively, thesystem server240 may include a client-side application that enables thesystem server240 to communicate with a cloud-computing provider that performs one or more backend operations using a server-side application and/or through one or more server-side services.
• Thecashier system220 includes one ormore cash machines250 configured to obtain the preauthorization message for carrying out the financial transaction. Acash machine250 may be included in, coupled to, and/or associated with themerchant device230. Thecash machine250 includes one or more memory devices or computer-readable media252 storing computer-executable instructions, and one ormore processors254 configured to execute the computer-executable instructions to perform one or more operations, such as carry out the financial transaction. In some embodiments, aprocessor254 executes or runs one or more applications to perform the operations. A payment card app, for example, may be used to carry out the financial transaction. A GPS app, for another example, may be used to identify a position of thecash machine250.
• Thecash machine250 may use one ormore interfaces256 to transmit data to and/or receive data from the other computing systems (e.g., user device210,merchant device230, system server240). For example, aninterface256 may be used to receive a preauthorization message from themerchant device230 and/orsystem server240. Theinterfaces256 may also be used to present information to and/or receive user input from a user of the cash machine250 (e.g.,merchant120, user202). For example, aninterface256 may be used to present a preauthorization message to the user of thecash machine250.
• Amanned cash machine250 enables a user affiliated with themerchant120, such as a cashier at a retailer or a teller at a financial institution, to service a customer or client of the merchant120 (e.g., user202) for carrying out the financial transaction. Anautomated cash machine250, such as a self-serve kiosk at a retailer or an automated banking machine (e.g., ATM) at a financial institution, enables theuser202 to carry out the financial transaction with little or no assistance from a user affiliated with themerchant120.
• Thecash machine250 may include a client-side application that enables thecash machine250 to communicate with a cloud-computing provider (e.g.,merchant device230, system server240) that performs one or more backend operations using a server-side application and/or through one or more server-side services. For example, a thin client included in, coupled to, and/or associated with thecash machine250 may provide remote access to themerchant device230 and/orsystem server240 for performing one or more backend operations.
• Theecosystem200 includes one ormore communication networks260 that enable information to be communicated between a plurality of computing or communication systems coupled to the communication networks260 (e.g., user device210,cashier system220,merchant device230,system server240, cash machine250).Example communication networks260 include a cellular or mobile network and the Internet. Alternatively, thecommunication networks260 may include any communication medium that enables theecosystem200 to function as described herein including, for example, a personal area network (PAN), a LAN, and/or a WAN.
• FIG. 3 is a block diagram illustrating anexample computing system300 that may be used to process one or more preauthorized financial transactions in theecosystem200. Auser202 may use a user device210 to obtain authorization to withdraw or obtain cash at acash machine250 remote from the user device210. Cash may be obtained, for example, through a cash withdrawal action that allows funds to be withdrawn from a user account (e.g., checking account, savings account) and/or through a cash disbursement action that allows funds to be “purchased” using the user account (e.g., credit card account).
• The user device210 may be used to provide amerchant device230 associated with thecash machine250 with account information associated with an access card310 (e.g., payment card150), such as acardholder identifier312. The account information may be provided without physically presenting thepayment card150 to themerchant device230 and/or to thecash machine250. Theaccess card310 may be, for example, an EMV® brand smart card. (EMV® is a registered trademark of EMVCo, LLC). In some embodiments, the account information includes data indicative of an enrollment status associated with a nonvisual communication program. Themerchant device230 uses the account information to generate a request for preauthorization of a financial transaction, and transmits the request to asystem server240 for processing the financial transaction. The request may include, for example, the account information and atransaction amount314.
• In response to receiving the request for preauthorization, thesystem server240 analyzes the request to identify thecardholder identifier312, and uses thecardholder identifier312 to identify acardholder account320 associated with thecardholder identifier312. Thecardholder account320 may be identified or selected, for example, from one or more cardholder accounts stored and/or maintained at thesystem server240. In some embodiments, thesystem server240 identifies, from the cardholder accounts, a first cardholder account (e.g., cardholder account320) associated withcredential data322 that matches or corresponds to thecardholder identifier312.Credential data322 includes any data that enables an entity (e.g.,user202, user device210) to be identified and/or authenticated.Credential data322 may include, for example, an account number, a username, a PIN, a password, a public key infrastructure (PKI) certificate, a token, biometric data, and the like.
• Thesystem server240 uses account data associated with thecardholder account320 to process the financial transaction. In some embodiments, thesystem server240 identifies an account threshold (e.g., an available credit line, an available account balance) associated with thecardholder account320, and determines whether thetransaction amount314 exceeds the account threshold. If thetransaction amount314 is less than or equal to the account threshold, thesystem server240 approves the request for preauthorization, reserves or allocates preauthorized funds, and generates a response to the request in accordance with the approval. The response may include, for example, apreauthorization code324 that may be used to authenticate a holder of thepreauthorization code324 for obtaining or capturing the preauthorized funds. If thetransaction amount314 is greater than the account threshold, thesystem server240 declines the request for preauthorization and generates a response to the request in accordance with the declination.
• Preauthorized funds may be obtained or captured at acash machine250, for example, to realize or carry out the financial transaction. In some embodiments, thesystem server240 identifies or determines atransaction timeframe332 in which the preauthorized funds may be captured for carrying out the financial transaction. Additionally, thesystem server240 may identify or determine one ormore machine identifiers334 associated with one ormore cash machines250 at which the preauthorized funds may be captured for carrying out the financial transaction. Thetransaction timeframe332 and/ormachine identifiers334 may be determined based ontime data336,machine location data338 associated with one or more geolocations of thecash machines250, and/or user location data340 associated with a geolocation of theuser202. In some embodiments, thesystem server240 identifies and/or generates thetime data336,machine location data338, and/or user location data340 based on user input. For example, the request for preauthorization may be analyzed to identify and/or generate thetime data336,machine location data338, and/or user location data340. For another example, theuser202 may be prompted to identify a desired time and/or geolocation.
• In some embodiments, thesystem server240 identifies and/or generates the user location data340 based on position data342 (e.g., GPS data). Theposition data342 may be associated with an object that is associated with theuser202, such as the user device210 or theaccess card310. Contactdata344 associated with thecardholder account320, for example, may be used to communicate with one or more user devices210 associated with theuser202 for obtaining theposition data342.Contact data344 includes any data that enables an entity (e.g.,user202, user device210) to be located and/or approached for communicating with the entity.Contact data344 may include, for example, a telephone number, a BLUETOOTH® brand wireless technology identifier, a routing number, an Internet Protocol (IP) address, a media access controller (MAC) address, an NFC identifier, an RFID identifier, and the like.
• Thetime data336,machine location data338, and/or user location data340 may be identified, generated, and/or modified in accordance withpreference data346 associated with thecardholder account320.Preference data346 may be indicative of one or more tastes, tendencies, or biases of an entity (e.g., user202). Tastes, tendencies, and/or biases may be expressed by the user202 (e.g., via user input) or implied based on other data associated with theuser202. For example, a transaction history indicative of a repeated time and/or geolocation may be indicative of a preference for the repeated time and/or geolocation.
• Thesystem server240 generates one or more preauthorization messages that enable theuser202 to carry out the financial transaction within thetransaction timeframe332 and/or at apredetermined cash machine250. The preauthorization messages may include, for example, amachine instruction352 and/or a user instruction354. Themachine instruction352 may be transmitted to one or morepredetermined cash machines250 such that thepredetermined cash machines250 are configured to perform one or more operations for carrying out the financial transaction. The user instruction354 may be transmitted to the user device210 used to enter into the financial transaction, a user device210 different from the user device210 used to enter into the financial transaction, and/or thepredetermined cash machines250 such that a user device210 and/or apredetermined cash machine250 is configured to present the user instruction354 to theuser202.
• Theuser202 may follow the user instruction354 to capture the preauthorized funds within thetransaction timeframe332 at apredetermined cash machine250. In some embodiments, the cashier system220 (e.g.,merchant device230, cash machine250) identifies acapture time362 associated with a moment the preauthorized funds are captured. Thecapture time362 may be identified, for example, upon receiving thepreauthorization code324. Thecapture time362 may also be identified, for another example, upon identifying that theuser202 is proximate to thepredetermined cash machine250.
• In some embodiments, thecashier system220 scans a predetermined scan area proximate to thecash machine250 to generate scan data, and analyzes the scan data to determine whether theuser202 is proximate to thepredetermined cash machine250. For example, thecashier system220 may generate scan data associated with a user device210 and/oraccess card310 presented to thecash machine250 for capturing the preauthorized funds. For another example, thecashier system220 may generate scan data associated with theuser202, user device210, and/oraccess card310 approaching thecash machine250 for capturing the preauthorized funds. The scan data may be analyzed to authenticate theuser202 in the predetermined scan area as being authorized to capture the preauthorized funds. Additionally or alternatively, thecashier system220 receivesposition data342 associated with the user device210 and/oraccess card310, and analyzes theposition data342 to determine whether theuser202 is proximate to thepredetermined cash machine250 for authenticating theuser202.
• Upon identifying thecapture time362, thecashier system220 determines whether thecapture time362 satisfies thetransaction timeframe332. If thecapture time362 is less than or equal to the transaction timeframe332 (e.g., thetransaction timeframe332 has not expired or “timed out”), thecash machine250 dispenses an amount of cash associated with thetransaction amount314. In some embodiments, thecash machine250 dispenses the amount of cash in accordance with adenomination breakdown372. Thedenomination breakdown372 may be included in themachine instruction352. For example, thedenomination breakdown372 may be identified based on the request for preauthorization and/orpreference data346. Alternatively, theuser202 may be prompted to identify a desireddenomination breakdown372.
• Upon dispensing the amount of cash associated with thetransaction amount314, thecashier system220 generates and transmits anotification374 that is indicative of the amount of cash being dispensed. Thenotification374 may be received, for example, at thesystem server240 to enable thesystem server240 to recognize or identify the financial transaction as being realized or carried out. On condition that acapture time362 is not or yet to be identified, thecashier system220 and/orsystem server240 may periodically (e.g., each predetermined interval of time) and/or systematically (e.g., each predetermined occurrence) determine whether ahold duration376 associated with the preauthorized funds satisfies one or morepredetermined hold thresholds378.
• If thehold duration376 exceeds apredetermined hold threshold378, thetransaction timeframe332 may be extended or increased and/or a more-proximate or more-convenient cash machine250 may be identified. In some embodiments, thecashier system220 and/orsystem server240 communicates with the user device210 to prompt theuser202 to modify thetransaction timeframe332 and/or identify anothercash machine250. If thehold duration376 exceeds the transaction timeframe332 (e.g., acapture time362 is not identified before thetransaction timeframe332 expires or “times out”), the preauthorized funds are released to enable thesystem server240 to allocate the funds towards another financial transaction, including another preauthorized financial transaction.
• In some embodiments, thecashier system220 and/orsystem server240 determines whether to process the financial transaction in accordance with a nonvisual communication program. For example, thecashier system220 and/orsystem server240 may determine whether thecardholder account320 is enrolled in or associated with a nonvisual communication program. If thecardholder account320 is associated with the nonvisual communication program, thecashier system220 and/orsystem server240 communicates with theuser202 using nonvisual communication (e.g., at the user device210, themerchant device230, and/or the cash machine250). A cardholder account may be enrolled in the nonvisual communication program, for example, if a user of the cardholder account is blind or prefers to communicate using one or more nonvisual communications, such as an audible communication and/or a tactile communication. In some embodiments, thecashier system220 and/orsystem server240 uses or analyzespreference data346 to identify an enrollment status of thecardholder account320.
• FIG. 4 is a flowchart illustrating anexample method400 for processing a preauthorized financial transaction in theecosystem200 using a computing system (e.g.,merchant device230, system server240). A request for preauthorization of a financial transaction is identified at410. The request for preauthorization may be generated at and/or received from, for example, acashier system220. In some embodiments, the request for preauthorization includes acardholder identifier312 and atransaction amount314.
• Upon approving the request for preauthorization, atransaction timeframe332 in which preauthorized funds may be captured is determined at420, and one ormore cash machines250 at which the preauthorized funds may be captured are identified at430. Thetransaction timeframe332 and/orcash machines250 may be determined and/or identified based on one or more communications with the user device210. For example, the request for preauthorization may be analyzed to identify thetransaction timeframe332, one ormore machine identifiers334,time data336,machine location data338, and/or user location data340. For another example,position data342 associated with the user device210 and/oraccess card310 may be received. For yet another example, a user of the user device210 (e.g., user202) may be prompted to identify a desired time and/or geolocation for capturing the preauthorized funds. In some embodiments,preference data346 associated with acardholder account320 used to enter into the financial transaction may be used to determine, identify, and/or modify thetransaction timeframe332,machine identifiers334,time data336,machine location data338, and/or user location data340.
• Preference data346 may also be used to determine whether to process the financial transaction in accordance with a nonvisual communication program. For example,preference data346 may be used to determine at440 whether thecardholder account320 is associated with the nonvisual communication program. If thecardholder account320 is not enrolled in the nonvisual communication program, an instruction is generated at450 to dispense cash in a conventional manner. For example, the instruction may configure thecash machine250 to use visual prompts and/or instructions for carrying out the financial transaction.
• On the other hand, if the financial transaction is to be processed in accordance with the nonvisual communication program (e.g., if thecardholder account320 is enrolled in the nonvisual communication program), amachine instruction352 is generated at460 to dispense cash in accordance with the nonvisual communication program. For example, themachine instruction352 may configure thecash machine250 to use nonvisual prompts and/or instructions for carrying out the financial transaction. For another example, themachine instructions352 may configure thecash machine250 to dispense cash in a manner that allows theuser202 to confirm or verify that thetransaction amount314 of cash was dispensed from thecash machine250 using nonvisual cues.
• FIG. 5 is a block diagram illustrating a computing system500 (e.g.,cashier system220, system server240) including aninterface component510, an account component520, apreauthorization component530, anidentification component540, adetection component550, adispenser component560, and/or amodification component570 that may be used to process one or more preauthorized financial transactions in theecosystem200.
• In some embodiments, theinterface component510 enables thecomputing system500 to receive data from and/or transmit data to one or more other computing systems (e.g., user device210,cashier system220,merchant device230,system server240, cash machine250). For example, theinterface component510 may be coupled to another computing system to facilitate communication between the other computing system and the account component520, thepreauthorization component530, theidentification component540, thedetection component550, thedispenser component560, and/or themodification component570. In some embodiments, theinterface component510 facilitates communication between and among the account component520, thepreauthorization component530, theidentification component540, thedetection component550, thedispenser component560, and/or themodification component570.
• The account component520 enables thecomputing system500 to manage data associated with one or more accounts (e.g., cardholder account320). Account data stored and/or maintained at or by thecomputing system500 may include data registered with thecomputing system500, such ascredential data322,contact data344, and/orpreference data346. In some embodiments, the account component520 usescredential data322 to selectively allow one or more users (e.g., user202) to access and use account data associated with thecardholder account320. For example, thecredential data322 may be used to authenticate theuser202 as being an authorized user of thecardholder account320. In some embodiments, the account component520 usescontact data344 to communicate with one or more other computing systems associated with the cardholder account320 (e.g., user device210). For example, contact data may be used to locate and/or approach a user device210 for communicating with a user of the user device210 (e.g., user202).
• The account component520 is configured to process one or more registration requests to register data with thecomputing system500. Various identifiers (e.g., biometric identifier, device identifier, card identifier), for example, may be registered with thecomputing system500 to associate auser202, a user device210, and/or anaccess card310 with thecardholder account320. For another example, user preferences may be registered with thecomputing system500 to enroll an entity (e.g.,user202, user device210, access card310) and/or an account (e.g., cardholder account320) in a nonvisual communication program. The account component520 is configured to register data with thecomputing system500 such that theinterface component510, account component520, thepreauthorization component530, theidentification component540, thedetection component550, thedispenser component560, and/or themodification component570 may access and/or use the data in an efficient manner.
• Thepreauthorization component530 enables thecomputing system500 to identify a preauthorized financial transaction and an account associated with the preauthorized financial transaction. Thepreauthorization component530 is configured to communicate (e.g., via the interface component510) with another computing system (e.g., user device210,cashier system220,merchant device230,system server240, cash machine250) to obtain a message associated with a financial transaction, such as a request for preauthorization and/or a preauthorization message (e.g., machine instruction352). A message may indicate that the financial transaction is associated with a nonvisual communication program. In some embodiments, thepreauthorization component530 identifies atransaction amount314 and an account associated with the financial transaction (e.g., cardholder account320).
• Theidentification component540 enables thecomputing system500 to identify one or more parameters associated with a preauthorized financial transaction. Theidentification component540 is configured to communicate with the account component520 (e.g., via the interface component510) to access thecardholder account320 to identify account data (e.g.,credential data322,contact data344, preference data346) registered with thecomputing system500. In some embodiments, theidentification component540 identifies atransaction timeframe332 in which preauthorized funds may be captured and/or one ormore cash machines250 at which the preauthorized funds may be captured. Thetransaction timeframe332 and/orcash machines250 may be identified and/or determined based ontime data336,machine location data338 and/or user location data340.
• For example, a current location (e.g., based on user location data340), a destination (e.g., based on machine location data338), and a travel rate for traversing a distance between a geolocation of theuser202 and a geolocation of thecash machine250 may be used to determine thetransaction timeframe332. For another example, a current location (e.g., based on user location data340), a travel time (e.g., based on time data336), and a travel rate may be used to determine an area around a geolocation of theuser202 that is traversable within the amount of time associated with thetime data336. The area may be analyzed to identify one ormore cash machines250 physically located in the area. If a plurality ofcash machines250 are identified, a plurality ofmachine identifiers334 associated with the identifiedcash machines250 may be transmitted to a user device210 for prompting theuser202 to select or identify, from the plurality ofcash machines250, a set ofcash machines250 at which the preauthorized funds may be captured.
• Thedetection component550 enables thecomputing system500 to authenticate a user proximate to thecash machine250 as an authorized user of an account (e.g., cardholder account320). In some embodiments, thedetection component550 determines whether a cardholder (e.g., user202) of an account associated with a preauthorized financial transaction (e.g., cardholder account320) is proximate to thecash machine250. Upon determining that theuser202 is proximate to thecash machine250, thedetection component550 identifies acapture time362 associated with the preauthorized financial transaction, and determines whether thecapture time362 satisfies thetransaction timeframe332.
• For example, a transmission may be detected and analyzed to determine whether a source of the transmission (e.g., user device210, access card310) is associated with thecardholder account320. The transmission may include or indicate an identifier associated with the source (e.g., device identifier, card identifier). Additionally or alternatively, scan data associated with one or more objects detected in a predetermined scan area may be analyzed to identify one or more identifiers (e.g., biometric identifier, device identifier, card identifier). Thedetection component550 compares one or more identifiers with account data registered with the computing system500 (e.g.,credential data322, contact data344). If an identifier matches or corresponds tocredential data322 and/orcontact data344, theuser202 is determined to be proximate to thecash machine250.
• For another example,position data342 associated with a user device210 and/oraccess card310 associated with thecardholder account320 is obtained. Contactdata344 registered with thecomputing system500, for example, may be used to identify the user device210 and/oraccess card310 and communicate with the user device210 and/oraccess card310 for obtaining theposition data342. Thedetection component550 analyzes theposition data342 to determine whether theuser202 is proximate to thecash machine250. If a geolocation associated with the position data342 (e.g., a device location) is proximate to a geolocation associated with the cash machine250 (e.g., a machine location), theuser202 is determined to be proximate to thecash machine250.
• Thedispenser component560 enables thecomputing system500 to dispense cash in accordance with the nonvisual communication program. In some embodiments, thedispenser component560 obtains adenomination breakdown372 corresponding to atransaction amount314, and dispenses thetransaction amount314 of cash in accordance with thedenomination breakdown372. In some embodiments, thedispenser component560 dispenses cash in a predetermined order, grouping, cadence, or timing of denominations that allows theuser202 to confirm or verify that thetransaction amount314 of cash was dispensed. Upon dispensing thetransaction amount314 of cash, thedispenser component560 generates anotification374 that is indicative of thetransaction amount314 of cash being dispensed.
• Themodification component570 enables thecomputing system500 to modify thetransaction timeframe332 in which the preauthorized financial transaction may be carried out and/or identify anothercash machine250 at which the preauthorized financial transaction may be carried out. In some embodiments, themodification component570 determines whether ahold duration376 associated with the preauthorized financial transaction exceeds apredetermined hold threshold378. If thehold duration376 exceeds thepredetermined hold threshold378, themodification component570 generates a request to modify thetransaction timeframe332 and/or identify anothercash machine250.
• FIG. 6 is a sequence diagram illustrating anexample method600 for processing a preauthorized financial transaction in theecosystem200. In some embodiments, a user device210 transmits at602 account information and atransaction amount314 to amerchant device230. Themerchant device230 uses the account information and thetransaction amount314 to generate at605 a request for preauthorization. The request for preauthorization is transmitted at606 to asystem server240 for processing.
• Upon receiving the request for preauthorization, thesystem server240 identifies at610 acardholder account320 used to enter into the financial transaction. The request for preauthorization may be analyzed to determine whether to approve the request for preauthorization. If the request for preauthorization is approved, thesystem server240 determines at615 atransaction timeframe332 in which the financial transaction may be carried out and one ormore cash machines250 at which the preauthorized funds may be captured.
• In some embodiments, thesystem server240 identifies at620 that thecardholder account320 is enrolled in a nonvisual communication program. Upon identifying that thecardholder account320 is enrolled in the nonvisual communication program, thesystem server240 generates at625 amachine instruction352 and a user instruction354 in accordance with the nonvisual communication program, and transmits at626 a response to the request for preauthorization, including themachine instruction352 and the user instruction354, to themerchant device230. Alternatively, themerchant device230 may identify that thecardholder account320 is enrolled in the nonvisual communication program, and generate themachine instruction352 and/or the user instruction354 in accordance with the nonvisual communication program.
• Themerchant device230 transmits at628 themachine instruction352 to acash machine250, and transmits at629 the user instruction354 to the user device210. Alternatively, thesystem server240 may transmit themachine instruction352 directly to thecash machine250, and/or transmit the user instruction354 directly to the user device210. The user device210 presents at630 the user instruction354 to a user of the user device210 (e.g., user202) to enable the user to carry out the financial transaction. In some embodiments, the user instruction354 is transmitted to a user device210 associated with thecardholder account320 other than the user device210 used to enter into the financial transaction (e.g., a mobile device) for presentation.
• Upon receiving themachine instruction352, thecash machine250 is configured to carry out the financial transaction in accordance with the nonvisual communication program. Thecash machine250 identifies at640 acapture time362 that is indicative of theuser202 being proximate to thecash machine250, and dispenses at645 cash to theuser202. The cash may be dispensed, for example, in accordance with adenomination breakdown372. Upon dispensing the cash, thecash machine250 generates at650 anotification374 associated with the dispensed cash, and transmits at652 thenotification374 to themerchant device230. Themerchant device230 transmits at654 thenotification374 to thesystem server240 to enable thesystem server240 to identify that the financial transaction is carried out. In some embodiments, thecash machine250 transmits thenotification374 directly to thesystem server240.
• FIG. 7 is a flow diagram illustrating anexample dataflow700 for preauthorizing a financial transaction and carrying out the preauthorized financial transaction in theecosystem200. Thedataflow700 includes apreauthorization phase710, in which a request for preauthorization of a financial transaction is processed, and arealization phase720, in which a preauthorized financial transaction is carried out.
• During thepreauthorization phase710, auser202 may use a client-side application730 (e.g., at a user device210) to preauthorize an automated banking machine-related financial transaction. The client-side application730 may be used, for example, to provide acardholder identifier312 and atransaction amount314 for generating a request for preauthorization. A server-side application740 (e.g., at themerchant device230, at the system server240) obtains thecardholder identifier312 and thetransaction amount314 from the client-side application730, and identifies acardholder account320 associated with thecardholder identifier312 for processing the financial transaction.Credential data322 may be obtained from amemory area750, and compared with thecardholder identifier312 to identify thecardholder account320.
• The server-side application740 determines atransaction timeframe332 in which the financial transaction may be carried out and one ormore cash machines250 at which preauthorized funds may be captured based ontime data336,machine location data338, and/or user location data340. Thetime data336,machine location data338, and/or user location data340 may be identified and/or generated at the server-side application740. For example, the request for preauthorization may be analyzed to extract or identifytime data336,machine location data338, and/or user location data340. For another example,position data342 may be obtained from the client-side application730 to identify a geolocation of auser202 associated with thecardholder account320 for generating user location data340. For yet another example,machine location data338 may be obtained from one or more thin client applications (e.g., at one or more cash machines250) to identify one or more geolocations of thecash machines250 for generatingmachine location data338. For yet another example,preference data346 may be obtained from thememory area750 to identify, generate, and/or modifytime data336,machine location data338, and/or user location data340.
• The server-side application740 determines whether thecardholder account320 is enrolled in a nonvisual communication program.Preference data346 associated with thecardholder account320, for example, may be used to determine an enrollment status. If thecardholder account320 is enrolled in the nonvisual communication program, the server-side application740 generates amachine instruction352 and a user instruction354 in accordance with the nonvisual communication program.
• Themachine instruction352 enables thethin client application760 to perform one or more operations for carrying out the financial transaction. The user instruction354 enables the client-side application730 to instruct a user of the client-side application730 (e.g., the user202) to perform one or more operations for carrying out the financial transaction. For example, theuser202 may approach acash machine250 identified in the user instruction354 within thetransaction timeframe332 to capture the preauthorized funds at thecash machine250.
• Thedataflow700 enters therealization phase720 when acapture time362 is identified. Thethin client application760 may identify thecapture time362 upon identifying auser202 proximate to thecash machine250. Identifying auser202, or an object associated with theuser202, at thethin client application760, for example, may be indicative of theuser202 being proximate to thecash machine250. In some embodiments, thethin client application760 communicates with the client-side application730 to authenticate theuser202. If thecapture time362 satisfies thetransaction timeframe332, cash is dispensed at thecash machine250 in accordance with the nonvisual communication program. Upon identifying that the cash has been dispensed, thethin client application760 generates anotification374 associated with the cash being dispensed. Thenotification374 may be obtained, for example, at the server-side application740.
• FIG. 8 is a block diagram illustrating anexample operating environment800 that may be used to process one or more financial transactions. The operatingenvironment800 is only one example of a computing and networking environment and is not intended to suggest any limitation as to the scope of use or functionality of the disclosure. The operatingenvironment800 should not be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in theexample operating environment800.
• The disclosure is operational with numerous other computing and networking environments or configurations. While some embodiments of the disclosure are illustrated and described herein with reference to the operatingenvironment800 being or including a merchant device230 (shown inFIG. 2), a system server240 (shown inFIG. 2), a computing system500 (shown inFIG. 5), and/or a server-side application740 (shown inFIG. 7), aspects of the disclosure are operable with any computing system (e.g., user device210,cashier system220,cash machine250, access card310) that executes instructions to implement the operations and functionality associated with the operatingenvironment800.
• For example, the operatingenvironment800 may include a mobile device, a tablet, a laptop computer, a desktop computer, a server computer, a microprocessor-based system, a multiprocessor system, a communication devices in a wearable or accessory form factor (e.g., a watch, glasses, a headset, earphones, and the like), programmable consumer electronics, a portable media player, a gaming console, a set top box, a kiosk, a tabletop device, an industrial control device, a minicomputer, a mainframe computer, a network computer, a distributed computing environment that includes any of the above systems or devices, and the like. The operatingenvironment800 may represent a group of processing units or other computing systems. Additionally, any computing system described herein may be configured to perform any operation described herein including one or more operations described herein as being performed by another computing system.
• With reference toFIG. 8, an example system for implementing various aspects of the disclosure may include a general purpose computing system in the form of acomputer810. Components of thecomputer810 may include, but are not limited to, a processing unit820 (e.g., a processor), a system memory825 (e.g., a computer-readable storage device), and asystem bus830 that couples various system components including thesystem memory825 to theprocessing unit820. Thesystem bus830 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.
• Thesystem memory825 includes any quantity of media associated with or accessible by theprocessing unit820. For example, thesystem memory825 may include computer storage media in the form of volatile and/or nonvolatile memory, such as read only memory (ROM)831 and random access memory (RAM)832. TheROM831 may store a basic input/output system (BIOS)833 that facilitates transferring information between elements withincomputer810, such as during start-up. TheRAM832 may contain data and/or program modules that are immediately accessible to and/or presently being operated on by processingunit820. For example, thesystem memory825 may store computer-executable instructions, application data, transaction data, identifier data, profile data, time data, location data, and other data. By way of example, and not limitation,FIG. 8 illustratesoperating system834,application programs835,other program modules836, andprogram data837.
• Thecomputer810 includes a variety of computer-readable media. Computer-readable media may be any available media that may be accessed by thecomputer810 and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media are tangible and mutually exclusive to communication media.
• Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology, such as semiconductor, magnetic, or optical technologies, for storage of information, such as computer-executable instructions, data structures, program modules or other data. Example computer storage media includes, but is not limited to,ROM831,RAM832, electrically erasable programmable read-only memory (EEPROM), solid-state memory, flash memory, a hard disk, magnetic storage, floppy disk, magnetic tape, a compact disc (CD), a digital versatile disc (DVD), a BLU-RAY DISC® brand optical disc, an ultra density optical (UDO) disc, or any other medium which may be used to store the desired information and which may be accessed by thecomputer810. (BLU-RAY DISC® is a registered trademark of Blu-ray Disc Association located in Burbank, Calif.). Computer storage media are implemented in hardware and exclude carrier waves and propagated signals. Computer storage media for purposes of this disclosure are not signals per se.
• Communication media typically embodies computer-executable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
• By way of example only,FIG. 8 illustrates ahard disk drive841 that reads from or writes to non-removable, nonvolatile magnetic media, a universal serial bus (USB)port842 that provides for reads from or writes to a removable,nonvolatile memory843, and anoptical disk drive844 that reads from or writes to a removable, nonvolatileoptical disk845. Other removable/non-removable, volatile/nonvolatile computer storage media that may be used in the example operating environment include, but are not limited to, solid state memory, flash memory, and the like. Thehard disk drive841 may be connected to thesystem bus830 through a non-removable memory interface such asinterface846, andmagnetic disk drive842 andoptical disk drive844 may be connected to thesystem bus830 by a removable memory interface, such asinterface847.
• The drives and their associated computer storage media, described above and illustrated inFIG. 8, provide storage of computer-executable instructions, data structures, program modules, applications, components (e.g.,interface component510, account component520,preauthorization component530,identification component540,detection component550,dispenser component560, modification component570), and other data for thecomputer810. InFIG. 8, for example,hard disk drive841 is illustrated as storingoperating system854,application programs855,other program modules856 andprogram data857. Note that these components may either be the same as or different fromoperating system834,application programs835,other program modules836, andprogram data837.Operating system854,application programs855,other program modules856, andprogram data857 are given different numbers herein to illustrate that, at a minimum, they are different copies.
• Theprocessing unit820 includes any quantity of processing units, and the instructions may be performed by theprocessing unit820 or by multiple processors within the operatingenvironment800 or performed by a processor external to the operatingenvironment800. Theprocessing unit820 may be programmed to execute the computer-executable instructions for implementing aspects of the disclosure, such as those illustrated in the figures (e.g.,FIGS. 4, 6, and 7). For example, theprocessing unit820 may execute an interface component510 (shown inFIG. 5), an account component520 (shown inFIG. 5), a preauthorization component530 (shown inFIG. 5), an identification component540 (shown inFIG. 5), a detection component550 (shown inFIG. 5), a dispenser component560 (shown inFIG. 5), and/or a modification component570 (shown inFIG. 5) for implementing aspects of the disclosure.
• Upon programming or execution of these components, the operatingenvironment800 and/orprocessing unit820 is transformed into a special purpose microprocessor or machine. For example, thepreauthorization component530, when executed by theprocessing unit820, causes thecomputer810 to obtain a preauthorization message associated with a financial transaction, and analyze the preauthorization message to identify a transaction amount and a cardholder account associated with the financial transaction; thedetection component550, when executed by theprocessing unit820, causes thecomputer810 to determine that a cardholder associated with the cardholder account is proximate to a cash machine, identify a capture time associated with the financial transaction, and determine whether the capture time satisfies the transaction timeframe; and thedispenser component560, when executed by theprocessing unit820, causes thecomputer810 to dispense the transaction amount of cash in accordance with a nonvisual communication program. Although theprocessing unit820 is shown separate from thesystem memory825, embodiments of the disclosure contemplate that thesystem memory825 may be onboard theprocessing unit820 such as in some embedded systems.
• A user may enter commands and information into thecomputer810 through one or more input devices, such as a pointing device861 (e.g., mouse, trackball, touch pad), akeyboard862, a microphone863, and/or an electronic digitizer864 (e.g., on a touchscreen). Other input devices not shown inFIG. 8 may include a joystick, a game pad, a controller, a satellite dish, a camera, a scanner, an accelerometer, or the like. Thecomputer810 may accept input from the user in any way, including from input devices, via gesture input, via proximity input (such as by hovering), and/or via voice input. These and other input devices may be coupled to theprocessing unit820 through auser input interface865 that is coupled to thesystem bus830, but may be connected by other interface and bus structures, such as a parallel port, game port or theUSB port842.
• Information, such as text, images, audio, video, graphics, alerts, and the like, may be presented to a user via one or more presentation devices, such as amonitor866, aprinter867, and/or aspeaker868. Other presentation devices not shown inFIG. 8 may include a projector, a vibrating component, or the like. These and other presentation devices may be coupled to theprocessing unit820 through a video interface869 (e.g., for amonitor866 or a projector) and/or an output peripheral interface870 (e.g., for aprinter867, aspeaker868, and/or a vibration component) that are coupled to thesystem bus830, but may be connected by other interface and bus structures, such as a parallel port, game port or theUSB port842. In some embodiments, the presentation device is integrated with an input device configured to receive information from the user (e.g., a capacitive touch-screen panel, a controller including a vibrating component). Note that themonitor866 and/or touch screen panel may be physically coupled to a housing in which thecomputer810 is incorporated, such as in a tablet-type personal computer.
• Thecomputer810 may operate in a networked environment using logical connections to one or more remote computers, such as aremote computer880. Theremote computer880 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to thecomputer810, although only amemory storage device881 has been illustrated inFIG. 8. The logical connections depicted inFIG. 8 include one ormore LANs882 and one ormore WANs883, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
• When used in a LAN networking environment, thecomputer810 is coupled to theLAN882 through a network interface oradapter884. When used in a WAN networking environment, thecomputer810 may include amodem885 or other means for establishing communications over theWAN883, such as the Internet. Themodem885, which may be internal or external, may be connected to thesystem bus830 via theuser input interface865 or other appropriate mechanism. A wireless networking component including an interface and antenna may be coupled through a device, such as an access point or peer computer to aLAN882 orWAN883. In a networked environment, program modules depicted relative to thecomputer810, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,FIG. 8 illustratesremote application programs886 as residing onmemory storage device881. It may be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers may be used.
• The block diagram ofFIG. 8 is merely illustrative of an example system that may be used in connection with one or more examples of the disclosure and is not intended to be limiting in any way. Further, peripherals or components of the computing systems known in the art are not shown, but are operable with aspects of the disclosure. At least a portion of the functionality of the various elements inFIG. 8 may be performed by other elements inFIG. 8, or an entity (e.g., processor, web service, applications, server, computing system, etc.) not shown inFIG. 8.
• Although described in connection with an example computing system environment, embodiments of the disclosure are capable of implementation with numerous other general purpose or special purpose computing system environments, configurations, or devices. Embodiments of well-known computing systems, environments, and/or configurations that may be suitable for use with aspects of the disclosure include, but are not limited to, mobile devices, tablets laptop computers, desktop computers, server computers, microprocessor-based systems, multiprocessor systems, programmable consumer electronics, communication devices in wearable or accessory form factors, portable media players, gaming consoles, set top boxes, kiosks, tabletop devices, industrial control devices, minicomputers, mainframe computers, network computers, distributed computing environments that include any of the above systems or devices, and the like.
• Embodiments of the disclosure may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices in software, firmware, hardware, or a combination thereof. The computer-executable instructions may be organized into one or more computer-executable components or modules. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Aspects of the disclosure may be implemented with any number and organization of such components or modules. For example, aspects of the disclosure are not limited to the specific computer-executable instructions or the specific components or modules illustrated in the figures and described herein. Other embodiments of the disclosure may include different computer-executable instructions or components having more or less functionality than illustrated and described herein.
• In some embodiments, the operations illustrated in the drawings may be implemented as software instructions encoded on a computer readable medium, in hardware programmed or designed to perform the operations, or both. For example, aspects of the disclosure may be implemented as a system on a chip or other circuitry including a plurality of interconnected, electrically conductive elements.
• The order of execution or performance of the operations in embodiments of the disclosure illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and embodiments of the disclosure may include additional or fewer operations than those disclosed herein. For example, it is contemplated that executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of aspects of the disclosure.
• The embodiments illustrated and described herein as well as embodiments not specifically described herein but within the scope of aspects of the disclosure constitute example means for obtaining permission using nonvisual communication to authorize one or more transactions. For example, the elements illustrated inFIGS. 1-3, 5, and 8, such as when encoded to perform the operations illustrated inFIGS. 4, 6, and 7, constitute at least an example means for identifying a request for preauthorization of a financial transaction (e.g., preauthorization component530); an example means for determining a transaction timeframe associated with a financial transaction (e.g., identification component540); an example means for identifying a cash machine associated with a financial transaction (e.g., identification component540); an example means for determining whether to process a financial transaction in accordance with a nonvisual communication program (e.g., preauthorization component530); and an example means for generating a preauthorization instruction to dispense the transaction amount of cash in accordance with a nonvisual communication program (e.g., preauthorization component530).
• When introducing elements of aspects of the disclosure or the embodiments thereof, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. Furthermore, references to an “embodiment” or “example” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments or examples that also incorporate the recited features. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements. The phrase “one or more of the following: A, B, and C” means “at least one of A and/or at least one of B and/or at least one of C.”
• Having described aspects of the disclosure in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the disclosure as defined in the appended claims. As various changes could be made in the above constructions, products, and methods without departing from the scope of aspects of the disclosure, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.
• While the aspects of the disclosure have been described in terms of various embodiments with their associated operations, a person skilled in the art would appreciate that a combination of operations from any number of different embodiments is also within the scope of the aspects of the disclosure.

Claims (20)

What is claimed is:

1. A computing system for preauthorizing one or more financial transactions, the computing system comprising:

a memory device storing data associated with one or more cardholder accounts and computer-executable instructions; and

a processor configured to execute the computer-executable instructions to:

receive, from a cashier system, a request for preauthorization of a first financial transaction of the one or more financial transactions, the request for preauthorization including a transaction amount and a cardholder identifier;

based on the cardholder identifier, identify a first cardholder account of the one or more cardholder accounts;

determine a transaction timeframe and one or more machine identifiers associated with the first financial transaction;

access the first cardholder account to determine whether to process the first financial transaction in accordance with a nonvisual communication program; and

on condition that the first financial transaction is to be processed in accordance with the nonvisual communication program, generate an instruction to identify a capture time associated with the first financial transaction, determine whether the capture time satisfies the transaction timeframe, and, on condition that the capture time satisfies the transaction timeframe, dispense the transaction amount of cash in accordance with the nonvisual communication program.

2. The computing system ofclaim 1, wherein the processor is further configured to execute the computer-executable instructions to:

transmit, to the cashier system, the instruction such that one or more cash machines are configured to dispense the transaction amount of cash in accordance with the nonvisual communication program, the one or more cash machines associated with the one or more machine identifiers; and

receive, from the cashier system, a notification indicative of the transaction amount of cash being dispensed.

3. The computing system ofclaim 1, wherein the processor is further configured to execute the computer-executable instructions to:

identify user location data and time data associated with the first financial transaction; and

analyze the user location data and the time data to identify one or more cash machines, the one or more cash machines associated with the one or more machine identifiers.

4. The computing system ofclaim 1, wherein the processor is further configured to execute the computer-executable instructions to:

identify user location data and machine location data associated with the financial transaction, the machine location data associated with the one or more machine identifiers; and

analyze the user location data and the machine location data to identify the transaction timeframe.

5. The computing system ofclaim 1, wherein the processor is further configured to execute the computer-executable instructions to:

identify a plurality of cash machines;

generate a prompt to select, from the plurality of cash machines, a set of cash machines; and

receive user input associated with a selection of the set of cash machines, the selection of the set of cash machines associated with the one or more machine identifiers.

6. The computing system ofclaim 1, wherein the processor is further configured to execute the computer-executable instructions to:

receive a denomination breakdown corresponding to the transaction amount; and

generate the instruction to dispense the transaction amount of cash in accordance with the denomination breakdown.

7. The computing system ofclaim 1, wherein the processor is further configured to execute the computer-executable instructions to:

determine whether a hold duration associated with the first financial transaction exceeds a hold threshold;

on condition that the hold duration exceeds the hold threshold, transmit one or more of a request to modify the transaction timeframe or a request to identify another cash machine.

8. One or more computer storage media embodied with computer-executable instructions, the one or more computer storage media comprising:

a preauthorization component that, upon execution by at least one processor, obtains a preauthorization message associated with a financial transaction, and analyzes the preauthorization message to identify a transaction amount and a cardholder account associated with the financial transaction;

a detection component that, upon execution by the at least one processor, determines that a cardholder associated with the cardholder account is proximate to a cash machine, identifies a capture time associated with the financial transaction, and determines whether the capture time satisfies the transaction timeframe; and

a dispenser component that, upon execution by the at least one processor, dispenses the transaction amount of cash in accordance with a nonvisual communication program.

9. The one or more computer storage media ofclaim 8, wherein the detection component is configured to:

obtain position data associated with one or more of a user device associated with the cardholder account or an access card associated with the cardholder account; and

analyze the position data to determine whether the one or more of the user device or the access card are proximate to the cash machine, the cardholder determined to be proximate to the cash machine on condition that the one or more of the user device or the access card are proximate to the cash machine.

10. The one or more computer storage media ofclaim 8, wherein the detection component is configured to:

detect a transmission associated with one or more of a user device or an access card, the user device associated with a device identifier, the access card associated with a card identifier; and

compare one or more of the device identifier or the card identifier with account data registered with the cardholder account to determine whether the one or more of the user device or the access card are associated with the cardholder account, the cardholder determined to be proximate to the cash machine on condition that the one or more of the user device or the access card are associated with the cardholder account.

11. The one or more computer storage media ofclaim 8, wherein the detection component is configured to:

detect an object within a predetermined scan area;

scan the predetermined scan area to generate scan data;

analyze the scan data to identify one or more of a biometric identifier associated with a user, a device identifier associated with a user device, or a card identifier associated with an access card; and

compare one or more of the biometric identifier, the device identifier, or the card identifier with account data registered with the cardholder account to determine whether the object is associated with the cardholder account, the cardholder determined to be proximate to the cash machine on condition that the object is associated with the cardholder account.

12. The one or more computer storage media ofclaim 8, wherein the dispenser account is configured to generate a notification indicative of the transaction amount of cash being dispensed.

13. The one or more computer storage media ofclaim 8, wherein the dispenser component is configured to:

obtain a denomination breakdown corresponding to the transaction amount; and

dispense the transaction amount of cash in accordance with the denomination breakdown.

14. The one or more computer storage media ofclaim 8 further comprising a modification component configured to:

determine whether a hold duration associated with the financial transaction exceeds a hold threshold; and

on condition that the hold duration exceeds the hold threshold, generate one or more of a request to modify the transaction timeframe or a request to identify another cash machine.

15. A computer-implemented method for preauthorizing one or more financial transactions, the computer-implemented method comprising:

identifying a request for preauthorization of a first financial transaction of the one or more financial transactions, the request for preauthorization including a transaction amount and a cardholder identifier;

determining a transaction timeframe associated with the first financial transaction;

identifying one or more cash machines associated with the first financial transaction;

using the cardholder identifier to determine whether to process the first financial transaction in accordance with a nonvisual communication program; and

on condition that the first financial transaction is to be processed in accordance with the nonvisual communication program, generating a preauthorization instruction to dispense the transaction amount of cash in accordance with the nonvisual communication program upon determining that a capture time associated with the first financial transaction satisfies the transaction timeframe.

16. The computer-implemented method ofclaim 15, further comprising:

identifying position data associated with a geolocation of a user device;

identifying time data associated with an amount of time; and

analyzing the position data and the time data to identify the one or more cash machines.

17. The computer-implemented method ofclaim 15, further comprising:

identifying position data associated with a device location of a user device;

identifying location data associated with one or more machine locations of the one or more cash machines; and

analyzing the position data and the location data to identify the transaction timeframe.

18. The computer-implemented method ofclaim 15, further comprising:

identifying a plurality of cash machines;

prompting a user of the user device to select, from the plurality of cash machines, a set of cash machines; and

receiving user input associated with the selected set of cash machines, wherein the one or more cash machines are identified based on the selected set of cash machines.

19. The computer-implemented method ofclaim 15, further comprising receiving a denomination breakdown corresponding to the transaction amount, wherein the instruction is generated based on the denomination breakdown.

20. The computer-implemented method ofclaim 15, further comprising:

determining whether a hold duration associated with the first financial transaction exceeds a hold threshold; and

on condition that the hold duration exceeds the hold threshold, transmitting one or more of a request to modify the transaction timeframe or a request to identify another cash machine.

Images