Patent ID: 12236406

DESCRIPTION OF THE EMBODIMENTS

Disclosed embodiments improve the convenience and reduce risks associated communal bill payment, i.e., group bill payments. To achieve these improvements in group bill payment systems and methods, the disclosed embodiments comprise creating a secure group bill payment account associated with a plurality of group members. The group bill payment account is configured to receive information via a network from the plurality of group members. The group bill payment account may be further configured to transmit a group payment to a provider. In some embodiments, the group bill payment account receives instructions from a group member to create a rule for requesting payment from a first group member to the group bill payment account, the bill being from the provider and being associated with the group members. The group bill payment server may determine a group member charge based on the rule and a received bill. In some embodiments, the group bill payment account sends a payment request to a group member based on the group member charge and receives a deposit into the group bill payment account from the group member based on the payment request. The group bill payment account may transmit the group payment from the group bill payment account to the provider and send a notification to the first group member, the notification comprising information about a status of the group payment.

In the embodiments, a group member may be a family member, a roommate, an employee, a business partner, a colleague, a friend, a club member, a team member, or other type of group member.

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings and disclosed herein. Wherever convenient, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG.1is a diagram of an exemplary group bill payment system100. In particular,FIG.1depicts a diagram of exemplary system100, consistent with disclosed embodiments, revealing some technical aspects of the present disclosure for achieving the intended results of the present disclosure. System100is an example of a system group bill payment. By creating and using a group bill payment account configured to receive deposits and transmit payments to a provider, the embodiments allow for improved convenience and reduced risk in communal bill payment.

As shown inFIG.1, system100may include a plurality of group member devices102a,102b, and102n; a plurality of financial institutions104a,104b, and104n; group bill payment server106; group database108; provider110; and network112. Components of system100are connected to each other through network112.

FIG.1is an exemplary configuration of system100. As will be appreciated by one skilled in the art, the components and arrangement of components included in system100may vary. For example, as compared to the depiction inFIG.1, system100may include a larger or smaller number of group member devices, financial institutions, providers, group bill payment servers, or networks. In addition, system100may further include other components or devices not depicted that perform or assist in the performance of one or more processes consistent with the disclosed embodiments. The components and arrangements shown inFIG.1are not intended to limit the disclosed embodiments, as the components used to implement the disclosed processes and features may vary.

Referring toFIG.1, a group member may use one or more group member devices102a-n. Group member devices102a-nmay be personal computers, mobile devices, smartphones, tablets, or the like. An exemplary embodiment of group member device102a-nis depicted inFIG.2and described below.

Consistent with disclosed embodiments, group member devices102a-nmay be used to access systems associated with group bill payment server106, a financial institution104, or a provider110. In some embodiments, a group member using one of group member devices102a-nlogs into group bill payment server106with a method of authentication. For example, group member devices102a-nmay be configured to allow the user to perform an authentication process comprising providing a credential. The credential may comprise at least one of a username, a password, a pin, an answer to a security question, a selection of a picture, a card swipe, a proximity card scan, a token, a one-time password, speech, a signature, a keyboarding rhythm, a fingerprint, a biometric identifier, or another credential.

In some embodiments, group member devices102a-nare configured to retrieve and transmit data to and from the other components of system100. For example, group member devices102a-nmay be configured to retrieve or update a group bill payment account status, payment information, provider service data, or other data from at least one of group bill payment server106, financial institutions104a-n, or provider110. Group member devices102a-nmay be configured to access group bill payment server106and create a group member user account and a group bill payment account. In some embodiments, group member devices102a-nmay be configured to access group bill payment server106and assign a group bill payment account manager.

In some embodiments, a group member using a group member device102a-naccesses group bill payment server106to configure at least one of a payment to provider110or a deposit from a financial institution. The payment and deposit may be configured for immediate transfer, for a scheduled transfer, or for recurring scheduled transfer.

In some embodiments, group member devices102a-nare configured to send and receive messages or notifications via network112to and from components of system100, in including to and each other, to and from group bill payment server106, to and from financial institutions104a-n. For example, group member devices102a-nmay send or receive a notification to another component of system100comprising at least one of a provider payment status, a group member deposit status, or a group bill payment account balance. In some embodiments, a group member using a group member device102a-nmay conduct chat sessions with another group member using another group member device102a-n. As one of skill in the art will appreciate, other forms of communication between components of system100are possible.

In the embodiment of system100, financial institutions104a-ncomprise a server comprising one or more processors, one or more input/output (I/O) devices, and a memory. Financial institutions104a-nconnected to network112and may comprise at least one of a checking account, a savings account, a credit card account, or other financial account. The financial accounts may be associated with one or more group members. The financial accounts and user accounts may be associated with a provider.

Financial institutions104a-nare capable of completing an electronic transaction. In some embodiments, financial institutions104a-nmay be capable of performing millions of transactions per day or more. Financial institutions104a-nare configured to receive a deposit in a financial account and make a payment from the financial account.

Financial institutions104a-nmay comprise an online platform for accessing a financial account. For example, a group member using group member device102a-nmay use an online platform to check an account status, make a deposit into the financial account, or make a payment from the financial account.

In some embodiments, financial institutions104a-nuse secure authentication processes. For example, a financial institution104a-nmay require a group member using a group member device102a-nor a provider110to perform an authentication process before data relating to a financial account. The authentication process may comprise providing a credential. The credential may comprise at least one of a username, a password, a PIN, an answer to a security question, a selection of a picture, a card swipe, a proximity card scan, a token, a one-time password, speech, a signature, a keyboarding rhythm, a fingerprint, a biometric identifier, or another credential.

In some embodiments, financial institutions104a-nare configured to perform Payment Card Industry (PCI) compliant transactions or to perform transactions compliant with other standards. In some embodiments, financial institutions104a-nmay comprise an e-commerce payment system configured to perform transactions including at least one of a credit card transaction, a debit card transaction, a smart card transaction, an E-wallet transaction, a NetBanking® transaction, a mobile payment, an AmeriCommerce® transaction, an Amazon Pay® transaction, a Visa Pay® transaction, an Apple Pay® transaction or the like. As one of skill in the art will appreciate, financial institutions104a-nmay be configured to perform electronic transaction using still other methods.

In some embodiments, financial institutions104a-nuse encryption methods to send information to and from other components of system100. Financial institutions104a-nmay use encryption methods to send data, to send messages, or to complete transactions.

As depicted inFIG.1, group bill payment server106is connected to network112. Group bill payment server106comprises one or more processors, one or more input/output (I/O) devices, and a memory. In some embodiments, group bill payment server106is hosted on a cloud compute service.

In some embodiments, group bill payment server106is configured to allow a user accessing group bill payment server106through network112using one of group member devices102a-n. In some embodiments, group bill payment server106is configured to create a plurality of user accounts associated with respective group members and may be further configured to create one or more provider accounts associated with provider110.

In some embodiments, group bill payment server106is configured to create a secure group bill payment account associated with a plurality of group members. Group bill payment server106may be capable of linking the group bill payment account to an external bank account. In some embodiments, the external bank account may carry a group bill payment account balance to be used for future payments.

In some embodiments, group bill payment server106is configured for receiving instructions from a group member using one of group member devices102a-n. For example, group bill payment server106may receive instructions to create a rule for requesting payment from a group member to the group bill payment account.

In some embodiments, group bill payment server106may be configured to receive a bill associated with group members from a provider. In some embodiments, receiving the bill comprises receiving an image file and using optical character recognition to generate text data based on the image file. In some embodiments, accessing an email account using a credential; and automatically detecting an email in the email account from the provider, wherein the email contains electronic billing information. In some embodiments, group bill payments server106is configured to receive a bill directly from provider110. In some embodiments, group bill payments server106receives information about bills through manual entry from group member devices102a-n. In some embodiments, group bill payments server106can receive bill information from financial institutions104a-.

In some embodiments, group bill payment server may be configured to determine a group member charge based on a bill from a provider and a rule. The rule may be based on a predetermined percentage, an income, or a usage rate.

In some embodiments, group bill payment server106is configured to send requests for payment to group member devices102a-n. The request may comprise at least one of an email, a text message, a push notification, a direct debit from a bank account, or a charge to a credit card. Group bill payment server106may be configured to send a notification to any group member based on nonpayment by one of the group members.

Group bill payment server106may be capable of transmitting a payment. In some embodiments, group bill payment server106may comprise an e-commerce payment system. Transmitting the payment may comprise completing an electronic transaction. For example, the group bill payment account may complete a credit card transaction, a debit card transaction, a smart card transaction, an E-wallet transaction, a NetBanking® transaction, a mobile payment, an AmeriCommerce® transaction, an Amazon Pay® transaction, a Visa Pay® transaction, an Apple Pay® transaction or the like. In some embodiments, Group bill payment server106transmits a lump payment to a provider comprising a plurality of group bill payments associated with respective groups.

Consistent with disclosed embodiments, group bill payment server106may be configured to receive a deposit from financial institutions104a-nand transmit a group payment to provider110. Transmitting a payment may comprise automatically printing a check and sending the check to provider110via at least one of a courier service or postal service. In some embodiments, transmitting a payment comprises generating a digital image of a check and transmitting the digital image to provider110.

In some embodiments, group bill payment server106makes a payment to one or more financial institutions to an account associated with provider110.

In some embodiments, group bill payment server106is a component of a financial institution. The financial institution may be capable of carrying a group bill payment account balance to be used for future payments. In an embodiment not depicted inFIG.1, group bill payment server106may be a component of one of financial institutions104a-n.

In some embodiments, a user or a provider may be required to complete an authentication processes that comprises providing a credential before accessing group bill payment server106. The credential may comprise at least one of a username, a password, a pin, an answer to a security question, a selection of a picture, a card swipe, a proximity card scan, a token, a one-time password, speech, a signature, a keyboarding rhythm, a fingerprint, a biometric identifier, or another credential.

In some embodiments, group bill payment server106uses encryption methods to send information to and from other components of system100or components outside system100. Group bill payment account server106may use encryption methods to send or retrieve data, to send messages, to complete transactions, or to perform other operations.

In some embodiments, group bill payment server106is configured to perform at least one of Payment Card Industry (PCI) compliant transactions, Automated Clearing House (ACH) transactions, or transactions compliant with other standards. PCI is an information security standard for organizations that handle credit card transactions. PCI is a standard to increase security of cardholder data to reduce credit card fraud. PCI compliant institutions must validate compliance annually, by an external Qualified Security Assessor (QSA) or by an Internal Security Assessor (ISA) that creates a Report on Compliance. PCI compliance is mandatory for certain credit card brands and typically required of organizations handling large volumes of transactions. PCI Data Security Standard requirements comprise: building and maintaining secure network and systems; protecting cardholder data; maintaining a vulnerability management program; implementing strong access control measures; monitoring and testing networks; maintaining an information security policy. As one of skill in the art will appreciate, other group bill payment server106may be configured to comply with other standards.

As one of skill in the art will appreciate, group bill payment server106may be configured to perform electronic transactions using still other methods.

Consistent with the present disclosures, in some embodiments group bill payments server106is hosted on a cloud compute service and generates container instances in response to triggering events to perform disclosed methods. In some embodiments, the triggering event is generated by a messaging queue service or data streaming platform. Advantageously, container instances are ephemeral, with their provisioning based on a triggering event and their terminating based on completion of one or more jobs comprising the performance of disclosed methods. In some embodiments, the triggering event is receiving a bill from a provider. In some embodiments, the triggering event is the passage of a predetermined date and time.

Referring again toFIG.1, system100may comprise group database108connected to group bill payment server106. Database108comprises one or more memory units. In some embodiments, Database108may be implemented as one or more databases configured to store datasets. The datasets, in some embodiments, may be associated with group bill payment accounts, group member accounts, providers, and financial institutions. For example, database108may store group bill payment account balances, financial account credentials, provider account credentials, email credentials, a group member account payment method. Database108may be implemented using document management systems, SQL databases utilizing Microsoft® SQL Server® engines, SharePoint® databases, Oracle® databases, Sybase™ databases, or other relational databases, or non-relational databases such as key-value stores or NoSQL databases such as Apache® HBase™ In some embodiments, database108may comprise an associative array architecture, such as a key-value storage, for storing and rapidly retrieving large amounts of information.

In some embodiments, not shown inFIG.1, group database108is a component of group bill payment server106.

As depicted inFIG.1, provider110is connected to network112. Provider110may be a business, a landlord, a mortgage lender, an insurance provider, a bank, a credit card company, a utility provider, an Internet Service Provider, a cable provider, a service provider, a non-profit organization, a school, a charity, an entertainment venue, a membership organization, a food club, a drink club, or other provider of goods or services. Not shown in detail inFIG.1, provider110may comprise an organization, an agent acting on behalf of the organization, or a device or computer system configured to perform operations. As one of skill in the art would understand, provider110may comprise still other examples.

In some embodiments, provider110is configured to receive an electronic payment directly from group bill payment account106via network112. Alternatively or additionally, provider110may be configured to receive an electronic payment from group bill payment account106via network112at a financial account held with one of financial institutions104a-n. In some embodiments, provider110may be configured to receive a check. In some embodiments not shown, provider110may not be connected to network112and may be capable of receiving a check.

In some embodiments, provider110sends a bill. In some embodiments, sending a bill comprises at least one of mailing a paper bill to an address, emailing a bill to at least one of a group member or group bill payment account server106, sending a notification to a group member, or allowing a group member or other user to download a bill. In some embodiments, the notification is a text message, an email, or a push notification.

In some embodiments, provider110may complete an authentication process that comprises providing a credential before accessing group bill payment server106or accessing one of financial institutions104a-n. The credential may comprise at least one of a username, a password, a pin, an answer to a security question, a selection of a picture, a card swipe, a proximity card scan, a token, a one-time password, speech, a signature, a keyboarding rhythm, a fingerprint, a biometric identifier, or another credential.

In the embodiment of system100, network112may be a public network or private network. Network112may be, for example, a wired or wireless network, including, without limitation, a Local Area Network, a Wide Area Network, a Metropolitan Area Network, an IEEE 802.11 wireless network (e.g., “Wi-Fi”), a network of networks (e.g., the Internet) or the like. Group member devices102a, financial104a-n, group bill payment server106, and provider110, may connect to network112. In some embodiments, network112may be secure and require a password to access the network.

FIG.2is a diagram of an exemplary group member device, consistent with disclosed embodiments. In some embodiments, group member device102is a personal computer, a mobile device, a smartphone, a tablet, or the like.

As shown inFIG.2, group member device102comprises a comprises one or more processors210, one or more input/output (I/O) devices220, and a memory230.

Processor210may be one or more known or custom processing devices designed to perform functions of the disclosed methods, such as a single core or multiple core processors capable of executing parallel processes simultaneously. For example, processor210may be a single core processor configured with virtual processing technologies. In certain embodiments, processor210may use logical processors to simultaneously execute and control multiple processes. Processor210may implement virtual machine technologies, or other known technologies to provide the ability to execute, control, run, manipulate, store, etc. multiple software processes, applications, programs, etc. One of ordinary skill in the art would understand that other types of processor arrangements could be implemented that provide for the capabilities disclosed herein.

I/O devices220may also include one or more communication modules (not shown) for sending and receiving information from other components in system100by, for example, establishing wired or wireless connectivity between group member device102and network112. Exemplary communication modules as I/O devices220may include, for example, a short-range or near field wireless communication modem, a Wi-Fi communication modem, or a cellular communication modem.

In some embodiments, group bill payment server106is hosted on a cloud compute service. Examples of cloud compute service that may host group bill payments server106include AWS Lambda by Amazon®, Oracle Cloud®, Cloud Functions® by Google®, Azure Functions® by Microsoft®, Apache OpenWhisk®, or other cloud compute services. In some embodiments, to perform methods disclosed herein, users may interact with native cloud compute service functions through terminals or shells using tools like, for example, AWS® Command Line Interface, Google's® gcloud command line tool, or Secure Shell (SSH).

In some embodiments, group bill payment server106includes a messaging queue service. For example, group bill payment server106may comprise at least one of Amazon Simple Queue Service (Amazon SQS®), RabbitMQ, Apache ActiveMQ®, RocketMQ®, or other messaging queue service. The messaging queue service may be configured to send messages between two or more clients and may support cross language clients and protocols in JAVASCRIPT, C, C++, JAVA, PHP, PYTHON, RUBY, PERL, BASH, or the like. The messaging queue service may generate a triggering event in response to at least one of receiving a bill, receiving a notification from a group member device, receiving a notification from a provider, receiving a notification from a financial institution, or the passage of a predetermined date and time.

Group bill payment server106may comprise a distributed streaming platform used alternatively to or in combination with a messaging queue service. For example, group bill payment server106may comprise at least one of Amazon Kinesis Data Streams®, Apache Kafka®. Azure Events Hub®, Google Cloud DataFlow, or other distributed streaming platform. The distributed streaming platform may be configured to publish and subscribe to data streams, store data streams, and process data streams in real time. In some embodiments, the distributed streaming platform generates a triggering event in response to at least one of receiving a bill, receiving a notification from a group member device, receiving a notification from a provider, receiving a notification from a financial institution, or the passage of a predetermined date and time.

In some embodiments, group bill payment server106is hosted on a cloud compute service and is configured to generate ephemeral container instances in response to triggering events. In some embodiments, the triggering event is generated by a messaging queue service or data streaming platform. In some embodiments, the triggering event is generated in response to receiving a bill. In some embodiments, the trigger event is the passage of a predetermined date and time. In some embodiments, the trigger event is generated in response to receiving a notification from at least one of a group member device, a provider, or a financial institution. In some embodiments, a container instance may be an AWS Lambda® compute instance, Oracle Cloud® compute instance, Google Cloud Functions® virtual machine, Microsoft Azure Functions® host instance, Apache OpenWhisk® instance, or other container instance.

A container instance, in some embodiments, may comprise a stand-alone, executable package that includes code, runtime, system tools, system libraries, and settings that is configured to execute a job, the job performing methods disclosed herein. A container instance may be scaled by functions of a cloud compute service to include a number of processors and an amount of memory based on an estimated size of a job. A container instance may be configured to execute functions written in one or more programming languages, including JAVASCRIPT, C, C++, JAVA, PHP, PYTHON, RUBY, PERL, BASH, or other programming or scripting languages. Container instances are ephemeral and may run for a single job or a series of jobs, and data stored by container instance may be destroyed upon termination, providing security advantages.

Advantageously, a container instance may be a closed container. That is, a container instance may block attempts to access the container and not permit access from outside using terminals or remote shell tools like SSH, RTP, FTP, or Curl, for example. Accordingly, a container instance provides security benefits to system100by protecting personal or financial information.

Group member device102may comprise memory230that includes one or more storage devices configured to store information used by processor210(or other components) to perform certain functions related to the disclosed embodiments. In one example, group member device102may include memory230that includes instructions to enable processor210to execute one or more applications, such as server applications, a call hosting application, a messaging application, an electronic transaction application, an account status application, network communication processes, and any other type of application or software known to be available on computer systems. Alternatively or additionally, the instructions, application programs, etc. may be stored in an internal database or external storage (not shown) in direct communication with group member device102, such as one or more databases or memory accessible over network112. A database or other external storage may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible (i.e., non-transitory) computer-readable medium.

FIG.3is a diagram of an exemplary group bill payment server106, consistent with disclosed embodiments.

In some embodiments, group bill payment server106may be on a single server, a cluster of servers configured for parallel processing, multiple server clusters, or a cloud service. Group bill payment server106may be hosted on a private or public network and may further be on a cloud. As one of skill in the art will appreciate, other arrangements are possible, consistent with disclosed embodiments.

As shown inFIG.3, group bill payment server106comprises one or more processors310, one or more I/O devices320, and a memory330. I/O devices may comprise a printer. Memory330may include at least one of group member module332, financial institution module334, or provider module336.

Processor310may be one or more known or custom processing devices designed to perform functions of the disclosed methods, such as a single core or multiple core processors capable of executing parallel processes simultaneously. For example, processor310may be a single core processor configured with virtual processing technologies. In certain embodiments, processor310may use logical processors to simultaneously execute and control multiple processes. Processor231may implement virtual machine technologies, or other known technologies to provide the ability to execute, control, run, manipulate, store, etc. multiple software processes, applications, programs, etc. One of ordinary skill in the art would understand that other types of processor arrangements could be implemented that provide for the capabilities disclosed herein.

Group bill payment server106may include one or more storage devices configured to store information used by processor310(or other components) to perform certain functions related to the disclosed embodiments. In one example, group bill payment server106may include memory330that includes instructions to enable processor310to execute one or more applications, such as server applications, a call hosting application, a messaging application, an electronic transaction application, an account status application, network communication processes, and any other type of application or software known to be available on computer systems. Alternatively or additionally, the instructions, application programs, etc. may be stored in an internal database or external storage (not shown) in direct communication with group bill payment server106, such as one or more databases or memory accessible over network112. A database or other external storage may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible (i.e., non-transitory) computer-readable medium.

In one embodiment, group bill payment server106may include memory330that includes instructions that, when executed by processor310, perform one or more processes consistent with the functionalities disclosed herein. Methods, systems, and articles of manufacture consistent with disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example, group bill payment server106may include memory330that may include one or more programs to perform one or more functions of the disclosed embodiments, including the functions performed by member module332, financial institution module334, or provider module336. Moreover, processor310may execute one or more programs located remotely from system100. For example, group bill payment server106may access one or more remote programs, that, when executed, perform functions related to disclosed embodiments.

As depicted inFIG.3, I/O devices320may comprise printer322configured to print a check. I/O devices320may also include one or more communication modules (not shown) for sending and receiving information from other components in system100by, for example, establishing wired or wireless connectivity between group bill payment server and network112. Exemplary communication modules as I/O devices310may include, for example, a short-range or near field wireless communication modem, a Wi-Fi communication modem, or a cellular communication modem. As one of skill in the art will appreciate, to perform functions disclosed in the embodiments, I/O devices320may comprise other devices not depicted inFIG.3.

Still referring toFIG.3, memory330may comprise group member module332, financial institution module334, and provider module336.

Group member module332may be configured to create, modify, or delete user accounts and group bill payment accounts, consistent with disclosures made in reference toFIG.1. In some embodiments, member module332is configured to send notifications to group members. For example, group member module332may be configured to send and receive data to and from one of group member devices102a-n. Group member module332may be configured to generate a rule for group bill payment. Consistent with disclosed embodiments and as depicted inFIG.3, member module332may be configured to require and accept an authentication credential. As disclosed above with respect toFIG.1, member module332may be configured to send and receive encrypted data to and from at least one of a group member device102a-n, a financial institution104a-n, or provider110.

Still referring toFIG.3, financial institution module334may be configured to make and receive payments to and from a financial institution like, for example, financial institutions104a-nassociated with a group member or a provider.

Referring toFIG.3, provider module336may be configured to create, modify, or delete provider accounts, consistent with disclosures made in reference toFIG.1. In some embodiments, provider module336is configured to send notifications to providers. For example, provider module336may be configured to send and receive data to and from a device associated with provider110. Consistent with disclosed embodiments and as depicted inFIG.3, provider module336may be configured to require and accept an authentication credential. As disclosed above with respect toFIG.1, provider module336may be configured to send and receive encrypted data to and from at least one of a group member device102a-n, a financial institution104a-n, or group bill payment account server106.

FIG.4is a flowchart of an exemplary process400for group bill payment, consistent with disclosed embodiments performed by group bill payment server106.

At step402, group bill payment server106creates a group bill payment account associated with a plurality of group members. In some embodiments, creating a group bill payment account comprises receiving information via network112from one of the group member devices102a-n. The information may comprise at least one of a credential or a member payment method. In some embodiments, step402comprises adding or removing group members from the group bill payment account.

In some embodiments, group bill payment server stores user account information and group bill payment account information on group database108.

In some embodiments, step402may comprise assigning or modifying a privilege of a group member. For example, step402may comprise assigning a group member to manage the group bill payment account following an authentication process. In some embodiments, a plurality of group members may be assigned managing privileges. In some embodiments, the authentication process comprises sending a token to group bill payment server106. In some embodiments, the token may have been previously received from at least one of group bill payment server106or a remote token server (not depicted in the figures).

In some embodiments, step402comprises linking an external bank account held, for example, in one of financial institutions104a-n.

In some embodiments, step402may comprise receiving information associated with a provider comprising at least one of a provider deposit account, a provider address, a provider email address, or a credential associated with a user account hosted by a provider.

In some embodiments, group bill payment account106is hosted on a cloud compute service, and, at step402, a user may interact with native cloud compute service functions through terminals or shells using tools like, for example, AWS® Command Line Interface, Google's® gcloud command line tool, or Secure Shell (SSH).

Step404comprises receiving instructions from a group member to create a group bill payment rule.

In some embodiments, the instructions to create a group bill payment rule at step404comprises at least one of an amount due by a group member or a percentage of a bill owed by a group member. In some embodiments, the amount due may be a fixed amount. In some embodiments, the percentage may be one of a predetermined percentage, a percentage based on an income, or a percentage based on a usage rate. For example, the predetermined percentage may be a fixed percentage of a variable utility bill owed by the group member. In some embodiments, the percentage based on income may be proportional to the ratio of the income of the group member to the total income of all group members.

In some embodiments, the percentage based on a usage rate may be the relative proportion of data used by one or more user devices associated with the group member in a shared internet data plan. In some embodiments, the percentage based on a usage rate comprises identifying an area associated with a user in a floor plan uploaded to payment server110. In some embodiments, the percentage based on a usage rate is based on a number of hours, days, months, or other scheduling factor. For example, a group member may occupy an apartment only on weekends, and the group bill payment rule may be based on the number of weekend-days in a month.

In some embodiments, the group bill payment rule comprises a rule to pay a predetermined amount on a predetermined schedule. For example, the group bill payment rule may comprise paying a predetermined amount on the first business day of every month.

In some embodiments, step404comprises establishing a payment account associated with a group member to be used at step410when sending a payment request. For example, in some embodiments, at step404, a user may provide at least one of a direct debit account, a bank account withdrawal, a credit card, or other information to facilitate another electronic transaction. For example, the group bill payment account may complete a credit card transaction, a debit card transaction, a smart card transaction, an E-wallet transaction, a NetBanking® transaction, a mobile payment, an AmeriCommerce® transaction, an Amazon Pay® transaction, a Visa Pay® transaction, an Apple Pay® transaction or the like.

In some embodiments, step404comprises instructions to automatically send a request to an established payment account at step410and automatically receive a deposit at step412.

In some embodiments, step404comprises instruction to create a group bill payment account balance by sending a group bill payment request to a group member prior to receiving a bill. In some embodiments, step404comprises granting group bill payment server106access to a line of credit to be used in the event of nonpayment by a group member. In some embodiments, step404comprises instructions to send a payment request to a guarantor in the event of nonpayment by a group member. For example, a guarantor could be one of the group members, a relative of a group member, or other person associated with a group member.

In some embodiments, step404comprises modifying an existing rule. As will be appreciated by one of skill in the art, step404may comprise other operations consistent with disclosed embodiments.

In some embodiments, group bill payment account106is hosted on a cloud compute service, and, at step404, a user may interact with native cloud compute service functions through terminals or shells using tools like, for example, AWS® Command Line Interface, Google's® gcloud command line tool, or Secure Shell (SSH).

Step405comprises configuring group bill payment server106to receive a bill.

In some embodiments, at step405, a group member using a group member device102configures the group payment server106to access an account managed by provider110following an authentication protocol. For example, the group member may provide a website address, a username, and a password for accessing an account managed by provider110. Further, in some embodiments, the group member may provide instructions for downloading the bill.

In some embodiments, at step405, group bill payment server106may be configured to process a bill using optical character recognition (OCR). For example, the group member may provide instructions for identifying at least one of a charge or a due date following an OCR conversion of an image file.

In some embodiments, at step405, the group bill payment server106is configured to retrieve an email comprising a bill. For example, a group member may provide group bill payment server106with at least one of an email account username or an email account password, and further provide instructions for processing an email comprising a bill associated with provider110. The instructions may comprise at least one of a provider name, a rule for identifying a charge amount, a rule for identifying a due date, instructions to identify a charge in the text of an email, or instructions to identify a charge in an attachment.

In some embodiments, group billing server106is hosted on a cloud compute service and step405comprises cloud compute instructions to spin up, that is, generate, a container instance upon a triggering event. In some embodiments, the triggering event is generated by a messaging queue service or data streaming platform. The triggering event may be one of receiving a bill from a user device102a-n, receiving a bill from a provider110, receiving instructions to retrieve a bill from a group member device102, or the passage of a predetermined date and time. Consistent with the present disclosure, in some embodiments, step405comprises providing instructions to the container instance or the to automatically terminate the container instance upon completion of a job, the job comprising at receiving a bill and at least one of steps408-416.

In some embodiments, at step405, a user may interact with native cloud compute service functions through terminals or shells using tools like, for example, AWS® Command Line Interface, Google's® gcloud command line tool, or Secure Shell (SSH).

In some embodiments, the group bill payment rule created at step404comprises sending a predetermined payment amount on a predetermined schedule, and step405may be skipped.

Step406comprises receiving a bill associated with a provider and a group bill payment account. Receiving a bill comprises receiving a bill from at least one of a group member device102a-nor from provider110. In some embodiments, receiving a bill comprises receiving instructions comprising at least one of an amount due, a due date, a provider, or provider payment information. In some embodiments, the instructions are received from a user logged into at least one of a user account or a group bill payment account. In some embodiments, receiving a bill comprises receiving an image file and using OCR to generate text data based on the image file. In some embodiments, receiving a bill comprises accessing an email account using a credential. In some embodiments, receiving a bill comprises automatically detecting an email in the email account from the provider, wherein the email contains electronic billing information.

In some embodiments, the bill comprises a fixed charge that does not vary in amount for each billing cycle. In some embodiments, the bill comprises a variable charge that varies in amount for each billing cycle.

In some embodiments, step406is performed by a container instance generated, by group bill payment server106, in response to a triggering event, based on cloud compute instructions disclosed in reference to step405. In some embodiments, the container instance may be generated within milliseconds of a triggering event.

In some embodiments, the group bill payment rule created at step404comprises sending a predetermined payment amount on a predetermined schedule, and step406is skipped.

As will be appreciated by one of skill in the art, consistent with disclosed embodiments, creating a rule may comprise other logical constraints based on information associated with at least one of a provider, a bill, a schedule, a group member, or a payment method.

Step408comprises determining a charge to a group member based on the rule. Determining a charge comprises applying the rule created at step404. In some embodiments, the charge is further based on the received bill or electronic billing information. For example, group bill payment server106may determine a charge of $40.00 to a group member by applying a rule to assign 30% of a received utility bill that varies each billing cycle to a group member, wherein the received utility bill totaled $120.00. As another example, group bill payment server106may determine a charge by applying a rule that a group member owes a fixed fee of $500.00 for rent. In some embodiments, step408is performed by a container instance generated at step406.

Step410comprises sending a payment request. In some embodiments, sending the payment request comprises at least one of an email, a text message, a push notification, or sending a payment request to an established payment account. Sending a payment request to an established payment account may comprise, for example, a direct debit from a bank account, or a charge to a credit card.

In some embodiments, step410is performed by a container instance generated at step406.

In some embodiments, step410is performed in anticipation of a bill, based on a rule created at step404, prior to at least one of steps406or408. In these embodiments, a group bill payment account balance may be generated.

Step412comprises receiving a deposit from a group member into the group bill payment account. In some embodiments, receiving a deposit comprises at least one of receiving a check, receiving a wire transfer, a receiving a direct debit, performing a bank withdrawal from a linked bank account, charging a credit card, or other transaction. For example, the group bill payment account may complete a credit card transaction, a debit card transaction, a smart card transaction, an E-wallet transaction, a NetBanking® transaction, a mobile payment, an AmeriCommerce® transaction, an Amazon Pay® transaction, a Visa Pay® transaction, an Apple Pay® transaction or the like.

In some embodiments, step412is performed by a container instance generated at step406.

Step414comprises transmitting a group payment.

In some embodiments, transmitting a group payment at step414comprises transferring funds from group bill payment account106to one of a provider or a financial institution associated with a provider. In some embodiments, transmitting a group payment comprises sending an electronic payment. For example, the group bill payment account may complete a credit card transaction, a debit card transaction, a smart card transaction, an E-wallet transaction, a NetBanking® transaction, a mobile payment, an AmeriCommerce® transaction, an Amazon Pay® transaction, a Visa Pay® transaction, an Apple Pay® transaction or the like. In some embodiments, transmitting a group payment comprises automatically generating and sending a check. Generating a check may comprise printing a check with printer322. Sending a check may comprise sending a check by one of a courier service, a postal service, or other means. In some embodiments, transmitting a group payment is performed prior to step412.

In some embodiments, step414is performed by a container instance generated at step406.

Step416comprises sending a notification. In some embodiments, the notification comprises at least one of an email, a text message, or a push notification. In some embodiments, the notification comprises a payment status. In some embodiments, step416is performed by a container instance generated at step406.

In some embodiments not depicted inFIG.4, based on nonpayment by a group member, process400further comprises sending a second payment request to the group members. In some embodiments, process400comprises sending a nonpayment notification to another group member. In some embodiments, the nonpayment notification comprises at least one of sending an email, a text message, or a push notification. In some embodiments, in the event of nonpayment by a group member, group bill payment server106transmits a payment to provider110at step408using funds available in at least one of a group bill payment account balance, a line of credit, or a payment method of a guarantor. In some embodiments, in the event of nonpayment by a group member, group bill payment server106does not transmit a payment to provider110and skip408is skipped.

Consistent with disclosed embodiments, in some embodiments, any of steps402-416of process400may be performed by a container instance.

FIG.5shows diagram500of an exemplary apartment shared by group members, consistent with disclosed embodiments.

Consistent with disclosed embodiments, creating a rule for group bill payment based on usage may comprise creating a rule for group bill payment based on diagram500. The rule may comprise a percentage of a bill owed by a group member based on an area associated with a group member.

In some embodiments, three group members may reside in apartment in rooms502,504, and506. That is, three group members may be apartment-mates. As shown inFIG.5, apartment-mates residing in room502,504, and506use corresponding closets522,524, and518. Rooms508,510,512,520, and526represent a shared living room, a shared dining room, a shared kitchen, a shared utility closet, and a shared laundry room, respectively. In the example ofFIG.5, apartment-mates residing in rooms502and504share bathroom514, while an apartment mate residing in room506has exclusive use of bathroom516.

Considering this example, group members residing in rooms502,504, and506may be associated with a respective proportion of the apartment area. Respective proportions may be determined by summing the all areas of associated with a particular group member, including shared and exclusive-use areas, and dividing by the total area of the apartment.

In some embodiments, the respective proportion may change based on a change in the area associated with a group member, resulting in a modification to a rule. For example, a group member506may stop using kitchen512, or may offer use of closet518to a user residing in room502.

In some embodiments, the rule may be based on a weighting function. For example, the rule may assign a weight to each room502-518based on the perceived value of the respective room. Room506may be assigned a high weight owing to its greater privacy, while room504may be assigned a lower rate than room502because it may lack a window. Other arrangements are possible.

In some embodiments, more than one group member resides in at least one of rooms502,504, or506. That is the group may comprise apartment-mates and roommates. The rule for group bill payment may be based on the group members status as an apartment-mate and roommate.

For example, four apartment mates may share the apartment depicted in diagram500. Two roommates may reside in room506. In this example, the group bill payment server may first specify a collective percentage owed collectively by both roommates in room506, then specify a relative share of the collective percentage to each roommate. The relative share may be based on any criteria. As will be appreciated by one of skill in the art, other arrangements are possible.

Systems and methods disclosed herein involve unconventional improvements over conventional communal or group bill payment systems. As compared to conventional technologies for group bill payment, embodiments of the invention reduce risk and increase convenience.

Descriptions of the disclosed embodiments are not exhaustive and are not limited to the precise forms or embodiments disclosed. Modifications and adaptations of the embodiments will be apparent from consideration of the specification and practice of the disclosed embodiments. Additionally, the disclosed embodiments are not limited to the examples discussed herein.

Computer programs based on the written description and methods of this specification are within the skill of a software developer. The various programs or program modules can be created using a variety of programming techniques. For example, program sections or program modules can be designed in or by means of Java, C, C++, NodeJS, C #, GO, Python, Ruby, assembly language, or any such programming languages. One or more of such software sections or modules can be integrated into a computer system, non-transitory computer-readable media, or existing communications software.

Moreover, while illustrative embodiments have been described herein, the scope includes any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., of aspects across various embodiments), adaptations or alterations based on the present disclosure. The elements in the claims are to be interpreted broadly based on the language employed in the claims and not limited to examples described in the present specification or during the prosecution of the application, which examples are to be construed as non-exclusive. Further, the steps of the disclosed methods can be modified in any manner, including by reordering steps or inserting or deleting steps. It is intended, therefore, that the specification and examples be considered as exemplary only, with a true scope and spirit being indicated by the following claims and their full scope of equivalents.