# US 2024/0202736 A1 · System and method for making purchase payments after payment failures

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0202736 A1
- Document ID: US20240202736A1
- Status: Published application
- Kind: A1
- Application number: 18/590,209
- Filed: 2024-02-28
- Published: 2024-06-20
- Earliest claimed: 2018-01-09
- Assignees: Affirm, Inc.
- Applicants: Affirm, Inc.
- Inventors: Youyou Yang; Daniel Kaufman; Edward Oistacher
- Web page: https://patentgrep.com/patent/US20240202736A1

## CPC

- G06Q 20/407: {Cancellation of a transaction}
- G06Q 20/085: {involving remote charge determination or related payment systems}
- G06Q 20/14: specially adapted for billing systems
- G06Q 20/24: Credit schemes, i.e. "pay after"
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

When a loan payment failure occurs, a loan server can retry a payment from a client's financial institution sources rather than immediately charging the client for the payment failure. The payment retry is scheduled on a Friday that is at least three days after the payment failure. If a payment failure from the financial institution sources to the loan server occurs between a Friday and the following Monday the payment retry by the loan server to the financial institution sources will occur on the first following Friday and if the payment failure occurs on Tuesday, Wednesday or Thursday, the payment retry will occur on the second following Friday which is the Friday of the following week from the failure date.

## Claims

### Claim 1

A server for managing payment rescheduling associated with a loan of a buyer to be repaid via a financial source associated with the buyer, the server comprising:
a memory storing a rule table and program instructions;
a high-speed communication interface operably coupling the server to an external communication port to enable the server to communicate with external devices including a buyer computing device and a financial source computing device via wired or wireless communication; and
a processor configured to execute the program instructions and manage message processing for inbound and outbound messages via the high-speed communication interface,
wherein the program instructions, when executed by the processor, configure the server to:
receive an inbound message from the financial source computing device providing notice of a failed payment on a failure date, the failed payment being a scheduled payment from the financial source associated with the loan,
determine whether a payment retry condition is satisfied,
determine a payment retry date based on the rule table in response to the payment retry condition being satisfied, and
communicate the payment retry date as an outbound message to the buyer computing device via the external communication port,
wherein the payment retry date is determined based on comparing a recurring predetermined preferred payment date to the failure date and selecting a next instance of the recurring predetermined preferred payment date that is greater than a minimum delay period from the failure date,
wherein the outbound messages include a message provided to the buyer computing device to direct the buyer computing device to display a retry cancel button, the retry cancel button being selectable by the buyer to cancel the payment retry date.

### Claim 2 (depends on 1)

The server of claim 1, wherein the program instructions further configure the server to add the failed payment to a tracked number of prior failed payments associated with the loan to determine a total number of failed payments,
wherein the payment retry condition comprises a retry limit, and
wherein the payment retry condition is satisfied responsive to the total number of failed payments being less than the retry limit.

### Claim 3 (depends on 1)

The server of claim 1, wherein the payment retry condition comprises the failed payment being determined to be associated with a scheduled payment or an autopay function.

### Claim 4 (depends on 1)

The server of claim 1, wherein the payment retry condition comprises the failure date being within a predetermined time period.

### Claim 5 (depends on 1)

The server of claim 1, wherein the recurring predetermined preferred payment date is Friday, and
wherein the minimum delay period is three days.

### Claim 6 (depends on 1)

The server of claim 1, wherein the recurring predetermined preferred payment date is the 15th day of a month or a last day of the month, and
wherein the minimum delay period is three days.

### Claim 7 (depends on 1)

The server of claim 1, wherein outbound messages further include instructions to the buyer computing device to direct the buyer computing device to remove the retry cancel button within a predetermined time before the payment retry date to remove an ability of the buyer to cancel the payment retry date.

### Claim 8 (depends on 1)

The server of claim 1, further comprising modifying the communicating the payment retry date to include a suggested resolution to the buyer along with the payment reentry date.

### Claim 9 (depends on 1)

The server of claim 1, wherein the program instructions include instructions to modify the determining the payment retry date based on an error code.

### Claim 10 (depends on 9)

The server of claim 9, wherein modifying the determining the payment retry date comprises determining no payment retry date and canceling the communicating the payment retry date based on the error code.

### Claim 11 (depends on 1)

The server of claim 1, wherein the rule table is constructed based on research regarding characteristics of consumers.

### Claim 12 (depends on 1)

The server of claim 1, wherein the program instructions further configure the server to conduct a payment retry on the payment retry date via the financial source.

### Claim 13 (depends on 12)

The server of claim 12, wherein the program instructions further configure the server to check a status of the loan after the communicating the payment retry date and prior to the payment retry date, and cancel the payment retry based on the status of the loan.

### Claim 14 (depends on 13)

The server of claim 13, wherein the status of the loan indicates a change in a loan amount since the failure date.

### Claim 15 (depends on 12)

The server of claim 12, wherein the program instructions further configure the server to communicate with the financial source computing device to check a balance of an account of the buyer at the financial source after the communicating the payment retry date and prior to the payment retry date, and cancel the payment retry based on the balance of the account.

### Claim 16 (depends on 1)

The server of claim 1, wherein the program instructions further configure the server to conduct a payment retry on the payment retry date via a first financial instrument associated with the buyer.

### Claim 17 (depends on 16)

The server of claim 16, wherein the program instructions further configure the server to conduct an additional payment retry on the payment retry date via a second financial instrument associated with the buyer.

### Claim 18 (depends on 17)

The server of claim 17, wherein the program instructions further configure the server to conduct a payment retry on the payment retry date, and schedule a subsequent retry date if the payment retry is not successful on the payment retry date.

### Claim 19 (depends on 18)

The server of claim 18, wherein the program instructions further configure the server to limit a number of retries per payment instrument in a given period of time.

### Claim 20 (depends on 18)

The server of claim 18, wherein the program instructions further configure the server to limit a number of retries in a given period of time.
