Dynamic generation of digital messages with unique links for direct to merchant payments

Patent metadata

Field	Value
Publication number	US-12400231-B2
Application number	US-202318324859-A
Country	US
Kind code	B2
Filing date	May 26, 2023
Priority date	Sep 30, 2020
Publication date	Aug 26, 2025
Grant date	Aug 26, 2025

Abstract

A payer initiates a payment transaction of a certain dollar amount through a user interface provided by their bank. The bank generates a hyperlink associated with the payment transaction. By managing a state of the transaction, the hyperlink can be given an expiration time and/or a counter of visits. The hyperlink is sent to a payment recipient in a text message or email, either by the payer or by the bank. Upon following the hyperlink, the recipient can enter their own debit card information to receive the money transfer to their debit account, without the need to set up an account login or account. A notification mechanism, such as a broadcast stream of payments, can be employed to inform different entities (such as those recording property payments or utilities payments) that a payment was made to the payment recipient.

First claim

What is claimed is:

1. A transaction management system for managing direct payer to payee transactions without intermediate payment systems, the transaction management system comprising:
a server having an electronic communications interface capable of receiving data from a payer computing device and a payee computing device via a digital communications network, wherein the server is associated with and is in electronic communication with a trusted consumer banking service computing device associated with a consumer banking service where a user associated with the payer computing device holds a first financial account;
wherein an application is installed on the payer computing device, and the application is configured to generate one or more user payment interfaces on the payer computing device which allow a payer to enter electronic payment transaction information;
wherein the payer computing device interacts electronically with the server and the trusted consumer banking service computing device, wherein the payee computing device interacts electronically with the server, and wherein the server interacts electronically with one or more third party payment processing computer systems to record payments made by payers to payees, wherein recording payments updates a ledger representing one or more accounts held by a payer or a payee with the one or more third party payment processing computer systems; and
the server, comprising a memory configured to store instructions and at least one processor configured to execute the instructions to perform operations comprising:
receiving, by the server and from the payer computing device, an electronic payment transaction comprising a monetary value;
in response to identifying, by the server, the first financial account from which to debit the monetary value for the electronic payment transaction and based on receiving the electronic payment transaction, debiting the first financial account of the monetary value;
crediting, by the server, a holding account established at the server and associated solely with the payee for a credit amount, wherein the holding account is separate from the first financial account, wherein the credit amount is the monetary value for the electronic payment transaction;
generating, by the server, a unique hyperlink associated solely with the electronic payment transaction;
transmitting, by the server or the payer computing device, the unique hyperlink via an electronic communication to the payee computing device, wherein accessing the unique hyperlink on the payee computing device will cause the payee computing device to generate a payment acceptance interface uniquely associated with the electronic payment transaction for entry by the payee via the payee computing device of debit card information which is associated with a second financial account associated with the payee and to which the transaction management system can credit the monetary value to complete the electronic payment transaction, wherein the payment acceptance interface is generated on the payee computing device via a browser or a device-specific application already native to the payee computing device;
receiving, by the server and in response to the payee computing device accessing the unique hyperlink, a request to deliver the payment acceptance interface associated with the electronic payment transaction to the payee computing device;
in response to determining that the unique hyperlink is valid, delivering, by the server, the payment acceptance interface associated with the electronic payment transaction to the payee computing device;
receiving, by the server and based on payee interaction with the payment acceptance interface on the payee computing device, the debit card information associated with the second financial account associated with the payee computing device, wherein the payee interaction occurs without a requirement to create an account with the transaction management system, or log in to the transaction management system, or download any dedicated application associated with the electronic payment transaction;
based on receiving the debit card information, processing the electronic payment transaction by transmitting, by the server, a debit instruction to the holding account to debit the holding account for the monetary value, and a credit instruction to a second financial institution associated with the second financial account to post a credit to the second financial account for the monetary value; and
automatically, in response to processing the electronic payment transaction, transmitting, by the server and to the one or more third party payment processing computer systems via an electronic broadcast communication, payment transaction data between the payer and the payee.

2. The transaction management system of claim 1 , wherein transmitting the unique hyperlink via the electronic communication to the payee computing device comprises providing, for display via a message graphical user interface for viewing the electronic communication, the unique hyperlink together with a text message element for generating a message to the payee computing device.

3. The transaction management system of claim 1 , wherein receiving, by the server and from the payer computing device, the electronic payment transaction comprising the monetary value comprises:
providing, for display via a user interface of the application installed on the payer computing device, a payee selection element and a transaction value element; and
identifying the monetary value and the payee computing device based on user interaction with the payee selection element and the transaction value element.

4. The transaction management system of claim 1 , wherein the operations further comprise debiting the first financial account of the monetary value based on determining that the first financial account or one or more additional financial accounts corresponding to the payer computing device have sufficient funds to cover the electronic payment transaction.

5. The transaction management system of claim 4 , wherein the operations further comprise generating, utilizing a machine learning model, a feasibility recommendation that the first financial account or the one or more additional financial accounts corresponding to the payer have sufficient funds to cover the electronic payment transaction.

6. The transaction management system of claim 1 , wherein delivering, by the server, the payment acceptance interface associated with the electronic payment transaction to the payee computing device comprises providing, for display:
a receive payment message indicating the monetary value and a payer identifier corresponding to the payer computing device, and
one or more debit card information entry fields.

7. The transaction management system of claim 1 , wherein generating, by the server, the unique hyperlink associated with the electronic payment transaction comprises generating a hyperlink entry for the unique hyperlink within a hyperlink database.

8. The transaction management system of claim 7 , wherein determining that the unique hyperlink is valid comprises, in response to determining that the payee computing device has accessed the unique hyperlink, accessing the hyperlink entry within the hyperlink database to verify that the unique hyperlink is valid.

9. The transaction management system of claim 1 , wherein the operations further comprise:
determining an expiration trigger associated with the unique hyperlink; and
determining that the unique hyperlink is valid by determining that the expiration trigger has not occurred.

10. The transaction management system of claim 9 , wherein the expiration trigger

Assignees

• Chime Financial Inc

Inventors

• Ducker Michael
• Wu Baishi

Classifications

• G06N20/00

  Machine learning · CPC title

• G06Q20/4014

  Identity check for transactions · CPC title

• G06Q20/4016 Primary

  involving fraud or risk level assessment in transaction processing · CPC title

• G06Q20/16

  Payments settled via telecommunication systems · CPC title

• G06Q20/108

  Remote banking, e.g. home banking · CPC title