Systems and methods for establishing a pull payment relationship

Abstract

Systems and methods for establishing a pull payment relationship are disclosed. A method includes: generating, by a computing system, a transaction code associated with a payee; receiving, by the computing system and from a user device associated with a payor, the transaction code associated with the payee and a transaction code associated with the payor, the transaction codes exchanged during a contact or a near-contact event; establishing, by the computing system, a payment relationship between the payee and the payor responsive to receiving the transaction codes from the user device associated with the payor; receiving, by the computing system, a payment request; determining, by the computing system, that the received transaction codes contained in the payment request match the transaction codes of the payee and the payor stored by the computing system; and processing, by the computing system, the received payment request.

What is claimed: 
     
         1 . A method comprising:
 generating, by a computing system, a transaction code associated with a payee;   receiving, by the computing system and from a user device associated with a payor, the transaction code associated with the payee and a transaction code associated with the payor, the transaction codes exchanged during a contact or a near-contact event;   establishing, by the computing system, a payment relationship between the payee and the payor responsive to receiving the transaction codes from the user device associated with the payor;   receiving, by the computing system, a payment request;   determining, by the computing system, that the received transaction codes contained in the payment request match the transaction codes of the payee and the payor stored by 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:
 determining, by the computing system, whether the payment request conforms to the established 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 established rules; and   fulfilling, by the computing system, the payment request in response to determining that the payment request conforms to the established rules.   
     
     
         7 . The method of  claim 6 , wherein the established rules define at least one of an amount, a limit, a time, a date, or a frequency of a payment between the payor and the payee. 
     
     
         8 . The method of  claim 6 , wherein the established rules define a requirement of an approval from the payor or a third party before making a payment. 
     
     
         9 . The method of  claim 8 , further comprising:
 determining, by the computing system, that the payment request is delayed 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.   
     
     
         10 . 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 a transaction code associated with a payee; 
 receive, from a user device associated with a payor, the transaction code associated with the payee and a transaction code associated with the payor, the transaction codes exchanged during a contact or a near-contact event; 
 establish a payment relationship between the payee and the payor responsive to receiving the transaction codes from the user device associated with the payor; 
 receive a payment request; 
 determine that the received transaction codes contained in the payment request match the transaction codes of the payee and the payor stored by the computing system; and 
 process the received payment request. 
   
     
     
         11 . The computing system of  claim 10 , wherein the contact or the near-contact event is a near field communication (NFC). 
     
     
         12 . The computing system of  claim 11 , wherein the at least one processing circuit is further structured to establish rules governing a relationship between the payee and the payor. 
     
     
         13 . The computing system of  claim 12 , wherein the established rules define a requirement of an approval from the payor or a third party before making a payment. 
     
     
         14 . The computing system of  claim 13 , wherein the at least one processing circuit is further structured to:
 determine that the payment request is delayed 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.   
     
     
         15 . 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 processors to perform operations, the operations comprising:
 generating, by the computing system, a transaction code associated with a payee;   receiving, by the computing system and from a user device associated with a payor, the transaction code associated with the payee and a transaction code associated with the payor, the transaction codes exchanged during a contact or a near-contact event;   establishing, by the computing system, a payment relationship between the payee and the payor responsive to receiving the transaction codes from the user device associated with the payor;   receiving, by the computing system, a payment request;   determining, by the computing system, that the received transaction codes contained in the payment request match the transaction codes of the payee and the payor stored by the computing system; and   processing, by the computing system, the received payment request.   
     
     
         16 . The non-transitory computer-readable media of  claim 15 , wherein the contact or the near-contact event is a near field communication (NFC). 
     
     
         17 . The non-transitory computer-readable media of  claim 15 , wherein the transaction code of the payee and the transaction code of the payor are tokenized. 
     
     
         18 . The non-transitory computer-readable media of  claim 15 , wherein the operations further comprise establishing rules governing a relationship between the payee and the payor. 
     
     
         19 . The non-transitory computer-readable media of  claim 18 , wherein the established rules define at least one of an amount, a limit, a time, a date, or a frequency of a payment between the payor and the payee. 
     
     
         20 . The non-transitory computer-readable media of  claim 18 , wherein established rules define a requirement of an approval from the payor or a third party before making a payment.