Systems and methods for establishing a pull payment relationship

Patent metadata

Field	Value
Publication number	US-11734657-B1
Application number	US-202217963115-A
Country	US
Kind code	B1
Filing date	Oct 10, 2022
Priority date	Oct 3, 2016
Publication date	Aug 22, 2023
Grant date	Aug 22, 2023

Abstract

A method includes generating a transaction code associated with a payee; generating and providing a payee device token to a payee user device; receiving an indication of a contact or a near-contact event between the payee user device and a payor user device; receiving from the payor user device, the transaction code associated with the payee and a transaction code associated with the payor, the transaction codes exchanged during the contact or near-contact event; establishing a payment relationship between the payee and the payor responsive to receiving the indication and the transaction codes from the payor user device; receiving a payment request; determining that the payment request originated from the user device identified by the payee device token, and that the received transaction codes contained in the payment request match stored transaction codes of the payee and the payor contained in a database; and processing the received payment request.

First claim

What is claimed:

1. A method comprising:
generating and providing, by a computing system, a transaction code associated with a payee to a user device of the payee;
generating and providing, by the computing system, a payee device token to the user device of the payee;
generating and providing, by the computing system, a transaction code associated with a payor to a user device of the payor;
receiving, by the computing system, an indication of a contact or a near-contact event between the user device associated with the payee and the user device associated with the payor;
receiving, by the computing system and from the user device associated with the payor, the transaction code associated with the payee and the transaction code associated with the payor;
establishing, by the computing system, a payment relationship between the payee and the payor responsive to receiving the indication and the transaction codes from the user device associated with the payor;
receiving, by the computing system, a payment request from the user device associated with the payee, wherein the payment request includes the payee device token;
determining, by the computing system, that the payment request originated from the user device identified by the payee device token, and that the received transaction codes contained in the payment request match stored transaction codes of the payee and the payor contained in a database of the computing system; and
processing, by the computing system, the received payment request.

2. The method of claim 1 , wherein the contact or the near-contact event is a near field communication (NFC).

3. The method of claim 1 , wherein the transaction code of the payee and the transaction code of the payor are tokenized.

4. The method of claim 1 , further comprising:
registering, by the computing system, the payee for a pull payment service; and
registering, by the computing system, the payor for the pull payment service.

5. The method of claim 1 , further comprising establishing rules governing the payment relationship between the payee and the payor.

6. The method of claim 5 , further comprising:
receiving, by the computing system, the payment request from the payee requesting a payment from the payor;
determining, by the computing system, whether the payment request conforms to the rules governing the payment relationship;
declining, by the computing system, the payment request in response to determining that the payment request does not conform to the rules; and
fulfilling, by the computing system, the payment request in response to determining that the payment request conforms to the rules.

7. The method of claim 5 , wherein the rules define at least one of an amount, a limit, a time/date, and a frequency of a payment.

8. The method of claim 5 , wherein the rules provide that an approval from the payor or a third party is required before making a payment.

9. The method of claim 8 , further comprising:
determining, by the computing system, whether the payment request is approved by the payor or the third party as specified in the rules;
declining, by the computing system, the payment request in response to determining that the payment request is declined by the payor or the third party; and
fulfilling, by the computing system, the payment request in response to determining that the payment request is approved by the payor or the third party.

10. The method of claim 8 , further comprising:
determining, by the computing system, that the payment request is held off by the payor or the third party;
transferring, by the computing system, funds from an account associated with the payor to a holding account at the computing system;
transferring, by the computing system, the funds from the holding account to an account associated with the payee upon receiving an approval by the payor or the third party; and
transferring, by the computing system, the funds back from the holding account to the account associated with the payor upon receiving a declination by the payor or the third party.

11. The method of claim 1 , further comprising:
receiving, by the computing system, a priority value from the payee specifying a hierarchy of a plurality of accounts of the payee; and wherein
processing, by the computing system, the received payment request comprises transferring funds from an account of the payor to an account of the payee based on the hierarchy of the plurality of accounts of the payee indicated by the priority value.

12. The method of claim 1 , further comprising:
storing, by the computing system in a payment database, the transaction code of the payee linked to the transaction code of the payor as part of the established payment relationship; and
restricting, by the computing system, the established payment relationship between the payor and the payee to approving payment requests from only the user device identified by the payee device token.

13. A computing system comprising:
at least one processing circuit comprising at least one processor coupled to at least one memory device, the at least one processing circuit structured to:
generate and provide a transaction code associated with a payee to a user device of the payee;
generate and provide a payee device token to the user device of the payee;
generate and provide a transaction code associated with a payor to a user device of the payor;
receive an indication of a contact or a near-contact event between the user device associated with the payee and the user device associated with the payor;
receive from the user device associated with the payor, the transaction code associated with the payee and the transaction code associated with the payor;
establish a relationship between the payee and the payor responsive to receiving the indication and the transaction codes from the user device associated with the payor;
receive a payment request from the user device associated with the payee, wherein the payment request includes the payee device token;
determine that the payment request originated from the user device identified by the payee device token, and that the received transaction codes contained in the payment request match stored transaction codes of the payee and the payor contained in a database of the computing system; and
process the received payment request.

14. The computing system of claim 13 , wherein the contact or the near-contact event is a near field communication (NFC).

15. The computing system of claim 13 , wherein the processor is further configured to establish rules governing the payment relationship between the payee and the payor.

16. The computing system of claim 15 , wherein the rules provide that an approval from the payor or a third party is required before making a payment.

17. The computing system of claim 16 , wherein the processor is further configured to:
determine that the payment request is held off by the payor or the third party;
transfer funds from an account associated with the payor to a holding account at the computing system;
transfer the funds from the holding account to an account associated with the payee upon receiving an approval by the payor or the third party; and
transfer the funds back from the holding account to the account associated with the payor upon receiving a declination by the payor or the third party.

18. A non-transitory computer-readable media having computer-executable instructions embodied therein that, when executed by one or more processors of a computing system cause the one or more proc

Assignees

• Wells Fargo Bank Na

Inventors

• David Daniel
• Hartsell Jonathan A
• Kamp Heath
• Phelps Sarah W
• Sprague Philip
• Zikeli Christina

Classifications

• G06Q20/10 Primary

  specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems · CPC title

• G06Q20/3278

  RFID or NFC payments by means of M-devices · CPC title

• G06Q20/405 Primary

  Establishing or using transaction specific rules · CPC title

• G06Q20/14

  specially adapted for billing systems · CPC title