Systems and methods for management and recycling of payment transactions

Abstract

Systems and methods disclosed herein for managing recurring payment transactions. The recurring payment transaction can be based on account information stored by the merchant. When an initial payment transaction is not successful, a resubmission schedule is determined. The resubmission schedule identifies particular time slots within which subsequent payment transactions are to be submitted. The time slots are selected to increase the likelihood of a successful payment transaction.

1 - 22 . (canceled) 
     
     
         23 . A computer-implemented method for resubmitting transaction requests, comprising:
 receiving, at an acquirer computing system, a denial message from an issuer processor in response to a transmitted first authorization request including account information of an account associated with a payment card network and the issuer processor;   generating a resubmission schedule at the acquirer computing system, the resubmission schedule being based on one or more of a predefined date rule specifying a day of the month, a common payroll date, a predefined pattern rule specifying an amount of time to elapse, and a predefined time window rule specifying a time slot or a time of day, wherein the generated resubmission schedule is configured to reduce a number of transactions to obtain an approval from the issuer processor; and   transmitting, by the acquirer computing system, a second authorization request to the issuer processor based on the generated resubmission schedule.   
     
     
         24 . The computer-implemented method of  claim 23 , wherein the generated resubmission schedule is based on at least one transaction parameter comprising any of a method of payment, a Bank Identification Number (BIN), a Reason Response Code (RRC) received with the denial message, and a transaction amount. 
     
     
         25 . The computer-implemented method of  claim 24 , wherein the generated resubmission schedule identifies i) a day of the week for transmitting the second authorization request and ii) a time slot identifying a window of time of that day of the week. 
     
     
         26 . The computer-implemented method of  claim 24 , wherein the generated resubmission schedule identifies i) a day of the month for transmitting the second authorization request and ii) a time slot identifying a window of time of the day of the month for transmitting the second authorization request. 
     
     
         27 . The computer-implemented method of  claim 24 , wherein first authorization request is for a first payment transaction of a recurring billing arrangement, the recurring billing arrangement including the first payment transaction and one or more scheduled payment transactions, and
 wherein the generated resubmission schedule identifies i) a periodic schedule for resubmission of the second authorization request and ii) a time slot identifying a window of time of each day on the periodic schedule.   
     
     
         28 . The computer-implemented method of  claim 27 , wherein the recurring billing arrangement is based on an installment payment obligation. 
     
     
         29 . The computer-implemented method of  claim 27 , wherein the recurring billing arrangement is based on any of a subscription obligation and an installment payment obligation. 
     
     
         30 . The computer-implemented method of  claim 23 , wherein the time slot identifies a period of time determined based at least in part on a number of available time slots for a day. 
     
     
         31 . The computer-implemented method of  claim 23 , wherein the time slot is selected from a set of preferred time slots associated with the first authorization request. 
     
     
         32 . The computer-implemented method of  claim 23 ,
 wherein the time slot or time of day is selected based at least in part on time when transaction communication traffic is usually at a minimum.   
     
     
         33 . The computer-implemented method of  claim 23 , further comprising:
 receiving, at the acquirer computing system, a denial message from the issuer processor in response to the transmitted second authorization request; and   transmitting, by the acquirer computing system, a third authorization request to the issuer processor based on the generated resubmission schedule, wherein the third authorization request is for a second scheduled payment transaction of the one or more scheduled payment transactions.   
     
     
         34 . A non-transitory computer readable medium having instructions stored thereon which when executed by a processor cause the processor to:
 receive a denial message in response to a transmitted first authorization request including account information of an account associated with a payment card network and an issuer processor;   generate a resubmission schedule, the resubmission schedule being based on one or more of a predefined date rule specifying a day of the month, a common payroll date, a predefined pattern rule specifying an amount of time to elapse, and a predefined time window rule specifying a time slot or a time of day, wherein the generated resubmission schedule is configured to reduce a number of transactions to obtain an approval from the issuer processor; and   transmit a second authorization request to the issuer processor based on the generated resubmission schedule.   
     
     
         35 . The non-transitory computer readable medium of  claim 34 , wherein the generated resubmission schedule is based on at least one a response code received with the denial message and a Bank Identification Number (BIN) identified in the authorization request. 
     
     
         36 . The non-transitory computer readable medium of  claim 35 , wherein first authorization request is for a first payment transaction of a recurring billing arrangement, the recurring billing arrangement including the first payment transaction and one or more scheduled payment transactions, and
 wherein the generated resubmission schedule identifies any of: a day of the week, a day of the month, and a periodic schedule for transmitting the second authorization request.   
     
     
         37 . The non-transitory computer readable medium of  claim 36 , wherein the recurring billing arrangement is based on an installment payment obligation. 
     
     
         38 . The non-transitory computer readable medium of  claim 36 , wherein the recurring billing arrangement is based on a subscription obligation. 
     
     
         39 . An acquirer computing system for receiving authorization requests for a plurality of merchants and communicating with one or more payment networks, the acquirer computing system comprising a non-transitory computer readable medium having instructions stored thereon which when executed by a processor cause the processor to:
 receive a denial message from an issuer processor in response to a transmitted first authorization request including account information of an account associated with a payment card network and the issuer processor;   generate a resubmission schedule, the resubmission schedule being based on one or more of a predefined date rule specifying a day of the month, a common payroll date, a predefined pattern rule specifying an amount of time to elapse, and a predefined time window rule specifying a time slot or a time of day, wherein the generated resubmission schedule is configured to reduce a number of transactions to obtain an approval from the issuer processor; and   transmit a second authorization request to the issuer processor based on the generated resubmission schedule.   
     
     
         40 . The acquirer computing system of  claim 39 , wherein first authorization request is for a first payment transaction of a recurring billing arrangement, the recurring billing arrangement including the first payment transaction and one or more scheduled payment transactions, and
 wherein the generated resubmission schedule identifies one of: a day of the week, a day of the month, and a periodic schedule for transmitting the one or more scheduled payment transactions.   
     
     
         41 . The acquirer computing system of  claim 39 , wherein the time slot or period of time is determined based at least in part on analysis of data of one or more payment transactions having parameters that are at least similar to parameters associated with the transmitted first authorization request. 
     
     
         42 . The acquirer computing system of  claim 39 , wherein the generated resubmission schedule identifies a plurality of time slots, wherein the second authorization request is to be submitted in at least one of the plurality of time slots.