Patent Application
20190147506
Many business entities (e.g., financial institutions, retailers, restaurants, department stores, grocery stores, and/or the like) own and/or operate multiple service locations (which may be referred to as branches). In many instances, different service locations may offer and/or provide the same or different services. In some instances, some services may be provided by affiliates of the business entities (e.g., third party service providers, vendors, and/or the like).
According to some implementations, a device may include one or more processors to receive information associated with one or more service resources that provide a service at a service location, at least one of the one or more service resources including a machine that is capable of automatically providing the service; monitor availability of the one or more service resources at the service location based on the information; provide status information, associated with the availability of the one or more service resources, to a user device to enable the user device to present the status information on a display, the status information indicating an availability for the user to receive the service at the service location based on a usage of the one or more service resources at the service location; receive a request for the service from the user device, the user device being associated with a user account registered with an entity that operates the service location; allocate a service resource of the one or more service resources at the service location to provide the service based on the request and a characteristic of the user account; detect an interaction between the user device and the allocated service resource at the service location; and/or automatically cause a transaction for the service to be processed using payment from a payment account associated with the user account based on detecting the interaction.
According to some implementations, a non-transitory computer-readable medium may store one or more instructions that, when executed by one or more processors, may cause the one or more processors to: receive information associated with a service offered at a service location, the information indicating an availability of one or more transaction terminals associated with providing the service at the service location; monitor an availability of the service at the service location based on the information; provide status information associated with the availability of the service to a user device, the status information indicating the availability of the service at the service location based on a usage of the one or more transaction terminals associated with providing the service at the service location; receive a request for the service from the user device, the user device being associated with a user account registered with an entity that operates the service location; allocate a transaction terminal of the one or more transaction terminals at the service location to provide the service based on the request and the user account; determine that an interaction occurred between the user device and the transaction terminal at the service location; and/or cause a transaction for the service to be processed using payment from a payment account associated with the user account associated with the user device based on determining that the user device interacted with the transaction terminal.
According to some implementations, a method may include receiving, by a server device, first information associated with a first set of services that are offered at a first service location and second information associated with a second set of services that are offered at a second service location, the first service location and the second service location being operated by an entity that provides the first set of services and the second set of services; monitoring, by the server device, first availability of the first set of services based on the first information and second availability of the second set of services based on the second information; transmitting, from the server device to a user device, first status information associated with respective statuses of one or more of the first set of services and second status information associated with respective statuses of one or more of the second set of services, the first status information being indicative of the first availability based on a usage of transaction terminals at the first service location for providing the first set of services and the second status information being indicative of the second availability based on a usage of transaction terminals at the second service location for providing the second set of services; receiving, by the server device and from the user device, a request that a first service of the first set of services be provided at the first service location; allocating, by the server device, a first transaction terminal of the transaction terminals at the first service location to provide the first service based on the request; detecting, by the server device, an interaction between the user device and the first transaction terminal at the first service location; and/or processing, by the server device, a transaction for the first service using a user account associated with the user device based on detecting the interaction.
The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
Service locations of a service provider (e.g., a business entity) may offer a variety of services that may vary from service location to service location. Accordingly, for a consumer of the entity to identify which services are offered at the service locations, the consumer may need to research (e.g., via a web search, contacting the individual service locations, etc.) which service locations provide a desired service. Furthermore, if the consumer wishes to receive such a service, the consumer may need to contact the service locations separately to make appointments for the service, and pay for the service via an in-person transaction.
Some implementations, described herein, provide a branch manager platform, for a service provider, that identifies or indicates offered services at service locations of the service provider, determines availabilities of the offered services, reserves resources (e.g., by scheduling appointments) that provide or facilitate providing the services, and/or processes a transaction for the service. Accordingly, consumers and/or user devices of consumers may utilize the branch manager platform to identify offered services, determine availabilities of the offered services, reserve resources for the offered services, and/or engage in transactions for the offered services.
According to some implementations, a branch manager platform may monitor availability of service resources (e.g., transaction terminals) that provide services at service locations of an entity, provide status information associated with the services resources to user devices, allocate resources based on requests for services from the user devices, and cause transactions to be processed based on interactions between the user devices and the service resources at the service locations. As a specific example, a branch manager platform may determine whether electric vehicle (EV) charging is available at service locations of an entity (which may not be considered a service provider of EV charging), monitor the usage of EV charging stations at the service locations of the entity, enable reservation of the EV charging stations (e.g., based on a membership status or other characteristics of an account of a consumer), and/or enable payment for EV charging (e.g., using payment from a payment account of the consumer that is associated with the entity).
As such, some implementations herein may conserve a variety of computing resources, network resources, and/or power resources for a consumer and/or business entity. For example, some implementations herein may avoid wasting computing resources used in searching for services (e.g., EV charging) at service locations, wasting computing resources to receive the services (e.g., by expending computing or power resources to arrive at a service location where EV charging is unavailable), wasting computing resources to process transactions (e.g., transactions involving external network communication with third party transaction service providers, such as card associations), and/or the like. Furthermore, some implementations herein may allow for controlled access to service resources (e.g., transaction terminals) at a service location, such that a user device may remotely control and/or reserve the service resource at the service location (e.g., by placing the service resource in a reservation mode).
As shown in
As shown in
As shown in
Accordingly, the branch manager platform, in the example implementation 100 of
As indicated above,
User device 210 includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with identifying services, reserving services, and/or engaging in transactions for services according to some implementations described herein. For example, user device 210 may include a communication and/or computing device, such as a mobile phone (e.g., a smart phone, a radiotelephone, etc.), a laptop computer, a tablet computer, a handheld computer, a gaming device, a wearable communication device (e.g., a smart wristwatch, a pair of smart eyeglasses, etc.), or a similar type of device.
Transaction terminal 220 includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with facilitating a transaction (e.g., a point-of-sale (PoS) transaction). Transaction terminal 220 may be a service resource associated with providing a service (e.g., a machine that is capable of automatically providing the service) according to some implementation described herein. For example, transaction terminal 220 may include a communication device and/or computing device capable of receiving data from user device 210 and/or a transaction card and processing a transaction based on the data. In some implementations, transaction terminal 220 may include a desktop computer, a laptop computer, a tablet computer, a handheld computer, a mobile phone (e.g., a smart phone, a radiotelephone, and/or the like), a self-checkout station, a kiosk, and/or the like. Transaction terminal 220 may be owned and/or operated by one or more individuals or businesses engaged in a sale of goods or services (e.g., one or more merchants, vendors, service providers, and/or the like). In some implementations, after an interaction with user device 210, transaction terminal 220 may provide or indicate transaction information associated with a transaction to transaction backend 250 for processing of the transaction.
In some implementations, transaction terminal 220 includes one or more devices to facilitate processing a transaction via user device 210. For example, transaction terminal 220 may include a PoS terminal, a security access terminal, an automated teller machine (ATM) terminal, an EV charging station, a transaction terminal for a walk-up banking account service, a transaction terminal for a drive-thru banking account service, a transaction terminal for a walk-up ATM service, a transaction terminal for a drive-thru ATM service, a transaction terminal for a transaction card service, a transaction terminal for an investment banking service, a transaction terminal for a loan service, and/or the like. Transaction terminal 220 may include one or more input devices and/or output devices to facilitate obtaining transaction data or transaction information from user device 210 and/or a transaction card. Example input devices of transaction terminal 220 may include a number keypad, a touchscreen, a magnetic strip reader, a chip reader, a camera, a scanner (e.g., a barcode scanner, QR code scanner, and/or the like), and/or a radio frequency (RF) signal reader. Example output devices of transaction terminal 220 may include a display device, a speaker, a printer, and/or the like.
Branch manager platform 225 includes one or more devices (e.g., computing resources 235) capable of managing and/or integrating services at service locations of an entity (e.g., an individual or business involved in providing a service). For example, branch manager platform 225 may be capable of monitoring transaction terminals 220, reserving transaction terminals 220, and/or facilitating a transaction via user device 210 and/or transaction terminals 220. In some implementations, branch manager platform 225 may indicate or provide status information associated with services and/or transaction terminals 220 at service locations to user device 210.
Cloud computing environment 230 includes an environment that delivers computing as a service, whereby shared resources, services, etc. may be provided to user device 210, transaction terminals 220, and/or transaction backend 250. Cloud computing environment 230 includes an environment that hosts branch manager platform 225. Cloud computing environment 230 may provide computation, software, data access, storage, and/or other services that do not require end-user knowledge of a physical location and/or configuration of a system and/or a device that delivers the services. As shown, cloud computing environment 230 may include a group of computing resources 235 (which may be referred to herein individually as computing resource 235).
Notably, while implementations described herein describe branch manager platform 225 as being hosted in cloud computing environment 230, in some implementations, branch manager platform 225 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.
Computing resource 235 includes one or more personal computers, workstation computers, server devices, or another type of computation and/or communication device. In some implementations, one or more computing resources 235 may host branch manager platform 225. The cloud resources may include compute instances executing in computing resource 235, storage devices provided in computing resource 235, data transfer devices provided by computing resource 235, etc. In some implementations, computing resource 235 may communicate with other computing resources 235 via wired connections, wireless connections, or a combination of wired and wireless connections.
As further shown in
Application 235-1 includes one or more software applications that may be provided to or accessed by user device 210. Application 235-1 may eliminate a need to install and execute the software applications on user device 210. For example, application 235-1 may include software associated with branch manager platform 225 and/or any other software capable of being provided via cloud computing environment 230. In some implementations, one application 235-1 may send/receive information to/from one or more other applications 235-1, via virtual machine 235-2.
Virtual machine 235-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 235-2 may be either a system virtual machine or a process virtual machine, depending upon use and degree of correspondence to any real machine by virtual machine 235-2. A system virtual machine may provide a complete system platform that supports execution of a complete operating system (“OS”). A process virtual machine may execute a single program, and may support a single process. In some implementations, virtual machine 235-2 may execute on behalf of a user (e.g., user device 210), and may manage infrastructure of cloud computing environment 230, such as data management, synchronization, or long-duration data transfers.
Virtualized storage 235-3 includes one or more storage systems and/or one or more devices that use virtualization techniques within the storage systems or devices of computing resource 235. In some implementations, within the context of a storage system, types of virtualizations may include block virtualization and file virtualization. Block virtualization may refer to abstraction (or separation) of logical storage from physical storage so that the storage system may be accessed without regard to physical storage or heterogeneous structure. The separation may permit administrators of the storage system flexibility in how the administrators manage storage for end users. File virtualization may eliminate dependencies between data accessed at a file level and a location where files are physically stored. This may enable optimization of storage use, server consolidation, and/or performance of non-disruptive file migrations.
Hypervisor 235-4 provides hardware virtualization techniques that allow multiple operating systems (e.g., “guest operating systems”) to execute concurrently on a host computer, such as computing resource 235. Hypervisor 235-4 may present a virtual operating platform to the guest operating systems, and may manage the execution of the guest operating systems. Multiple instances of a variety of operating systems may share virtualized hardware resources.
Network 240 includes one or more wired and/or wireless networks. For example, network 240 may include a cellular network (e.g., a long-term evolution (LTE) network, a code division multiple access (CDMA) network, a 3G network, a 4G network, a 5G network, another type of next generation network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, or the like, and/or a combination of these or other types of networks.
Transaction backend 250 includes one or more devices capable of authorizing and/or facilitating a transaction. For example, transaction backend 250 may include one or more servers and/or computers to store and/or provide information (e.g., authorizations, balances, transaction tokens, security information, account information, and/or the like) associated with processing a transaction via transaction terminal 220.
Transaction backend 250 may include one or more devices associated with financial institutions (e.g., banks, credit unions, and/or the like) and/or transaction card associations that authorize transactions and/or facilitate a transfer of funds or payments between an account of a user of user device 210 and/or a transaction card and an account of an individual or business of transaction terminal 220. For example, transaction backend 250 may include one or more devices of one or more issuing financial institutions associated with a user of user device 210, one or more devices of one or more acquiring financial institutions (or merchant banks) associated with transaction terminal 220, and/or one or more devices associated with one or more card associations (e.g., VISA®, MASTERCARD®, and/or the like) associated with accounts (e.g., credit accounts, debit accounts, and/or the like) associated with user device 210. Accordingly, in response to receiving account information associated with an account associated with a user of user device 210 (e.g., a checking account, a savings account, a membership account, a rewards account, a service-based credit account, and/or the like) from transaction terminal 220, various financial institutions and/or card associations of transaction backend 250 may communicate to authorize the transaction and/or transfer funds between accounts associated with the user of user device 210 and/or transaction terminal 220.
Transaction backend 250 may include one or more devices associated with a rewards program associated with an entity (e.g., a financial institution, a merchant, an EV charging service, and/or the like) providing the service via transaction terminal 220. For example, transaction backend 250 may authorize earning and/or redeeming of rewards (e.g., rewards points associated with receiving the service, cash rewards, client loyalty rewards associated with an entity associated with transaction terminal 220, and/or the like) based on a transaction processed by transaction terminal 220 via user device 210.
The number and arrangement of devices and networks shown in
Bus 310 includes a component that permits communication among the components of device 300. Processor 320 is implemented in hardware, firmware, or a combination of hardware and software. Processor 320 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, processor 320 includes one or more processors capable of being programmed to perform a function. Memory 330 includes a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by processor 320.
Storage component 340 stores information and/or software related to the operation and use of device 300. For example, storage component 340 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and/or a solid state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable medium, along with a corresponding drive.
Input component 350 includes a component that permits device 300 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and/or a microphone). Additionally, or alternatively, input component 350 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and/or an actuator). Output component 360 includes a component that provides output information from device 300 (e.g., a display, a speaker, and/or one or more light-emitting diodes (LEDs)).
Communication interface 370 includes a transceiver-like component (e.g., a transceiver and/or a separate receiver and transmitter) that enables device 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 370 may permit device 300 to receive information from another device and/or provide information to another device. For example, communication interface 370 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.
Device 300 may perform one or more processes described herein. Device 300 may perform these processes based on processor 320 executing software instructions stored by a non-transitory computer-readable medium, such as memory 330 and/or storage component 340. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.
Software instructions may be read into memory 330 and/or storage component 340 from another computer-readable medium or from another device via communication interface 370. When executed, software instructions stored in memory 330 and/or storage component 340 may cause processor 320 to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
The number and arrangement of components shown in
As shown in
According to some implementations, branch manager platform 225 may receive information associated with transaction terminal 220 that provides the service at the service location. In some implementations, the information may indicate an availability of transaction terminal 220 (e.g., whether transaction terminal 220 is operational, powered on, in use, and/or the like). In such cases, transaction terminal 220 may provide the information and/or branch manager platform 225 may obtain the information from transaction terminal 220.
The example service may be a walk-up banking account service (e.g., a face-to-face cashier service), a drive-thru banking account service (e.g., a cashier service accessible by vehicle), a walk-up ATM service, a drive-thru ATM service, a transaction card service (e.g., to request a new transaction card or replace a transaction card of an account, report theft or fraud associated with a transaction card, and/or the like), an investment banking service, or a loan service (e.g., a service that reviews loan applications and/or provides loans to loan applicants).
In some implementations, the service may be one of a plurality of services. In such cases, a plurality of different services may be offered at a service location. For example, a first service of the plurality of services may be an EV charging service and a second service of the plurality of services may be a walk-up banking account service. Additionally, or alternatively, branch manager platform 225 may receive information associated with a plurality of transaction terminals 220 and/or a plurality of service locations. For example, branch manager platform 225 may receive first information associated with a first set of services that are offered at a first service location and second information associated with a second set of services that are offered at a second service location.
In this way, branch manager platform 225 may receive information associated with a service and/or transaction terminal 220 for providing a service to enable branch manager platform 225 to monitor a status of the service and/or one or more service resources.
As further shown in
According to some implementations, when monitoring the status of the service, branch manager platform 225 may monitor an availability of transaction terminal 220 that is to provide the service at the service location. For example, branch manager platform 225 may determine a usage of transaction terminal 220 at the service location based on a total number of transaction terminals 220 capable of providing the service at the service location and a number of transaction terminals 220 that are in use at the service location. In some implementations, branch manager platform 225 may monitor transaction terminals 220 that provide the service at the service location via the information associated with the service.
In some implementations, branch manager platform 225 may monitor multiple services and/or transaction terminals 220 at multiple service locations. Accordingly, branch manager platform 225 may monitor a first availability of a first set of services offered at a first service location and second availability of a second set of services offered at a second service location. As such, branch manager platform 225 may monitor transaction terminals 220 that provide the corresponding first set of services at the first service location and transaction terminals 220 that provide the corresponding second set of services at the second service location.
In some implementations, branch manager platform 225 may monitor a number of people or customers at a particular service location. For example, branch manager platform 225 may use cameras (and corresponding image analysis, biometric analysis, and/or the like) and/or sensors (e.g., temperature sensors, motion sensors, and/or the like) to determine how many customers are located within a service location. In some instances, branch manager platform 225 may monitor wireless signals from user device 210 (another other devices similar to user device 210) to determine a number of people at the service location. For example, the more unique signals detected from user devices, the more people can be presumed to be in the service location. In some implementations, branch manager platform 225 may utilize machine learning to estimate or determine a number of people in a branch based on analytics associated with images from cameras and/or sensor data from sensors located at the service location.
In this way, branch manager platform 225 may monitor a status and/or availability of a service and/or transaction terminal 220 that provides the service at a service location to permit branch manager platform 225 to provide status information indicating the status to user device 210.
As further shown in
According to some implementations, the status information may indicate an availability of the service at the service location based on a usage of transaction terminal 220 associated with providing the service at the service location. The example usage may be current usage (e.g., the usage at the moment user branch manager platform 225 is monitoring the service and/or transaction terminal 220) and/or historical usage of transaction terminal 220. Additionally, or alternatively, the status information may indicate an availability based on demand for the service (e.g., demand in a particular area, at a particular time, and/or the like). In such cases, the demand may be modeled from current usage and/or historical usage at particular locations and/or times (e.g., times of the day, times of the week, times of the year, etc.). In some implementations, branch manager platform 225 generates the status information. For example, branch manager platform 225 may generate the status information to indicate the availability of the service based on a number of transaction terminals 220 in use and a total number of transaction terminals 220 that provide the service.
In some implementations, branch manager platform 225 may provide, to user device 210, status information associated with multiple services and/or associated with multiple corresponding transaction terminals 220 at multiple service locations. For example, branch manager platform 225 may transmit first status information associated with a status of a first service of a first set of services offered at a first location and second status information associated with a status of a second service of a second set of services offered at a second service location. Accordingly, status information for multiple services and/or service locations may be provided to user device 210.
In this way, branch manager platform 225 may provide status information to a user device 210, which may request that a service be provided and/or reserved via branch manager platform 225.
As further shown in
According to some implementations, user device 210 may be associated with a user account registered with an entity that operates the service location and/or that is associated with branch manager platform 225. For example, user device 210 may include an application that enables user device 210 to access and/or register a user account associated with the entity via branch manager platform 225. The example application may be hosted by branch manager platform 225 and/or maintained by the entity. In such instances, user device 210 and/or branch manager platform 225 may maintain the user account associated with the entity. In some implementations, branch manager platform 225 may receive a request from user device 210 to register the user account with the entity and branch manager platform 225 may register the user account with the entity based on a user input received via user device 210. In such cases, the user input may specify a membership type that may be used to allocate transaction terminal 220 and/or determine a transaction amount for the service. Accordingly, a user associated with user device 210 may be associated with the entity via a registered user account with the entity.
According to some implementations, branch manager platform 225 may indicate service locations that offer a particular service and the availability of the service. In some implementations, branch manager platform 225 may indicate a nearest storage location to user device 210 that is available to provide the service. For example, if a service is offered at a nearest service location, but all transaction terminals 220 that provide the service at the nearest service location are in use or are going to be in use at a requested time (i.e., usage is at 100% and the service is unavailable at the requested time), branch manager platform 225 may indicate the next nearest service location that is available to provide the service at the requested time.
In some implementations, the user account may include and/or identify a number of characteristics (which may correspond to the user or the user's status with the entity). For example, the characteristics may include membership information (e.g., a member identification, a member name, an indication of a relationship between the user of user device 210 and the entity, and/or the like) associated with the user account, a balance of funds in a payment account associated with the user account (e.g., which may indicate a tier or status of the user associated with user device 210), a membership type (e.g., a tier (e.g., top tier, low tier, etc.)) associated with the user of user device 210, types of accounts (e.g., checking, banking, investment banking, private banking, etc.) associated with user account, and/or the like. Accordingly, the characteristic of the user account may indicate a status or relationship between the user of user device 210 and the entity that operates branch manager platform 225 and/or the service locations.
According to some implementations, the request may be one of a plurality of requests for multiple services at one or more service locations. For example, the request may include a request that a first service of a first set of services be provided at a first service location and another request that a second service of the first set of services be provided at the first service location. In such cases, the first service and the second service may be provided by a first transaction terminal 220 and a second transaction terminal 220 respectively. Furthermore, the first transaction terminal 220 may be operated by a first entity and the second transaction terminal 220 may be operated by another entity that is different than the first entity. For example, a first entity (e.g., an EV charging service provider) may operating an EV charging station (the first transaction terminal) at the service location and a second entity (e.g., a financial institution, such as a bank) may operate an ATM terminal at the service location (e.g., a branch of the financial institution of the bank). In some implementations, multiple requests may be received such that branch manager platform 225 receives a request that a first service of a first set of services be provided at a first service location and another request that a second service of a second set of services be provided at a second location. In such cases, the second service may not be included in the first set of services available at the first service location (and vice versa).
In some implementations, the request may be any data (e.g., a message, an email, a text, an image, and/or the like) indicating a particular type of service to be provided at a particular service location. Accordingly, based on the specific type of service to be provided and/or service location where the service is to be provided, branch manager platform 225 may identify a corresponding transaction terminal 220 that is available to provide the service.
In this way, branch manager platform 225 may receive a request for a service from user device 210 that permits branch manager platform 225 to allocate transaction terminal 220 to provide the service.
As further shown in
Branch manager platform 225 may allocate transaction terminal 220 to provide a service by reserving or scheduling a time period for transaction terminal 220 to provide the service. For example, branch manager platform 225 may identify a schedule associated with transaction terminal 220 that indicates when transaction terminal 220 is to be in use to provide a service. For example, the schedule may indicate when transaction terminal 220 is available to provide a service, is reserved to provide a service, scheduled to be unavailable (e.g., due to hours of operation for the service location and/or transaction terminal 220), and/or the like. Accordingly, branch manager platform 225 may utilize the schedule when allocating transaction terminal 220 to provide a service by reserving time periods in the schedule when transaction terminal 220 is available to provide the service and/or when user device 210 is available to receive the service (e.g., based on a calendar or schedule of user device 210).
According to some implementations, branch manager platform 225 may determine a characteristic of a user account associated with user device 210 and an entity of the service location. For example, branch manager platform 225 may determine a priority associated with providing the service based on the characteristic and allocate transaction terminal 220 based on the priority associated with providing the service. For example, branch manager platform 225 may determine membership information (e.g., whether user device 210 is associated with an entity of transaction terminal 220), payment account information (e.g., information indicating a balance of funds in the payment account), and/or a membership type (e.g., a top tier membership, a low-tier membership, and/or the like) associated with an account of user device 210, and allocate transaction terminal 220 based on the membership information, payment account information, and/or membership type. Accordingly, the characteristic of the user account may be used to allocate transaction terminal 220 to provide a service based on the request of user device 210.
In some implementations, when branch manager platform 225 determines the characteristic indicates that user device 210 is associated with a member of the entity, then user device 210 may receive priority for reserving transaction terminal 220 over other user devices 210 that are not associated with members of the entity or have a lower status (based on membership type) with the entity. In some implementations, transaction terminal 220 may only be reserved to provide a service when user device 210 is associated with a user account of the entity.
According to some implementations, branch manager platform 225 may allocate transaction terminal 220 based on identifying a particular time in the request for service received from user device 210. For example, branch manager platform 225 may determine an expected availability of the service at the service location at the requested time based on a usage (e.g., current usage and/or historical usage) of transaction terminals 220 that provide the service and allocate transaction terminal 220 at the service location based on the expected availability. In some implementations, branch manager platform 225 may utilize machine learning for allocating transaction terminal 220 to provide a service. For example, machine learning may be used to predict an availability of a transaction terminal based on an expected demand (e.g., either current demand, historical demand, and/or the like). In such cases, branch manager platform 225 may utilize machine learning to update a model corresponding to predicting the availability of transaction terminal 220.
Branch manager platform 225 may allocate transaction terminal 220 to provide a service by reserving or scheduling a time period for transaction terminal 220 to provide the service. For example, branch manager platform 225 may send instructions or a message to place transaction terminal 220 in a reservation mode during a particular time associated with performance of the service (e.g., a time requested in the request). Accordingly, when in reservation mode, transaction terminal 220 may only be activated or enabled to provide a service via an interaction with user device 210.
In some implementations, branch manager platform 225, when allocating multiple transaction terminals 220 for multiple services may determine a time period during which a first transaction terminal 220 and a second transaction terminal are both available based on availability of the first transaction terminal 220 and the second transaction terminal 220. In such a case, the first transaction terminal 220 and the second transaction terminal 220 may be reserved at the same time. For example, an EV charging station and a transaction terminal for walk-up banking account service may be reserved during a same time period (e.g., so that a user's vehicle may charge while receiving the banking account service).
In this way, branch manager platform 225 may allocate transaction terminal 220 to provide a service (e.g., during a period of time) to enable or permit user device 210 to interact with the transaction terminal 220 to enable performance of the service.
As further shown in
In some implementations, branch manager platform 225 may detect the interaction by monitoring transaction terminal 220 to determine that the interaction occurred during a time period associated with providing the service. According to some implementations, the interaction may include a NFC interaction between user device 210 and the transaction terminal 220, transaction terminal 220 capturing an image on a display of user device 210 (e.g., to scan a barcode or QR code), transaction terminal 220 receiving verification information associated with user device 210 receiving or reserving the service, and/or the like.
In some implementations, the verification information may include a transaction identifier or reservation identifier sent to user device 210 and/or entered on an input device of transaction terminal 220. Additionally, or alternatively, the verification information may include biometric information associated with a user of user device 210. For example, the verification information may include a biometric signature, such as a fingerprint signature, a facial scan signature, a retina scan signature, a gait signature, and/or the like associated with the user. In such cases, based on the interaction of providing the verification information, transaction terminal 220 may perform a user identification verification process to verify the identity of the user. For example, transaction terminal 220 may perform a biometric scan (e.g., capture a fingerprint, capture an image of a user's face, and/or the like) of a user that caused the interaction between user device 210 and transaction terminal 220. Transaction terminal 220 may authorize the service to be provided based on whether transaction terminal 220 is able to match the biometrics of the user with a biometric token from user device 210.
In this way, branch manager platform 225 may detect an interaction between user device 210 and transaction terminal 220 to permit branch manager platform 225 to facilitate processing a transaction for the service.
As further shown in
In some implementations, branch manager platform 225 may cause the transaction to be processed using payment from a payment account associated with a user account and the entity. Additionally or alternatively, branch manager platform 225 may cause the transaction to be processed by causing a transfer of funds from the payment account associated with the user account of user device 210 to an account of the entity that operates the service location and/or that operates transaction terminal 220. For example, branch manager platform 225 may instruct transaction backend 250 to transfer funds from the payment account to the account of the entity.
In some implementations, branch manager platform 225 may identify a characteristic of the user account (e.g., membership information, account balance information, membership type information) and determine a transaction amount to be charged based on the characteristic of the user account. For example, if the user account indicates that a user associated with user device 210 is a top tier member, then branch manager platform 225 may determine transaction amount to be discounted (e.g., based on an amount, a percentage of a particular rate (e.g. 0%, 50%, 75%, etc.) relative to a non-top tier member or non-member. In such cases, branch manager platform 225 may cause withdrawal of funds from the payment account based on the determined transaction amount. In some implementations, the payment account (e.g., a checking account, a savings account, and/or the like) may be managed by an entity (e.g. a financial institution) that operates the service location (e.g., a branch of the financial institution).
In this way, branch manager platform 225 may cause a transaction to be processed for performance of the service based on an interaction between user device 210 and transaction terminal 220.
Although
Accordingly, branch manager platform 225 may be integrated for use with user device 210 and/or transaction terminal 220 to indicate an offered service at a service location, determine availability of the offered service, reserve transaction terminal 220 (e.g., by scheduling time period for providing the service based on an interaction with user device 210) to provide or facilitate providing the service, and/or process a transaction for the service. As such, some implementations described herein may conserve a variety of computing resources (e.g., resources that may be used to search for services), network resources (e.g., resources to facilitate processing transactions with third party financial institutions), and/or power resources (e.g., resources used by an EV and/or user device 210 to identify an available EV charging station, resources to process transactions with third party financial institutions, resources to power an unused transaction terminal 220, and/or the like).
The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.
As used herein, the term component is intended to be broadly construed as hardware, firmware, or a combination of hardware and software.
Some implementations are described herein in connection with thresholds. As used herein, satisfying a threshold may refer to a value being greater than the threshold, more than the threshold, higher than the threshold, greater than or equal to the threshold, less than the threshold, fewer than the threshold, lower than the threshold, less than or equal to the threshold, equal to the threshold, or the like.
It will be apparent that systems and/or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware can be designed to implement the systems and/or methods based on the description herein.
Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend from only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.), and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
