Rules engine for applying rules from a reviewing network to signals from an originating network

1. A rules engine for providing stand-in authorization services for a payment transaction initiated by a cardholder with a merchant using a payment card over a payment network, said rules engine comprising a processor communicatively coupled to a memory device, wherein said rules engine is communicatively coupled to a reviewing network, said rules engine configured to:

store authorization rules within said memory device, wherein the authorization rules are provided on behalf of an issuer of the payment card for providing the stand-in authorization services;

receive a first authorization message from an originating network including authorization data for the payment transaction initiated by the cardholder and a stand-in flag requesting that the stand-in authorization services be provided for the payment transaction by the reviewing network on behalf of the issuer, wherein the originating network and the reviewing network are separate payment networks;

identify the issuer based on a transaction identifier included in the received authorization data for the payment transaction and retrieve the authorization rules for the identified issuer from said memory device;

generate a second authorization message indicating whether the payment transaction is authorized or declined on behalf of the issuer based upon the authorization rules and the authorization data, and without any additional input from the issuer, the second authorization message further including stand-in transaction data and updating the issuer regarding the stand-in authorization services performed on the payment transaction on behalf of the issuer; and

transmit the second authorization message to the merchant.

2. The rules engine of claim 1 , further configured to:

retrieve historical transaction data for an account associated with the payment card.

3. The rules engine of claim 2 , further configured to:

retrieve the rules from said memory device, the rules provided by the issuer associated with the payment card used to initiate the payment transaction; and apply the rules to the payment transaction and the historical transaction data.

4. The rules engine of claim 2 , wherein the authorization data includes a first monetary amount of the payment transaction, said rules engine is further configured to:

compare the first monetary amount and the historical transaction data to a single transaction limit for the payment card; and

indicate, in the second authorization message, whether the payment transaction is authorized or declined based on whether authorizing the payment transaction would cause the single transaction limit for the payment card to be exceeded.

5. The rules engine of claim 2 , further configured to:

compare a transaction number amount included in the historical transaction data to a threshold transaction number limit over a predefined time period; and

indicate, in the second authorization message, whether the payment transaction is authorized or declined based on whether authorizing the payment transaction would cause the threshold transaction number limit over the predefined time period to be exceeded.

6. The rules engine of claim 1 , wherein the authorization data includes a first monetary amount of the payment transaction, said rules engine is further configured to:

add the first monetary amount to a cumulative transaction amount; and

indicate, in the second authorization message, whether the payment transaction is authorized or declined based on whether authorizing the payment transaction would cause the cumulative transaction amount to exceed a predefined monetary limit over a predetermined time period.

7. The rules engine of claim 1 , wherein to generate the second authorization message, said rules engine is further configured to:

generate advice data indicating one of an authorization and a decline of the payment transaction by said rules engine, and a reason code indicating a reason for decline when the payment transaction is declined; and

transmit the advice data to the payment network with the second authorization message.

8. A method for providing stand-in authorization services for a payment transaction initiated by a cardholder with a merchant using a payment card over a payment network, said method is implemented by a rules engine comprising a processor communicatively coupled to a memory device, wherein the rules engine is communicatively coupled to a reviewing network, said method comprising:

storing authorization rules within said memory device, wherein the authorization rules are provided on behalf of an issuer of the payment card for providing the stand-in authorization services;

receiving a first authorization message from an originating network including authorization data for the payment transaction initiated by the cardholder and a stand-in flag requesting that the stand-in authorization services be provided for the payment transaction y the reviewing network on behalf of the issuer, wherein the originating network and the reviewing network are separate payment networks;

identifying the issuer based on a transaction identifier included in the received authorization data for the payment transaction and retrieve the authorization rules for the identified issuer from said memory device;

generating a second authorization message indicating whether the payment transaction is authorized or declined on behalf of the issuer based upon the authorization rules and the authorization data, and without any additional input from the issuer, the second authorization message further including stand-in transaction data and updating the issuer regarding the stand-in authorization services performed on the payment transaction on behalf of the issuer; and

transmitting the second authorization message to the merchant.

9. The method of claim 8 , further comprising:

retrieving historical transaction data for an account associated with the payment card.

10. The method of claim 9 , further comprising:

retrieving the rules from said memory device, the rules provided by the issuer associated with the payment card used to initiate the payment transaction; and

applying the rules to the payment transaction and the historical transaction data.

11. The method of claim 9 , wherein the authorization data includes a first monetary amount of the payment transaction, said method further comprising:

comparing the first monetary amount and the historical transaction data to a single transaction limit for the payment card; and

indicating, in the second authorization message, whether the payment transaction is authorized or declined based on whether authorizing the payment transaction would cause the single transaction limit for the payment card to be exceeded.

12. The method of claim 9 , wherein the authorization data includes a first monetary amount of the payment transaction, said method further comprising:

comparing a transaction number amount included in the historical transaction data to a threshold transaction number limit over a predefined time period; and

indicating, in the second authorization message, whether the payment transaction is authorized or declined based on whether authorizing the payment transaction would cause the threshold transaction number limit over the predefined time period to be exceeded.

13. The method of claim 9 , wherein the authorization data includes a first monetary amount of the payment transaction, said method further comprising:

adding the first monetary amount to a cumulative transaction amount; and indicating, in the second authorization message, whether the payment transaction is authorized or declined based on whether authorizing the payment transaction would cause the cumulative transaction amount to exceed a predefined monetary limit over a predetermined time period.

14. The method of claim 9 , wherein generating the second authorization message further comprises:

generating advice data indicating one of an authorization and a decline of the payment transaction by said rules engine, and a reason code indicating a reason for decline when the payment transaction is declined; and

transmitting the advice data to the payment network with the second authorization message.

15. A non-transitory computer-readable storage medium having computer-executable instructions embodied thereon for providing stand-in authorization services for a payment transaction initiated by a cardholder with a merchant using a payment card over a payment network, wherein when executed by a rules engine comprising a processor communicatively coupled to a memory device, wherein the rules engine is communicatively coupled to a reviewing network, the computer-executable instructions cause the rules engine to:

store authorization rules within said memory device, wherein the authorization rules are provided on behalf of an issuer of the payment card for providing the stand-in authorization services;

receive a first authorization message from an originating network including authorization data for the payment transaction initiated by the cardholder and a stand-in flag requesting that the stand-in authorization services be provided for the payment transaction by the reviewing network on behalf of the issuer, wherein the originating network and the reviewing network are separate payment networks;

identify the issuer based on a transaction identifier included in the received authorization data for the payment transaction and retrieve the authorization rules for the identified issuer from said memory device;

generate a second authorization message indicating whether the payment transaction is authorized or declined on behalf of the issuer based upon the authorization rules and the authorization data, and without any additional input from the issuer, the second authorization message further including stand-in transaction data and updating the issuer regarding the stand-in authorization services performed on the payment transaction on behalf of the issuer; and

transmit the second authorization message to the merchant.

16. The non-transitory computer-readable storage medium of claim 15 , wherein said computer-executable instructions further cause the rules engine to:

retrieve historical transaction data for an account associated with the payment card.

17. The non-transitory computer-readable storage medium of claim 16 , wherein said computer-executable instructions further cause the rules engine to:

retrieve the rules from said memory device, the rules provided by the issuer associated with the payment card used to initiate the payment transaction; and

apply the rules to the payment transaction and the historical transaction data.

18. The non-transitory computer-readable storage medium of claim 16 , wherein the authorization data includes a first monetary amount of the payment transaction, and wherein said computer-executable instructions further cause the rules engine to:

compare the first monetary amount and the historical transaction data to a single transaction limit for the payment card; and

indicate, in the second authorization message, whether the payment transaction is authorized or declined based on whether authorizing the payment transaction would cause the single transaction limit for the payment card to be exceeded.

19. The non-transitory computer-readable storage medium of claim 16 , wherein the authorization data includes a first monetary amount of the payment transaction, and wherein said computer-executable instructions further cause the rules engine to:

compare a transaction number amount included in the historical transaction data to a threshold transaction number limit over a predefined time period; and

indicate, in the second authorization message, whether the payment transaction is authorized or declined based on whether authorizing the payment transaction would cause the threshold transaction number limit over the predefined time period to be exceeded.