| JP4397437 | IC card |
| JP4615474 | Communication terminal, user data movement system and user data movement method |
| WO/2014/027285 | GLOBAL LOTTERY |
CHIANG ALEXANDER (US)
YEE MILLIE (US)
| US20030195858A1 | 2003-10-16 | |||
| US20030126094A1 | 2003-07-03 |
| THE INVENTION CLAIMED IS: 1. A computer-implemented method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor, transaction data associated with a transaction in a transaction processing network initiated with a portable financial device, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; determining, with at least one processor, an accessibility of at least one system in the transaction processing network; in response to a determination that the at least one system in the transaction processing network is accessible, transmitting, with at least one processor, the transaction data associated with the transaction to the at least one system and receiving, from the at least one system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorizing the transaction based on the decision data. 2. The computer-implemented method of claim 1 , wherein the plurality of systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof. 3. The computer-implemented method of claim 1 , wherein accessing the decision data at the decision system comprises transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction, and wherein the transaction is authorized in response to the score satisfying a threshold score. 4. The computer-implemented method of claim 1 , further comprising: determining, with at least one processor, a score associated with the transaction based on the decision data and the transaction data; and authorizing, with at least one processor, the transaction in response to the score satisfying a threshold score. 5. The computer-implemented method of claim 1 , wherein the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof. 6. The computer-implemented method of claim 1 , further comprising: updating, with at least one processor, the decision data at the decision system based at least partially on the transaction data. 7. A computer-implemented method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network; receiving, with at least one processor from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network; processing, with at least one processor, the transaction based on the transaction data and the decision data; and providing, with at least one processor, authorization data associated with the at least one transaction to the system in the transaction processing network. 8. The computer-implemented method of claim 7, further comprising: receiving, with at least one processor, at least a portion of the decision data from a remote system outside the communication path of the transaction processing network. 9. A computer-implemented method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor, transaction data associated with a transaction initiated with a portable financial device at a merchant system; transmitting, with at least one processor, the transaction data associated with the transaction to a transaction processing network, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; receiving, with at least one processor, an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network; in response to receiving the indication that the transaction is declined by the transaction processing network, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device; and authorizing, with at least one processor, the transaction based on the decision data. 10. A system for backup transaction processing for electronic payment transactions comprising: a computer system of a plurality of computer systems in a transaction processing network, wherein the transaction processing network comprises the plurality of computer systems in a communication path for processing a transaction initiated with a portable financial device, the computer system comprising at least one processor programmed or configured to: receive transaction data associated with the transaction in the transaction processing network; determine an accessibility of at least one other computer system in the transaction processing network; in response to a determination that the at least one other computer system in the transaction processing network is accessible, transmit the transaction data associated with the transaction to the at least one other computer system and receive, from the at least one other computer system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorizing the transaction based on the decision data. 1 1. The system of claim 10, wherein the plurality of computer systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof. 12. The system of claim 10, wherein the computer system is further programmed or configured to: access the decision data at the decision system by transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction; and authorize the transaction in response to the score satisfying a threshold score. 13. The system of claim 10, wherein the computer system is further programmed or configured to: determine a score associated with the transaction based on the decision data and the transaction data; and authorize the transaction in response to the score satisfying a threshold score. 14. The system of claim 10, wherein the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more computer systems of the plurality of computer systems in the transaction processing network, or any combination thereof. 15. The system of claim 10, wherein the computer system is further programmed or configured to: update the decision data at the decision system based at least partially on the transaction data. 16. A computer program product for backup transaction processing for electronic payment transactions, the computer program product comprising at least one non-transitory computer-readable medium comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to: receive transaction data associated with a transaction in a transaction processing network initiated with a portable financial device, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; determine an accessibility of at least one system in the transaction processing network; in response to a determination that the at least one system in the transaction processing network is accessible, transmit the transaction data associated with the transaction to the at least one system and receive, from the at least one system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, access decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorize the transaction based on the decision data. 17. The computer program product of claim 16, wherein the plurality of systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof. 18. The computer program product of claim 16, wherein the one or more instructions further cause the at least one processor to: access the decision data at the decision system by transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction; and authorize the transaction in response to the score satisfying a threshold score. 19. The computer program product of claim 16, wherein the one or more instructions further cause the at least one processor to: determine a score associated with the transaction based on the decision data and the transaction data; and authorize the transaction in response to the score satisfying a threshold score. 20. The computer program product of claim 16, wherein the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof. |
BACKGROUND OF THE INVENTION
1. Field of the Invention
[0001] This invention relates generally to systems, devices, products, apparatus, and methods that are used for transaction processing, and in one particular embodiment, to a system, product, and method for backup transaction processing for electronic payment transactions.
2. Technical Considerations
[0002] The usage of electronic payments is increasing. Merchants, acquirers, transaction service providers, and issuers each have a vested interest in providing accurate, reliable, and dependable electronic payment transaction processing. For example, merchants may not be able to rely on customers using alternative methods of payment, such as cash and/or checks, to conduct transactions. As an example, many customers no longer carry checkbooks and/or sufficient amounts of cash for conducting transactions.
[0003] Flowever, a merchant, an acquirer, a transaction service provider, and/or an issuer may not be able to individually or independently provide or ensure accurate, reliable, and/or dependable electronic payment transaction processing. For example, a failure at or communication loss with one of the merchant, the acquirer, the transaction service provider, and/or the issuer may cause a failure in processing of an electronic payment transaction. As an example, the failure of an entire electronic payment transaction processing network or function can be the result of a problem with any of the many stakeholders in a processing and/or communication chain of the network or function. Although it may have previously been an inconvenience when problems with payment processing arose, because of the increasing proportion of electronic payments, sales may now come to a virtual standstill when electronic payments are not working, and what used to be an occasional inconvenience to a cardholder, is expanded to become impactful lost sales to the merchant, and lost business to the acquirer, the transaction service provider, and the issuer. SUMMARY OF THE INVENTION
[0004] Accordingly, provided are improved systems, devices, products, apparatus, and/or methods for backup electronic payment transaction processing.
[0005] According to a non-limiting embodiment or aspect, provided is a method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor, transaction data associated with a transaction in a transaction processing network initiated with a portable financial device, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; determining, with at least one processor, an accessibility of at least one system in the transaction processing network; in response to a determination that the at least one system in the transaction processing network is accessible, transmitting, with at least one processor, the transaction data associated with the transaction to the at least one system and receiving, from the at least one system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorizing the transaction based on the decision data.
[0006] In some non-limiting embodiments or aspects, the plurality of systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof.
[0007] In some non-limiting embodiments or aspects, accessing the decision data at the decision system comprises transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction, and wherein the transaction is authorized in response to the score satisfying a threshold score.
[0008] In some non-limiting embodiments or aspects, the method further comprises determining, with at least one processor, a score associated with the transaction based on the decision data and the transaction data; and authorizing, with at least one processor, the transaction in response to the score satisfying a threshold score. [0009] In some non-limiting embodiments or aspects, the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof.
[0010] In some non-limiting embodiments or aspects, the method further comprises updating, with at least one processor, the decision data at the decision system based at least partially on the transaction data.
[0011] According to a non-limiting embodiment or aspect, provided is a computer- implemented method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network; receiving, with at least one processor from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network; processing, with at least one processor, the transaction based on the transaction data and the decision data; and providing, with at least one processor, authorization data associated with the at least one transaction to the system in the transaction processing network.
[0012] In some non-limiting embodiments or aspects, the method further comprises receiving, with at least one processor, at least a portion of the decision data from a remote system outside the communication path of the transaction processing network.
[0013] According to a non-limiting embodiment or aspect, provided is a computer- implemented method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor, transaction data associated with a transaction initiated with a portable financial device at a merchant system; transmitting, with at least one processor, the transaction data associated with the transaction to a transaction processing network, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; receiving, with at least one processor, an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network; in response to receiving the indication that the transaction is declined by the transaction processing network, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device; and authorizing, with at least one processor, the transaction based on the decision data.
[0014] According to a non-limiting embodiment or aspect, provided is a system for backup transaction processing for electronic payment transactions comprising: a computer system of a plurality of computer systems in a transaction processing network, wherein the transaction processing network comprises the plurality of computer systems in a communication path for processing a transaction initiated with a portable financial device, the computer system comprising at least one processor programmed or configured to: receive transaction data associated with the transaction in the transaction processing network; determine an accessibility of at least one other computer system in the transaction processing network; in response to a determination that the at least one other computer system in the transaction processing network is accessible, transmit the transaction data associated with the transaction to the at least one other computer system and receive, from the at least one other computer system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorizing the transaction based on the decision data.
[0015] In some non-limiting embodiments or aspects, the plurality of computer systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof.
[0016] In some non-limiting embodiments or aspects, the computer system is further programmed or configured to: access the decision data at the decision system by transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction; and authorize the transaction in response to the score satisfying a threshold score.
[0017] In some non-limiting embodiments or aspects, the computer system is further programmed or configured to: determine a score associated with the transaction based on the decision data and the transaction data; and authorize the transaction in response to the score satisfying a threshold score.
[0018] In some non-limiting embodiments or aspects, the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more computer systems of the plurality of computer systems in the transaction processing network, or any combination thereof.
[0019] In some non-limiting embodiments or aspects, the computer system is further programmed or configured to: update the decision data at the decision system based at least partially on the transaction data.
[0020] According to a non-limiting embodiment or aspect, provided is a system for backup transaction processing for electronic payment transactions comprising: a computer system comprising at least one processor programmed or configured to: receive, from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network; receive, from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network; process the transaction based on the transaction data and the decision data; and provide authorization data associated with the at least one transaction to the system in the transaction processing network.
[0021] In some non-limiting embodiments or aspects, the computer system is further programmed or configured to: receive at least a portion of the decision data from a remote system outside the communication path of the transaction processing network.
[0022] According to a non-limiting embodiment or aspect, provided is a system for backup transaction processing for electronic payment transactions, comprising: a merchant system of a plurality of systems in a transaction processing network, wherein the transaction processing network comprises the plurality of computer systems in a communication path for processing a transaction initiated with a portable financial device, the merchant system comprising at least one processor programmed or configured to: receive transaction data associated with a transaction initiated with a portable financial device; transmit the transaction data associated with the transaction to the transaction processing network; receive an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network; in response to receiving the indication that the transaction is declined by the transaction processing network, access decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device; and authorize the transaction based on the decision data.
[0023] According to a non-limiting embodiment or aspect, provided is a computer program product for backup transaction processing for electronic payment transactions, the computer program product comprising at least one non-transitory computer-readable medium comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to: receive transaction data associated with a transaction in a transaction processing network initiated with a portable financial device, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; determine an accessibility of at least one system in the transaction processing network; in response to a determination that the at least one system in the transaction processing network is accessible, transmit the transaction data associated with the transaction to the at least one system and receive, from the at least one system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, access decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorize the transaction based on the decision data.
[0024] In some non-limiting embodiments or aspects, the plurality of systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof.
[0025] In some non-limiting embodiments or aspects, the one or more instructions further cause the at least one processor to: access the decision data at the decision system by transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction; and authorize the transaction in response to the score satisfying a threshold score.
[0026] In some non-limiting embodiments or aspects, the one or more instructions further cause the at least one processor to: determine a score associated with the transaction based on the decision data and the transaction data; and authorize the transaction in response to the score satisfying a threshold score.
[0027] In some non-limiting embodiments or aspects, the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof.
[0028] In some non-limiting embodiments or aspects, the one or more instructions further cause the at least one processor to: update the decision data at the decision system based at least partially on the transaction data.
[0029] According to a non-limiting embodiment or aspect, provided is a computer program product for backup transaction processing for electronic payment transactions, the computer program product comprising at least one non-transitory computer-readable medium comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to: receive, from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network; receive, from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network; process the transaction based on the transaction data and the decision data; and provide authorization data associated with the at least one transaction to the system in the transaction processing network.
[0030] In some non-limiting embodiments or aspects, the one or more instructions further cause the at least one processor to: receive at least a portion of the decision data from a remote system outside the communication path of the transaction processing network.
[0031] According to a non-limiting embodiment or aspect, provided is a computer program product for backup transaction processing for electronic payment transactions, the computer program product comprising at least one non-transitory computer-readable medium comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to: receive transaction data associated with a transaction initiated with a portable financial device at a merchant system; transmit the transaction data associated with the transaction to a transaction processing network, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; receive an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network; in response to receiving the indication that the transaction is declined by the transaction processing network, access decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device; and authorize the transaction based on the decision data.
[0032] Further embodiments or aspects are set forth in the following numbered clauses:
[0033] Clause 1. A computer-implemented method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor, transaction data associated with a transaction in a transaction processing network initiated with a portable financial device, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; determining, with at least one processor, an accessibility of at least one system in the transaction processing network; in response to a determination that the at least one system in the transaction processing network is accessible, transmitting, with at least one processor, the transaction data associated with the transaction to the at least one system and receiving, from the at least one system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorizing the transaction based on the decision data.
[0034] Clause 2. The computer-implemented method of clause 1 , wherein the plurality of systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof.
[0035] Clause 3. The computer-implemented method of clauses 1 and 2, wherein accessing the decision data at the decision system comprises transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction, and wherein the transaction is authorized in response to the score satisfying a threshold score.
[0036] Clause 4. The computer-implemented method of any of clauses 1 -3, further comprising: determining, with at least one processor, a score associated with the transaction based on the decision data and the transaction data; and authorizing, with at least one processor, the transaction in response to the score satisfying a threshold score.
[0037] Clause 5. The computer-implemented method of any of clauses 1 -4, wherein the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof. [0038] Clause 6. The computer-implemented method of any of clauses 1 -5, further comprising: updating, with at least one processor, the decision data at the decision system based at least partially on the transaction data.
[0039] Clause 7. A computer-implemented method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network; receiving, with at least one processor from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network; processing, with at least one processor, the transaction based on the transaction data and the decision data; and providing, with at least one processor, authorization data associated with the at least one transaction to the system in the transaction processing network.
[0040] Clause 8. The computer-implemented method of clause 7, further comprising: receiving, with at least one processor, at least a portion of the decision data from a remote system outside the communication path of the transaction processing network.
[0041] Clause 9. A computer-implemented method for backup transaction processing for electronic payment transactions, the method comprising: receiving, with at least one processor, transaction data associated with a transaction initiated with a portable financial device at a merchant system; transmitting, with at least one processor, the transaction data associated with the transaction to a transaction processing network, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; receiving, with at least one processor, an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network; in response to receiving the indication that the transaction is declined by the transaction processing network, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device; and authorizing, with at least one processor, the transaction based on the decision data.
[0042] Clause 10. A system for backup transaction processing for electronic payment transactions comprising: a computer system of a plurality of computer systems in a transaction processing network, wherein the transaction processing network comprises the plurality of computer systems in a communication path for processing a transaction initiated with a portable financial device, the computer system comprising at least one processor programmed or configured to: receive transaction data associated with the transaction in the transaction processing network; determine an accessibility of at least one other computer system in the transaction processing network; in response to a determination that the at least one other computer system in the transaction processing network is accessible, transmit the transaction data associated with the transaction to the at least one other computer system and receive, from the at least one other computer system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorizing the transaction based on the decision data.
[0043] Clause 1 1. The system of clause 10, wherein the plurality of computer systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof.
[0044] Clause 12. The system of clauses 10 and 1 1 , wherein the computer system is further programmed or configured to: access the decision data at the decision system by transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction; and authorize the transaction in response to the score satisfying a threshold score.
[0045] Clause 13. The system of any of clauses 10-12, wherein the computer system is further programmed or configured to: determine a score associated with the transaction based on the decision data and the transaction data; and authorize the transaction in response to the score satisfying a threshold score.
[0046] Clause 14. The system of any of clauses 10-13, wherein the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more computer systems of the plurality of computer systems in the transaction processing network, or any combination thereof.
[0047] Clause 15. The system of any of clauses 10-14, wherein the computer system is further programmed or configured to: update the decision data at the decision system based at least partially on the transaction data.
[0048] Clause 16. A system for backup transaction processing for electronic payment transactions comprising: a computer system comprising at least one processor programmed or configured to: receive, from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network; receive, from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network; process the transaction based on the transaction data and the decision data; and provide authorization data associated with the at least one transaction to the system in the transaction processing network.
[0049] Clause 17. The system of clause 16, wherein the computer system is further programmed or configured to: receive at least a portion of the decision data from a remote system outside the communication path of the transaction processing network.
[0050] Clause 18. A system for backup transaction processing for electronic payment transactions, comprising: a merchant system of a plurality of systems in a transaction processing network, wherein the transaction processing network comprises the plurality of computer systems in a communication path for processing a transaction initiated with a portable financial device, the merchant system comprising at least one processor programmed or configured to: receive transaction data associated with a transaction initiated with a portable financial device; transmit the transaction data associated with the transaction to the transaction processing network; receive an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network; in response to receiving the indication that the transaction is declined by the transaction processing network, access decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device; and authorize the transaction based on the decision data.
[0051] Clause 19. A computer program product for backup transaction processing for electronic payment transactions, the computer program product comprising at least one non-transitory computer-readable medium comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to: receive transaction data associated with a transaction in a transaction processing network initiated with a portable financial device, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; determine an accessibility of at least one system in the transaction processing network; in response to a determination that the at least one system in the transaction processing network is accessible, transmit the transaction data associated with the transaction to the at least one system and receive, from the at least one system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, access decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorize the transaction based on the decision data.
[0052] Clause 20. The computer program product of clause 19, wherein the plurality of systems comprises two or more of the following systems: a merchant system, an acquirer system, a transaction service provider system, an issuer system, or any combination thereof.
[0053] Clause 21 . The computer program product of clauses 19 and 20, wherein the one or more instructions further cause the at least one processor to: access the decision data at the decision system by transmitting the transaction data to the decision system, and receiving the decision data from the decision system, wherein the decision data comprises a score associated with the transaction; and authorize the transaction in response to the score satisfying a threshold score.
[0054] Clause 22. The computer program product of any of clauses 19-21 , wherein the one or more instructions further cause the at least one processor to: determine a score associated with the transaction based on the decision data and the transaction data; and authorize the transaction in response to the score satisfying a threshold score.
[0055] Clause 23. The computer program product of any of clauses 19-22, wherein the decision data is associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof.
[0056] Clause 24. The computer program product of any of clauses 19-23, wherein the one or more instructions further cause the at least one processor to: update the decision data at the decision system based at least partially on the transaction data.
[0057] Clause 25. A computer program product for backup transaction processing for electronic payment transactions, the computer program product comprising at least one non-transitory computer-readable medium comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to: receive, from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network; receive, from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network; process the transaction based on the transaction data and the decision data; and provide authorization data associated with the at least one transaction to the system in the transaction processing network. [0058] Clause 26. The computer program product of clause 25, wherein the one or more instructions further cause the at least one processor to: receive at least a portion of the decision data from a remote system outside the communication path of the transaction processing network.
[0059] Clause 27. A computer program product for backup transaction processing for electronic payment transactions, the computer program product comprising at least one non-transitory computer-readable medium comprising one or more instructions that, when executed by at least one processor, cause the at least one processor to: receive transaction data associated with a transaction initiated with a portable financial device at a merchant system; transmit the transaction data associated with the transaction to a transaction processing network, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; receive an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network; in response to receiving the indication that the transaction is declined by the transaction processing network, access decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device; and authorize the transaction based on the decision data.
[0060] These and other features and characteristics of the present invention, as well as the methods of operation and functions of the related elements of structures and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and the claims, the singular form of “a,”“an,” and“the” include plural referents unless the context clearly dictates otherwise. BRIEF DESCRIPTION OF THE DRAWINGS
[0061] Additional advantages and details of the invention are explained in greater detail below with reference to the exemplary embodiments or aspects that are illustrated in the accompanying schematic figures, in which:
[0062] FIG. 1 is a diagram of a non-limiting embodiment or aspect of an environment in which systems, devices, products, apparatus, and/or methods, described herein, may be implemented according to the principles of the present invention;
[0063] FIG. 2 is a diagram of a non-limiting embodiment or aspect of components of one or more devices of FIG. 1 ;
[0064] FIG. 3 is a flowchart of a non-limiting embodiment or aspect of a process for backup electronic payment transaction processing;
[0065] FIG. 4 is a flowchart of a non-limiting embodiment or aspect of a process for backup electronic payment transaction processing;
[0066] FIG. 5 is a flowchart of a non-limiting embodiment or aspect of a process for backup electronic payment transaction processing;
[0067] FIG. 6 is a diagram of an implementation of a non-limiting embodiment or aspect of one or more of the processes shown in FIGS. 3-5;
[0068] FIG. 7 is a diagram of an implementation of a non-limiting embodiment or aspect of one or more of the processes shown in FIGS. 3-5;
[0069] FIG. 8 is a diagram of an implementation of a non-limiting embodiment or aspect of one or more of the processes shown in FIGS. 3-5;
[0070] FIG. 9 is a diagram of an implementation of a non-limiting embodiment or aspect of one or more of the processes shown in FIGS. 3-5; and
[0071] FIG. 10 is a diagram of an implementation of a non-limiting embodiment or aspect of one or more of the processes shown in FIGS. 3-5.
DESCRIPTION OF THE INVENTION
[0072] For purposes of the description hereinafter, the terms “end,” “upper,” “lower,”“right,”“left,”“vertical,”“horizon tal,”“top,”“bottom,”“lateral,”“longitudinal, ” and derivatives thereof shall relate to the invention as it is oriented in the drawing figures. However, it is to be understood that the invention may assume various alternative variations and step sequences, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments or aspects of the invention. Hence, specific dimensions and other physical characteristics related to the embodiments or aspects of the embodiments or aspects disclosed herein are not to be considered as limiting unless otherwise indicated.
[0073] No aspect, component, element, structure, act, step, function, instruction, and/or the like used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles“a” and“an” are intended to include one or more items, and may be used interchangeably with“one or more” and“at least one.” Furthermore, as used herein, the term“set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with“one or more” or“at least one.” Where only one item is intended, the term“one” or similar language is used. Also, as used herein, the terms“has,”“have,”“having,” or the like are intended to be open-ended terms. Further, the phrase“based on” is intended to mean“based at least partially on” unless explicitly stated otherwise.
[0074] As used herein, the terms“communication” and“communicate” may refer to the reception, receipt, transmission, transfer, provision, and/or the like of information (e.g., data, signals, messages, instructions, commands, and/or the like). For one unit (e.g., a device, a system, a component of a device or system, combinations thereof, and/or the like) to be in communication with another unit means that the one unit is able to directly or indirectly receive information from and/or transmit information to the other unit. This may refer to a direct or indirect connection that is wired and/or wireless in nature. Additionally, two units may be in communication with each other even though the information transmitted may be modified, processed, relayed, and/or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit may be in communication with a second unit if at least one intermediary unit (e.g., a third unit located between the first unit and the second unit) processes information received from the first unit and communicates the processed information to the second unit. In some non-limiting embodiments or aspects, a message may refer to a network packet (e.g., a data packet and/or the like) that includes data. It will be appreciated that numerous other arrangements are possible. It will be appreciated that numerous other arrangements are possible.
[0075] As used herein, the terms“issuer institution,”“portable financial device issuer,”“issuer,” or“issuer bank” may refer to one or more entities that provide one or more accounts to a user (e.g., customer, consumer, and/or the like) for conducting transactions (e.g., payment transactions), such as initiating credit card payment transactions and/or debit card payment transactions. For example, an issuer institution may provide an account identifier, such as a personal account number (PAN), to a user that uniquely identifies one or more accounts associated with that user. The account identifier may be embodied on a portable financial device, such as a physical financial instrument (e.g., a payment card), and/or may be electronic and used for electronic payments. In some non-limiting embodiments or aspects, an issuer institution may be associated with a bank identification number (BIN) that uniquely identifies the issuer institution. As used herein“issuer institution system” may refer to one or more computer systems operated by or on behalf of an issuer institution, such as a server computer executing one or more software applications. For example, an issuer institution system may include one or more authorization servers for authorizing a payment transaction.
[0076] As used herein, the term“account identifier” may refer to one or more types of identifiers associated with a user account (e.g., an account identifier, a PAN, a card number, a payment card number, a token, and/or the like). In some non limiting embodiments or aspects, an issuer institution may provide an account identifier (e.g., a PAN, a token, and/or the like) to a user that uniquely identifies one or more accounts associated with that user. The account identifier may be embodied on a physical financial instrument (e.g., a portable financial device, a payment card, a credit card, a debit card, and/or the like) and/or may be electronic information communicated to the user that the user may use for electronic payment transactions. In some non-limiting embodiments or aspects, the account identifier may be an original account identifier, where the original account identifier is provided to a user at the creation of the account associated with the account identifier. In some non-limiting embodiments or aspects, the account identifier may be an account identifier (e.g., a supplemental account identifier) that is provided to a user after the original account identifier is provided to the user. For example, if the original account identifier is forgotten, stolen, and/or the like, a supplemental account identifier may be provided to the user. In some non-limiting embodiments or aspects, an account identifier may be directly or indirectly associated with an issuer institution such that an account identifier may be a token that maps to a PAN or other type of identifier. Account identifiers may be alphanumeric, any combination of characters and/or symbols, and/or the like.
[0077] As used herein, the term“merchant” may refer to one or more entities (e.g., operators of retail businesses) that provide goods and/or services, and/or access to goods and/or services, to a user based on a transaction, such as a payment transaction. As used herein“merchant system” may refer to one or more computer systems operated by or on behalf of a merchant, such as a server executing one or more software applications. As used herein, the term“product” may refer to one or more goods and/or services offered by a merchant.
[0078] As used herein, a“point-of-sale (POS) device” may refer to one or more devices, which may be used by a merchant to conduct a transaction (e.g., a payment transaction) and/or process a transaction. For example, a POS device may include one or more computers, peripheral devices, card readers, near-field communication (NFC) receivers, radio frequency identification (RFID) receivers, and/or other contactless transceivers or receivers, contact-based receivers, payment terminals, computers, servers, input devices, and/or the like. As an example, a POS device may use a POS application installed on the POS device to receive, process, and/or provide data associated with conducting the transaction and/or processing the transaction.
[0079] As used herein, a“POS system” may refer to one or more computers and/or peripheral devices used by a merchant to conduct a transaction. For example, a POS system may include one or more POS devices, and/or other like devices that may be used to conduct a payment transaction. A POS system (e.g., a merchant POS system) may also include one or more server computers programmed or configured to process online payment transactions through webpages, mobile applications, and/or the like.
[0080] As used herein, the term“transaction service provider” may refer to an entity that receives transaction authorization requests from merchants or other entities and provides guarantees of payment, in some cases through an agreement between the transaction service provider and an issuer institution. For example, a transaction service provider may include a payment network, such as Visa®, MasterCard®, American Express®, or any other entity that processes transactions. As used herein“transaction service provider system” may refer to one or more computer systems operated by or on behalf of a transaction service provider, such as a transaction service provider system executing one or more software applications. A transaction service provider system may include one or more processors and, in some non-limiting embodiments or aspects, may be operated by or on behalf of a transaction service provider.
[0081] As used herein, the term “portable financial device” may refer to a payment card (e.g., a credit card, a debit card, an ATM card, and/or the like), a gift card, a smartcard, a payroll card, a healthcare card, a loyalty card, a merchant discount card, a security card, an access card, and/or the like. The portable financial device may include volatile or non-volatile memory to store information (e.g., an account identifier, a name of a user or holder of the account, and/or the like).
[0082] As used herein, the terms“client” and“client device” may refer to one or more client-side devices or systems, remote from a transaction service provider, used to initiate or facilitate a transaction. As an example, a“client device” may refer to one or more POS devices and/or POS systems used by a merchant. In some non-limiting embodiments or aspects, a client device may be any electronic device configured to communicate with one or more networks and initiate or facilitate transactions such as, but not limited to, one or more computers, portable computers (e.g., tablet computers), mobile devices (e.g., cellular phones, smartphones, wearable devices, such as watches, glasses, lenses, and/or clothing, PDAs, and/or the like), and/or other like devices. Moreover, a“client” may also refer to an entity, such as a merchant, that owns, utilizes, and/or operates a client device for initiating transactions with a transaction service provider.
[0083] As used herein, the term“server” may refer to one or more computing devices, such as processors, storage devices, and/or similar computer components that communicate with client devices and/or other computing devices over a network, such as the Internet or private networks, and, in some examples, facilitate communication among other servers and/or client devices. It will be appreciated that various other arrangements are possible. As used herein, the term“system” may refer to one or more computing devices or combinations of computing devices such as, but not limited to, processors, servers, client devices, software applications, and/or other like components. In addition, reference to“a server” or“a processor,” as used herein, may refer to a previously-recited server and/or processor that is recited as performing a previous step or function, a different server and/or processor, and/or a combination of servers and/or processors. For example, as used in the specification and the claims, a first server and/or a first processor that is recited as performing a first step or function may refer to the same or different server and/or a processor recited as performing a second step or function.
[0084] As used herein, the terms “electronic wallet,”“electronic wallet mobile application,” and“digital wallet” may refer to one or more electronic devices and/or one or more software applications configured to initiate and/or conduct transactions (e.g., payment transactions, electronic payment transactions, and/or the like). For example, an electronic wallet may include a user device (e.g., a mobile device) executing an application program and server-side software and/or databases for maintaining and providing transaction data to the user device. As used herein, the term“electronic wallet provider” may include an entity that provides and/or maintains an electronic wallet and/or an electronic wallet mobile application for a user (e.g., a customer). Examples of an electronic wallet provider include, but are not limited to, Google Wallet™, Android Pay®, Apple Pay®, and Samsung Pay®. In some non limiting examples, a financial institution (e.g., an issuer institution) may be an electronic wallet provider. As used herein, the term “electronic wallet provider system” may refer to one or more computer systems, computer devices, servers, groups of servers, and/or the like operated by or on behalf of an electronic wallet provider.
[0085] As used herein, the term“acquirer” may refer to an entity licensed by the transaction service provider and/or approved by the transaction service provider to originate transactions using a portable financial device of the transaction service provider. Acquirer may also refer to one or more computer systems operated by or on behalf of an acquirer, such as a server computer executing one or more software applications (e.g.,“acquirer server”). An“acquirer” may be a merchant bank, or in some cases, the merchant system may be the acquirer. The transactions may include original credit transactions (OCTs) and account funding transactions (AFTs). The acquirer may be authorized by the transaction service provider to sign merchants of service providers to originate transactions using a portable financial device of the transaction service provider. The acquirer may contract with payment facilitators to enable the facilitators to sponsor merchants. The acquirer may monitor compliance of the payment facilitators in accordance with regulations of the transaction service provider. The acquirer may conduct due diligence of payment facilitators and ensure that proper due diligence occurs before signing a sponsored merchant. Acquirers may be liable for all transaction service provider programs that they operate or sponsor. Acquirers may be responsible for the acts of its payment facilitators and the merchants it or its payment facilitators sponsor.
[0086] Non-limiting embodiments or aspects of the present invention are directed to systems, methods and compute program products for backup transaction processing for electronic payment transactions. In some non-limiting embodiments or aspects, a method may include receiving transaction data associated with a transaction in a transaction processing network initiated with a portable financial device, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; determining an accessibility of at least one system in the transaction processing network; in response to a determination that the at least one system in the transaction processing network is accessible, transmitting the transaction data associated with the transaction to the at least one system and receiving, from the at least one system, authorization data associated with the transaction, via the communication path of the transaction processing network; and in response to a determination that the at least one system in the transaction processing network is inaccessible, accessing, with at least one processor, decision data at a decision system via a communication path outside the communication path of the transaction processing network, and authorizing the transaction based on the decision data.
[0087] In some non-limiting embodiments or aspects, a method may include receiving, from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network; receiving, from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network; processing the transaction based on the transaction data and the decision data; and providing authorization data associated with the at least one transaction to the system in the transaction processing network.
[0088] In some non-limiting embodiments or aspects, a method may include receiving transaction data associated with a transaction initiated with a portable financial device at a merchant system; transmitting the transaction data associated with the transaction to a transaction processing network, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction; receiving an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network; in response to receiving the indication that the transaction is declined by the transaction processing network, accessing decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device; and authorizing the transaction based on the decision data.
[0089] In this way, embodiment or aspects of the present invention may provide backup transaction processing for electronic payment transactions. For example, a failure of an electronic payment transaction processing network or function due to a failure at or communication loss with one or more of a merchant, an acquirer, a transaction service provider, and/or an issuer can be avoided or overcome by providing and/or accessing via a communication path outside the communication path of the transaction processing network decision data for authorizing the transaction. Accordingly, more accurate, reliable, and/or dependable electronic payment transaction processing can be provided.
[0090] Referring now to FIG. 1 , FIG. 1 is a diagram of an example environment 100 in which devices, systems, and/or methods, described herein, may be implemented. As shown in FIG. 1 , environment 100 includes transaction processing network 102 including merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10, user device 1 12, decision system 1 14, remote system 1 16, and/or communication network 1 18. Transaction processing network 102 including merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10, user device 1 12, decision system 1 14, and/or remote system 1 16 may interconnect (e.g., establish a connection to communicate) via wired connections, wireless connections, or a combination of wired and wireless connections.
[0091] Merchant system 104 may include one or more devices capable of receiving information from acquirer system 106, transaction service provider system 108, issuer system 1 10, user device 1 12, decision system 1 14, and/or remote system 1 16 via communication network 1 18 and/or communicating information to acquirer system 106, transaction service provider system 108, issuer system 1 10, user device 1 12, decision system 1 14, and/or remote system 1 16 via communication network 1 18. Merchant system 104 may also include a device capable of receiving information from user device 1 12 via communication network 1 18, a communication connection (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, and/or the like) with user device 1 12, and/or the like, and/or communicating information to user device 1 12 via the network, the communication connection, and/or the like. For example, merchant system 104 may include a computing device, such as a server, a group of servers, a client device, a group of client devices, and/or other like devices. In some non limiting embodiments or aspects, merchant system 104 may be associated with a merchant as described herein. In some non-limiting embodiments or aspects, merchant system 104 may include one or more user devices 1 12. For example, merchant system 104 may include user device 1 12 that allows a merchant to communicate information to decision system 1 14 and/or transaction processing network 102 including transaction acquirer system 106, transaction service provider system 108, and/or issuer system 1 10. In some non-limiting embodiments or aspects, merchant system 104 may include one or more devices, such as computers, computer systems, and/or peripheral devices capable of being used by a merchant to conduct a payment transaction with a user. For example, merchant system 108 may include a POS device and/or a POS system.
[0092] Acquirer System 106 may include one or more devices capable of receiving information from merchant system 104, transaction service provider system 108, issuer system 1 10, user device 1 12, decision system 1 14, and/or remote system 1 16 via communication network 1 18 and/or communicating information to merchant system 104, transaction service provider system 108, issuer system 1 10, user device 1 12, decision system 1 14, and/or remote system 1 16 via communication network 1 18. For example, acquirer system 106 may include a computing device, such as a server, a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, acquirer system 106 may be associated with an acquirer as described herein.
[0093] Transaction service provider system 108 may include one or more devices capable of receiving information from merchant system 104, acquirer system 106, issuer system 1 10, user device 1 12, decision system 1 14, and/or remote system 1 16 via communication network 1 18 and/or communicating information to merchant system 104, acquirer system 106, issuer system 110, user device 1 12, decision system 1 14, and/or remote system 1 16 via communication network 1 18. For example, transaction service provider system 108 may include a computing device, such as a server (e.g., a transaction processing server), a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, transaction service provider system 108 may be associated with a transaction service provider as described herein. In some non-limiting embodiments or aspects, transaction service provider system 108 may be in communication with a data storage device, which may be local or remote to the transaction service provider system 108. In some non limiting embodiments or aspects, transaction service provider system 108 may be capable of receiving information from, storing information in, communicating information to, or searching information stored in data storage device.
[0094] Issuer system 1 10 may include one or more devices capable of receiving information from merchant system 104, acquirer system 106, transaction service provider system 108, user device 1 12, decision system 1 14, and/or remote system 1 16 via communication network 1 18 and/or communicating information to merchant system 104, acquirer system 106, transaction service provider system 108, user device 1 12, decision system 1 14, and/or remote system 1 16 via communication network 1 18. For example, issuer system 1 10 may include a computing device, such as a server, a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, issuer system 1 10 may be associated with an issuer institution as described herein. For example, issuer system 1 10 may be associated with an issuer institution that issued a credit account, debit account, credit card, debit card, and/or the like to a user associated with user device 1 12.
[0095] In some non-limiting embodiments or aspects, transaction processing network 102 includes a plurality of systems in a communication path for processing a transaction. For example, transaction processing network 102 can include merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 in a communication path (e.g., a communication path, a communication channel, a communication network, etc.) for processing an electronic payment transaction. As an example, transaction processing network 102 can process (e.g., initiate, conduct, authorize, etc.) an electronic payment transaction via the communication path between merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10.
[0096] User device 1 12 may include one or more devices capable of receiving information from merchant system 104, acquirer system 106, transaction service provider system 108, issuer system 1 10, decision system 1 14, and/or remote system 1 16 via communication network 1 18 and/or communicating information to merchant system 104, acquirer system 106, transaction service provider system 108, issuer system 1 10, decision system 1 14, and/or remote system 1 16 via communication network 1 18. For example, user device 1 12 may include a client device and/or the like. In some non-limiting embodiments or aspects, user device 1 12 may or may not be capable of receiving information (e.g., from merchant system 104) via a short range wireless communication connection (e.g., an NFC communication connection, an RFID communication connection, a Bluetooth® communication connection, and/or the like), and/or communicating information (e.g., to merchant system 104) via a short range wireless communication connection. In some non-limiting embodiments or aspects, user device 1 12 may include an application associated with user device 1 12, such as an application stored on user device 1 12, a mobile application (e.g., a mobile device application, a native application for a mobile device, a mobile cloud application for a mobile device, and/or the like) stored on user device 1 12, and/or the like.
[0097] Decision system 1 14 may include one or more devices capable of receiving information from merchant system 104, acquirer system 106, transaction service provider system 108, issuer system 1 10, user device 1 12, and/or remote system 1 16 via communication network 1 18 and/or communicating information to merchant system 104, acquirer system 106, transaction service provider system 108, issuer system 1 10, user device 1 12, and/or remote system 1 16 via communication network 1 18. For example, decision system 1 14 may include a computing device, such as a server, a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, decision system 1 14 may integrate transaction authorization and/or risk assessment functions from merchant system 104, acquirer system 106, transaction service provider system 108, issuer system 1 10 and/or remote system 1 16. In some non-limiting embodiments or aspects, decision system 1 14 can be remote from and/or external to transaction processing network 102, user device 1 12, and/or remote system 1 16. For example, decision system 1 14 can communicate with merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 via a communication path outside the communication path of the transaction processing network. As an example, decision system 1 14 can transmit data to and/or receive data from merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 via a communication path other than the communication path used by transaction processing network 102 to process transactions. As an example, the communication path used by transaction processing network 102 to process transactions may use a sequentially dependent process or path through transaction processing network 102, which can risk failure of transaction processing network 102 due to failure of any one of the systems in the sequential process or path. In some non-limiting embodiments or aspects, decision system 1 14 may be in communication with a data storage device, which may be local or remote to decision system 1 14. In some non-limiting embodiments or aspects, decision system 1 14 may be capable of receiving information from, storing information in, communicating information to, or searching information stored in data storage device.
[0098] Remote system 1 16 may include one or more devices capable of receiving information from merchant system 104, acquirer system 106, transaction service provider system 108, issuer system 1 10, user device 1 12, and/or decision system 1 14 via communication network 1 18 and/or communicating information to merchant system 104, acquirer system 106, transaction service provider system 108, issuer system 1 10, user device 1 12, and/or decision system 1 14 via communication network 1 18. For example, remote system 1 16 may include a computing device, such as a server, a group of servers, and/or other like devices. In some non-limiting embodiments or aspects, remote system 1 16 may be associated with a third-party system (e.g., a system other than merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10, etc.), such as a system or data source outside or external to transaction processing network 102 and/or the communication path thereof for processing transactions, that provides transaction data and/or decision data associated with users and/or user accounts. In some non-limiting embodiments or aspects, remote system 1 16 can be remote from and/or external to transaction processing network 102, user device 1 12, and/or decision system 1 14.
[0099] Communication network 1 18 may include one or more wired and/or wireless networks. For example, communication network 1 18 may include a cellular network (e.g., a long-term evolution (LTE) network, a third generation (3G) network, a fourth generation (4G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, and/or the like, and/or a combination of these or other types of networks.
[0100] The number and arrangement of devices and networks shown in FIG. 1 are provided as an example. There may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in FIG. 1. Furthermore, two or more devices shown in FIG. 1 may be implemented within a single device, or a single device shown in FIG. 1 may be implemented as multiple, distributed devices. For example, one or more of merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 may include and/or implement decision system 1 14 (e.g., access decision system 1 14 internally and outside the communication path of transaction processing network 102), and/or decision system 1 14 may be separate and remote from and/or implemented outside one or more of merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 110 (e.g., one or more of merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 can externally access decision system 114 via a communication path outside the communication path of transaction processing network 102). Additionally, or alternatively, a set of devices (e.g., one or more devices) of environment 100 may perform one or more functions described as being performed by another set of devices of environment 100.
[0101] Referring now to FIG. 2, FIG. 2 is a diagram of example components of a device 200. Device 200 may correspond to one or more devices of transaction processing network 102, one or more devices of merchant system 104, one or more devices of acquirer system 106, one or more devices of transaction service provider system 108, one or more devices of issuer system 1 10, one or more devices of user device 1 12, one or more devices of decision system 1 14, one or more devices of remote system 1 16, and/or one or more devices of communication network 1 18. In some non-limiting embodiments or aspects, one or more devices of transaction processing network 102, one or more devices of merchant system 104, one or more devices of acquirer system 106, one or more devices of transaction service provider system 108, one or more devices of issuer system 1 10, one or more devices of user device 1 12, one or more devices of decision system 1 14, one or more devices of remote system 1 16, and/or one or more devices of communication network 1 18 can include at least one device 200 and/or at least one component of device 200. As shown in FIG. 2, device 200 may include a bus 202, a processor 204, memory 206, a storage component 208, an input component 210, an output component 212, and a communication interface 214.
[0102] Bus 202 may include a component that permits communication among the components of device 200. In some non-limiting embodiments or aspects, processor 204 may be implemented in hardware, firmware, or a combination of hardware and software. For example, processor 204 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and/or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.) that can be programmed to perform a function. Memory 206 may include random access memory (RAM), read only memory (ROM), and/or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, optical memory, etc.) that stores information and/or instructions for use by processor 204.
[0103] Storage component 208 may store information and/or software related to the operation and use of device 200. For example, storage component 208 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of computer-readable medium, along with a corresponding drive. [0104] Input component 210 may include a component that permits device 200 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally, or alternatively, input component 210 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output component 212 may include a component that provides output information from device 200 (e.g., a display, a speaker, one or more light- emitting diodes (LEDs), etc.).
[0105] Communication interface 214 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 214 may permit device 200 to receive information from another device and/or provide information to another device. For example, communication interface 214 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi® interface, a cellular network interface, and/or the like.
[0106] Device 200 may perform one or more processes described herein. Device 200 may perform these processes based on processor 204 executing software instructions stored by a computer-readable medium, such as memory 206 and/or storage component 208. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices.
[0107] Software instructions may be read into memory 206 and/or storage component 208 from another computer-readable medium or from another device via communication interface 214. When executed, software instructions stored in memory 206 and/or storage component 208 may cause processor 204 to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, embodiments or aspects described herein are not limited to any specific combination of hardware circuitry and software. [0108] The number and arrangement of components shown in FIG. 2 are provided as an example. In some non-limiting embodiments or aspects, device 200 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 2. Additionally, or alternatively, a set of components (e.g., one or more components) of device 200 may perform one or more functions described as being performed by another set of components of device 200.
[0109] Referring now to FIG. 3, FIG. 3 is a flowchart of a non-limiting embodiment or aspect of a process 300 for backup electronic payment transaction processing. In some non-limiting embodiments or aspects, one or more of the steps of process 300 may be performed (e.g., completely, partially, etc.) by transaction service provider system 108 (e.g., one or more devices of transaction service provider system 108). In some non-limiting embodiments or aspects, one or more of the steps of process 300 may be performed (e.g., completely, partially, etc.) by another device or a group of devices separate from or including transaction service provider system 108, such as merchant system 104 (e.g., one or more devices of merchant system 104), acquirer system 106 (e.g., one or more devices of acquirer system 106), issuer system 1 10 (e.g., one or more devices of issuer system 1 10), user device 1 12, decision system 1 14 (e.g., one or more devices of decision system 1 14), and/or remote system 1 16 (e.g., one or more devices of remote system 1 16).
[0110] As shown in FIG. 3, at step 302, process 300 includes receiving transaction data associated with a transaction in a transaction processing network initiated with a portable financial device, the transaction processing network including a plurality of systems in a communication path for processing the transaction. For example, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 receives transaction data associated with a transaction in transaction processing network 102 initiated with user device 1 12. As an example, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 receives transaction data associated with the transaction from user device 1 12 and/or one or more other systems in transaction processing network 102.
[0111] In some non-limiting embodiments or aspects, transaction data includes transaction parameters associated with transactions, such as payment transactions initiated and/or conducted with an electronic wallet application, and/or the like. Non- limiting examples of transaction parameters include: electronic wallet card data, decision data, authorization data, primary account number (PAN), transaction amount, transaction date and time, conversion rate of currency, merchant type, acquiring institution country, PAN country, response code, merchant name/location, type of currency, and/or the like. Response code may refer to a successful approval/completion of a transaction, denial because card reported as lost or stolen, do not honor, partial approval, VIP approval (VIP program), amount exceeds maximum, insufficient funds, incorrect PIN, suspected fraud, activity amount exceeded, allowable number of PIN-entry tries exceeded, and/or the like.
[0112] In some non-limiting embodiments or aspects, electronic wallet card data includes one or more of data associated with an identifier regarding a portable financial device to be provided to an electronic wallet application, data associated with an identifier of an issuer associated with the portable financial device to be provided to an electronic wallet application, data associated with an identifier of a transaction service provider associated with the portable financial device to be provided to an electronic wallet application, data associated with a name of a user associated with the portable financial device to be provided to an electronic wallet application, data associated with an account identifier of an account associated with the portable financial device to be provided to an electronic wallet application, and/or the like.
[0113] As further shown in FIG. 3, at step 304, process 300 includes determining an accessibility of at least one system in the transaction processing network. For example, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 determine an accessibility of at least one system in transaction processing network 102. As an example, merchant system 104 can determine an accessibility of acquirer system 106, transaction service provider system 108, and/or issuer system 1 10. As an example, acquirer system 106 can determine an accessibility of merchant system 104, transaction service provider system 108, and/or issuer system 1 10. As an example, transaction service provider system 108 can determine an accessibility of merchant system 104, acquirer system 106, and/or issuer system 110. As an example, issuer system 1 10 can determine an accessibility of merchant system 104, acquirer system 106, and/or transaction service provider system 108. [0114] In some non-limiting embodiments or aspects, an accessibility of a system is determined based on the system being available for communication and/or processing associated with a transaction in transaction processing network 102. For example, a system can be determined to be inaccessible when the system is down (e.g., not operating, not processing, not communicating, etc.), when another system attempting to access the system is down or experiencing a communication loss with the system, and/or a communication channel (e.g., the communication path for processing a transaction in transaction processing network 102, etc.) is down (e.g., communication and/or connectivity between systems or devices via the channel is not available, communication via the channel results in one or more communication and/or processing errors, etc.).
[0115] In some non-limiting embodiments or aspects, merchant system 104, acquirer system 106, transaction service provider system 108, and issuer system 1 10 may be accessible in transaction processing network 102 for communication and/or processing associated with a transaction.
[0116] In some non-limiting embodiments or aspects, and referring also to implementation 600 shown in FIG. 6, issuer system 1 10 may be inaccessible. For example, transaction service provider system 108 may be unable to communicate with and/or access issuer system 1 10 for communication and/or processing associated with the transaction via the communication path of transaction processing network 102. As an example, transaction service provider system 108 can determine that issuer system 1 10 is inaccessible for processing the transaction.
[0117] In some non-limiting embodiments or aspects, and referring also to implementation 700 shown in FIG. 7, acquirer system 106 may be inaccessible. For example, merchant system 104 may be unable to communicate with and/or access acquirer system 106 for communication and/or processing associated with the transaction via the communication path of transaction processing network 102. As an example, merchant system 104 can determine that acquirer system 106 is inaccessible for processing the transaction.
[0118] In some non-limiting embodiments or aspects, and referring also to implementation 800 shown in FIG. 8, merchant system 104 may be inaccessible. For example, merchant system 104 may be unable to communicate with and/or access decision system 1 14a, acquirer system 106, transaction service provider system 108, and issuer system 1 10 for communication and/or processing associated with the transaction via the communication path of transaction processing network 102. As an example, merchant system 104 can determine that merchant system 104 itself is inaccessible (e.g., offline, unable to communicate with external systems, etc.)
[0119] In some non-limiting embodiments or aspects, and referring also to implementation 900 shown in FIG. 9, transaction service provider system 108 may be inaccessible. For example, acquirer system 106 may be unable to communicate with and/or access transaction service provider system 108 for communication and/or processing associated with the transaction via the communication path of transaction processing network 102. As an example, acquirer system 106 can determine that transaction service provider system 108 is inaccessible for processing the transaction.
[0120] As further shown in FIG. 3, at step 306, process 300 includes in response to a determination that the at least one system in the transaction processing network is accessible, transmitting the transaction data associated with the transaction to the at least one system. For example, in response to a determination that the at least one system in transaction processing network 102 is accessible, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 transmits the transaction data associated with the transaction to the at least one system. As an example, merchant system 104 can transmit the transaction data associated with the transaction to acquirer system 106, transaction service provider system 108, and/or issuer system 1 10. As an example, acquirer system 106 can transmit the transaction data associated with the transaction to merchant system 104, transaction service provider system 108, and/or issuer system 1 10. As an example, transaction service provider system 108 can transmit the transaction data associated with the transaction to merchant system 104, acquirer system 106, and/or issuer system 1 10. As an example, issuer system 1 10 can transmit the transaction data associated with the transaction to merchant system 104, acquirer system 106, and/or transaction service provider system 108.
[0121] As further shown in FIG. 3, at step 308, process 300 includes receiving, from the at least one system, authorization data associated with the transaction, via the communication path of the transaction processing network. For example, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 receives, from the at least one system authorization data associated with the transaction (e.g., an authorization, approval, and/or completion of the transaction at and/or by the at least one system or a denial and/or failure of the transaction at and/or by the at least one system, etc.). As an example, acquirer system 106 can receive, from merchant system 104, transaction service provider system 108, and/or issuer system 1 10, authorization data associated with the transaction. As an example, transaction service provider system 108 can receive, from merchant system 104, acquirer system 106, and/or issuer system 1 10, authorization data associated with the transaction. As an example, issuer system 1 10 can receive, from merchant system 104, acquirer system 106, and/or transaction service provider system 108 authorization data associated with the transaction.
[0122] As further shown in FIG. 3, at step 310, process 300 includes in response to a determination that the at least one system in the transaction processing network is inaccessible, accessing decision data at a decision system via a communication path outside the communication path of the transaction processing network. For example, in response to a determination that the at least one system in transaction processing network 102 is inaccessible, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 accesses decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102. As an example, in response to a determination that acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 is inaccessible, merchant system 104 can access decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102. As an example, in response to a determination that merchant system 104, transaction service provider system 108, and/or issuer system 1 10 is inaccessible, acquirer system 106 can access decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102. As an example, in response to a determination that merchant system 104, acquirer system 106, and/or issuer system 1 10 is inaccessible, transaction service provider system 108 can access decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102. As an example, in response to a determination that merchant system 104, acquirer system 106, and/or transaction service provider system 108 is inaccessible, issuer system 1 10 can access decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102.
[0123] In some non-limiting embodiments or aspects, and referring again to implementation 600 as shown in FIG. 6, in response to a determination that issuer system 1 10 is inaccessible, transaction service provider system 108 can access decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102. In some non-limiting embodiments or aspects, and referring again to implementation 700 as shown in FIG. 7, in response to a determination that acquirer system 106 is inaccessible, merchant system 104 can access decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102. In some non-limiting embodiments or aspects, and referring again to implementation 800 as shown in FIG. 8, in response to a determination that merchant system 104 is inaccessible, merchant system 104 can access decision data at decision system 114b via a communication path outside the communication path of transaction processing network 102. For example, decision system 1 14b may be included in and/or implemented by merchant system 104. In some non limiting embodiments or aspects, and referring again to implementation 900 as shown in FIG. 9, in response to a determination that transaction service provider system 108 is inaccessible, acquirer system 106 can access decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102.
[0124] In some non-limiting embodiments or aspects, decision data includes data associated with transactions in transaction processing network 102 and/or associated with users of portable financial devices in transaction processing network 102. For example, decision data can include at least one of the following: transaction data, network data, issuer data, third-party data, and/or the like. As an example, decision data can be associated with at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof. For example, decision data can include parameters associated with transactions in transaction processing network 102 and/or parameters associated with users of portable financial devices associated with the transactions. [0125] In some non-limiting embodiments, network data includes data associated with at least one of the following: a transaction type of a transaction, a fraud and/or compromise exposure event associated with an account, a merchant type of a merchant associated with a transaction, a transaction velocity associated with an account (e.g., with respect to a portable financial device, an account, a user history, an industry history and/or average, a seasonal and/or history trend in velocity, etc.), a location of a transaction and/or a user, and/or the like. For example, a transaction type includes parameters such as a product type of a portable financial device (e.g., a credit card, a debit card, a prepaid card, a commercial card, a private label card, a charge card, etc.), a payment type of a transaction (e.g., a purchase payment, a return payment, an account inquiry, a balance request, a cash disbursement or withdrawal, a deposit, a prepaid load, a fraud report, etc.), an authentication means of an account (e.g., a PIN, a signature, a cardholder address, etc.), an entry method (e.g., a tokenized method, a tap method, a swipe method, a chip dip method, a key entered method, a card on file method, etc.), a channel of a transaction (e.g., a face to face transaction, an ecommerce transaction, an unattended terminal transaction, a mail order transaction, a telephone order transaction, a recurring transaction, a bill payment, etc.), and/or the like. As an example, a fraud and/or compromise exposure event includes parameters such as a global network fraud pattern and/or trend, a compromised event associated with an account (e.g., an indication that account information, for example, an account number, a cardholder name, a billing address, a secure code (e.g., a Cardholder Verification Value 2 - printed on signature panel - visible to the human eye), and/or content of a magnetic stripe (including a Cardholder Verification Value - not visible to the human eye - encoded on the magnetic stripe), is exposed or stolen, such as a result of a breach of a cardholder system, a merchant system, an acquirer system, a transaction service provider system, and/or a transaction processing network, etc.), and/or the like. For example, a merchant type includes parameters such as a transaction category of a transaction (e.g., everyday spending, luxury spending, etc.), a merchant type and/or a merchant category code (MCC) associated with a transaction, an industry type (e.g., a transaction risk may increase with“resale” of products, such as electronics which can be easily resold as compared to more perishable items, for example, fast food, etc.), an indication of a high risk cash type transaction, an indication of a quasi-cash and/or gambling withdrawal and/or payment transaction, a transaction amount of a transaction compared to an average transaction amount for an industry (e.g., a transaction amount greater than a threshold amount for a particular industry may indicate an intent to launder merchandise, a transaction amount lower than a threshold amount for a particular industry may indicate testing of cards and authentication components, such as CVV2 and/or PINs, etc.), and/or the like. As an example, a velocity includes parameters such as a transaction date of a transaction, a transaction time of a transaction, a number of transactions in a period of time associated with an account, a purchase amount of a number of transactions in a period of time associated with an account, a number of declines in a period of time associated with an account (e.g., indicating potential testing of PINs or other values, etc.), a number of transactions above a threshold number of transactions and/or a number of transaction performed simultaneously to each other over a number of different geographic locations and associated with a same account, and/or the like. For example, a location includes parameters such as a merchant location, a cardholder location, a location usage pattern (e.g., domestic“around the corner patterns”, etc.), cross-border usage locations, known high risk geographic usage, usage at multiple distance location at a same time, and/or the like.
[0126] In some non-limiting embodiments, issuer data includes data associated with at least one of the following: other financial device (e.g., other card, etc.) product activity and/or balances of a user, a mortgage and/or loan balance and/or utilization of a user, a utilization ratio of a user, a checking and/or saving account balance of a user, new account activity associated with a user, a brokerage, investment, and/or retirement account balance and/or utilization of a user, and/or the like. For example, other card product activity and/or balances includes parameters such as an amount of related debt associated with a user, an amount of credit associated with a user, prepaid or business account information associated with a user, and/or the like. As an example, a mortgage and/or loan balance and/or utilization includes parameters such as an outstanding, past due, and/or default mortgage and/or loan balance associated with a user. For example, a utilization ratio includes parameters such as a percentage and/or an amount of utilization of one or more credit lines associated with a user. As an example, a checking and/or saving account balance of a user includes parameters such as related deposit account information associated with a user, for example, an available account balance of a user, a credit line utilization ratio of a user, repayment across multiple accounts of a user, available and used credit across multiple accounts of a user, travel and/or large purchase intentions of a user, an employer of a user, a salary of a user, and/or the like. For example, new account activity associated with a user includes parameters related to financial behavior of a user, for example, a number of new accounts opened and/or an amount of financial exposure across accounts of a user. As an example, a user, a brokerage, investment, and/or retirement account balance and/or utilization of a user includes parameters such as a balance change investment balance and/or behavior associated with a user (e.g., a balance and/or behavior associated with one or more brokerage and/or investment accounts of the user, etc.), repayment across multiple accounts of a user, available and used credit across multiple accounts of a user, and/or the like.
[0127] In some non-limiting embodiments, third-party data includes data associated with a repayment, a late payment, an arrears payment, a collection payment, and/or a write-off across credit accounts of a user, an available and/or used credit utilization across accounts of a user, a composite outstanding debt amount of a user, a trending debt amount of a user, an employer of a user, a salary amount of a user, a salary trend of a user, a bankruptcy history of a user, an application for a new account of a user, a death of a user, extreme weather (e.g., a hurricane, tornado, etc.) associated with a location of a user, a political event (e.g., government instability, etc.) associated with a location of a user, a currency inflation associated with a location of a user and/or a merchant, an interest rate associated with a location of a user and/or a merchant, currency controls and revaluation associated with a location of a user and/or a merchant, and/or the like.
[0128] In some non-limiting embodiments or aspects, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 transmits the transaction data to decision system 1 14, and receives the decision data from decision system 1 14, wherein the decision data comprises a score associated with the transaction.
[0129] In some non-limiting embodiments or aspects, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 receives the decision data from decision system 1 14 for determining a score associated with the transaction based on the decision data and the transaction data at merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 (e.g., for determining the score within transaction processing network 102).
[0130] In some non-limiting embodiments or aspects, the score associated with the transaction is determined based on the transaction data associated with the transaction and/or the decision data. For example, the score can include a score associated with a risk for merchant system 104 authorizing the transaction, a risk for acquirer system 106 authorizing the transaction, a risk for transaction processing network 108 authorizing the transaction, and/or a risk for issuer system 1 10 authorizing the transaction. As an example, and referring again to implementation 600 as shown in FIG. 6, transaction service provider system 108 (and/or decision system 1 14) can determine a risk for transaction service provider system 108 authorizing the transaction without receiving authorization of the transaction from issuer system 1 10 based on the transaction data and/or the decision data. As an example, and referring again to implementation 700 as shown in FIG. 7, merchant system 104 (and/or decision system 1 14) can determine a risk for merchant system 104 authorizing the transaction without receiving authorization of the transaction from acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 based on the transaction data and/or the decision data. As an example, and referring again to implementation 800 as shown in FIG. 8, merchant system 104 (and/or decision system 1 14b) can determine a risk for merchant system 104 authorizing the transaction without receiving authorization of the transaction from acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 based on the transaction data and/or the decision data. As an example, and referring again to implementation 90 as shown in FIG. 9 acquirer system 106 can determine a risk for acquirer system 106 authorizing the transaction without receiving authorization of the transaction from transaction service provider system 108 and/or issuer system 1 10 based on the transaction data and/or the decision data.
[0131] In some non-limiting embodiments or aspects, the score can be determined by applying at least one rule to the transaction data associated with the transaction and/or the decision data. For example, the at least one rule may define at least one threshold of parameters of the transaction data and/or the decision data to be satisfied for the transaction to be authorized at and/or by one or more of merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10. As an example, the at least one rule may define at least one threshold associated with at least one of the parameters in the decision data.
[0132] In some non-limiting embodiments or aspects, a network score is determined as a function of one or more parameters in network data associated with a user and/or a transaction. For example, one or more statistical functions (e.g., an average, a mean, a standard deviation, etc.) can be applied to the one or more parameters and/or the one or more parameters can be weighted with respect to each other to determine the network score. In some non-limiting embodiments, an issuer score can be determined as a function of one or more parameters in issuer data associated with a user and/or a transaction. For example, one or more statistical functions (e.g., an average, a mean, a standard deviation, etc.) can be applied to the one or more parameters and/or the one or more parameters can be weighted with respect to each other to determine the issuer score. In some non-limiting embodiments, a third party score can be determined as a function of one or more parameters in third party data associated with a user and/or a transaction. For example, one or more statistical functions (e.g., an average, a mean, a standard deviation, etc.) can be applied to the one or more parameters and/or the one or more parameters can be weighted with respect to each other to determine the third party score. In some non-limiting embodiments, decision system 1 14 integrates the network score, the issuer score, and/or the third party score to determine the score associated with the transaction for the user. As an example, the network score, the issuer score, and/or the third party score the one or more parameters can be weighted with respect to each other and/or combined to determine the network score. For example, decision system 1 14 can apply a time based algorithm to track relevant parameters (e.g., transaction amount velocities, transaction count velocities, etc.) of a user (e.g., by card number, by financial institution account holder, by an aggregate of accounts associated with the user across multiple financial institutions, etc.) over periods of time and compare the tracked parameters to previous, anticipated, and/or cohort values. As an example, decision system 1 14 can apply a transaction amount based algorithm to track relevant purchase amount data of a user (e.g., trending of credit and/or debit account balances, a credit line utilization rate and/or trend, transfers between accounts and/or institutions, etc.). For example, decision system 1 14 can apply a cohort behavior algorithm to analyze spending, cash withdrawals, transfers, inquiries, and/or other parameters of a user (e.g. compare parameters of the user to other users with similar income, wealth, age, geography, and/or demographics, employer, etc.)· As an example, decision system 1 14 can apply a life cycle event algorithm (e.g., based on a global event, a logical time zone, weather, politics, etc.) to analyze data associated with global fraud event trending (e.g., parameters associated with organized crime, nation backed account testing, network attack, and/or other coordinated compromises), activity by logical time of day norms, velocity, industry, and/or other distinct regional behavior, and/or weather, natural disasters, political events, and/or other significant payment behavior influencing event and trends.
[0133] In some non-limiting embodiments or aspects, the at least one rule applied to the transaction data and/or the decision data is determined based on a system that is accessing the decision data at decision system 1 14 via the communication path outside the communication path of transaction processing network 102. For example, decision system 1 14 may determine the at least one rule for a first transaction based on merchant system 104 accessing the decision data for the first transaction, and decision system 1 14 may determine the at least one rule for a second transaction based on transaction service provider system 108 accessing the decision data for the second transaction
[0134] In some non-limiting embodiments or aspects, the transaction is automatically authorized (or declined) at and/or by one or more of merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 in response to the transaction data (and/or the decision data) including a predetermined account identifier (e.g., predetermined or known bad accounts, predetermined VIP accounts, etc.). For example, decision data 104 may include a list of accounts defined by merchant system 104 for automatic transaction approval. As an example, decision data 104 may include a list of accounts defined by transaction service provider system 108 for automatic transaction denial.
[0135] As further shown in FIG. 3, at step 312, process 300 includes authorizing the transaction based on the decision data. For example, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 authorizes the transaction based on the decision data. As an example, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 authorizes the transaction in response to the score associated with the transaction satisfying a threshold score. [0136] In some non-limiting embodiments or aspects, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 updates the decision data at decision system 1 14 based at least partially on the transaction data associated with the transaction. For example, merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10 updates the decision data at decision system 1 14 to include the transaction data associated with the transaction, the authorization data associated with the transaction including an indication of whether the transaction is authorized or denied (and/or reasons for authorization and/or denial), and/or the like.
[0137] Referring now to FIG. 4, FIG. 4 is a flowchart of a non-limiting embodiment or aspect of a process 400 for backup electronic payment transaction processing. In some non-limiting embodiments or aspects, one or more of the steps of process 400 may be performed (e.g., completely, partially, etc.) by decision system 1 14 (e.g., one or more devices of decision system 1 14). In some non-limiting embodiments or aspects, one or more of the steps of process 400 may be performed (e.g., completely, partially, etc.) by another device or a group of devices separate from or including decision system 1 14, such as merchant system 104 (e.g., one or more devices of merchant system 104), acquirer system 106 (e.g., one or more devices of acquirer system 106), transaction service provider system 108 (e.g., one or more devices of transaction service provider system 108), issuer system 1 10 (e.g., one or more devices of issuer system 1 10), user device 1 12, and/or remote system 1 16 (e.g., one or more devices of remote system 1 16).
[0138] As shown in FIG. 4, at step 402, process 400 includes receiving, from a plurality of systems in a transaction processing network, decision data associated with at least one of the following: at least one prior transaction in the transaction processing network, at least one user of at least one account associated with one or more systems of the plurality of systems in the transaction processing network, or any combination thereof, wherein the plurality of systems comprise a communication path for processing transactions in the transaction processing network. For example, decision system 1 14 receives, from merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10, decision data. As an example, decision system 1 14 can receive decision data associated with a global network view of the user from transaction service provider system 108 (e.g., types of transactions, comprised events, merchant types and/or MCC codes, transaction velocity, transaction countries, etc.), and receive decision data associated with a financial institution view of the user from issuer system 1 10 (e.g., related account behavior of the user, available account balance of the user, a credit line utilization ratio of the user, new account activity of the user, investment balance and/or behavior associated with the user, etc.).
[0139] In some non-limiting embodiments or aspects, decision system 1 14 receives at least a portion of the decision data from remote system 1 16 outside the communication path of transaction processing network 102. For example, decision system 1 14 can receive decision data associated with third-party sourced insights and/or accounts outside of transaction service provider system 108 and/or issuer system 1 10 from remote system 1 16 (e.g., repayment across multiple accounts of a user, available and used credit across multiple accounts of a user, travel and/or large purchase intentions of a user, an employer of a user, a salary of a user, a bankruptcy status of a user, one or more applications for new accounts by a user, new account activity associated with a user, etc.). As an example, decision system 1 14 can integrates decision data from transaction service provider 108, issuer system 1 10, and remote system 1 16 before a transaction is initiated in transaction processing network 102 to generate an integrated set of decision data and/or rules for determining scores associated with transactions based on transaction data associated with the transactions and the integrated decision data.
[0140] As further shown in FIG. 4, at step 404, process 400 includes receiving, from a system of the plurality of systems, transaction data associated with a transaction in the transaction processing network via a communication path outside the communication path of the transaction processing network. For example, decision system 1 14 receives, from one or more of merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10, transaction data associated with a transaction in transaction processing network 102 via a communication path outside the communication path of transaction processing network 102. As an example, decision system 114 provides the integrated decision data (e.g., via a cloud network and/or as a local data store) as a back-up should any of the stakeholders in transaction processing network 102 have processing or communication problems, or otherwise be unavailable.
[0141] In some non-limiting embodiments or aspects, and referring again to implementation 600 as shown in FIG. 6, decision system 1 14 receives the transaction data associated with the transaction from transaction service provider system 108, for example, as a result of transaction service provider system 108 accessing the decision data at decision system 1 14 in response to issuer system 1 10 being inaccessible.
[0142] In some non-limiting embodiments or aspects, and referring again to implementation 700 as shown in FIG. 7, decision system 1 14 receives the transaction data associated with the transaction from merchant system 104, for example, as a result of merchant system 104 accessing the decision data at decision system 1 14 in response to acquirer system 106 being inaccessible.
[0143] In some non-limiting embodiments or aspects, and referring again to implementation 800 as shown in FIG. 8, decision system 1 14b receives the transaction data associated with the transaction from merchant system 104, for example, as a result of merchant system 104 accessing the decision data at decision system 1 14 in response to merchant system 104 being inaccessible.
[0144] In some non-limiting embodiments or aspects, and referring again to implementation 900 as shown in FIG. 9, decision system 1 14 receives the transaction data associated with the transaction from acquirer system 106, for example, as a result of acquirer system 106 accessing the decision data at decision system 1 14 in response to transaction service provider system 108 being inaccessible.
[0145] As further shown in FIG. 4, at step 406, process 400 includes processing the transaction based on the transaction data and the decision data. For example, decision system 1 14 processes the transaction based on the transaction data and the decision data. As an example, decision system 1 14 determines a score associated with the transaction based on the transaction data associated with the transaction and the decision data as described herein. For example, and referring again to implementation 600 as shown in FIG. 6, decision system 1 14 can process the transaction based on current decision data received from transaction service provider system 108 (e.g,. decision data provided and/or determined concurrently with the current transaction, etc.) and previous decision data from issuer system 1 10 (e.g., decision data provided and/or determined prior to the current transaction, etc.). For example, and referring again to implementation 900 as shown in FIG. 9, decision system 1 14 can process the transaction based on current decision data received from issuer system 1 10 and prior decision data received from transaction service provider system 108.
[0146] As further shown in FIG. 4, at step 408, process 400 includes providing authorization data associated with the at least one transaction to the system in the transaction processing network. For example, decision system 1 14 provides authorization data associated with the at least one transaction to the one or more of merchant system 104, acquirer system 106, transaction service provider system 108, and/or issuer system 1 10. In some non-limiting embodiments or aspects, the authorization data includes the score associated with the transaction. In some non limiting embodiments or aspects, the authorization data includes an indication of whether the transaction is (or should be) authorized or denied (and/or reasons for authorization and/or denial), and/or the like.
[0147] Referring now to FIG. 5, FIG. 5 is a flowchart of a non-limiting embodiment or aspect of a process 500 for backup electronic payment transaction processing. In some non-limiting embodiments or aspects, one or more of the steps of process 500 may be performed (e.g., completely, partially, etc.) by merchant system 104 (e.g., one or more devices of merchant system 104). In some non-limiting embodiments or aspects, one or more of the steps of process 400 may be performed (e.g., completely, partially, etc.) by another device or a group of devices separate from or including decision system 1 14, such as merchant system 104 (e.g., one or more devices of merchant system 104), acquirer system 106 (e.g., one or more devices of acquirer system 106), transaction service provider system 108 (e.g., one or more devices of transaction service provider system 108), issuer system 1 10 (e.g., one or more devices of issuer system 1 10), user device 1 12, and/or remote system 1 16 (e.g., one or more devices of remote system 1 16).
[0148] As shown in FIG. 5, at step 502, process 500 includes receiving transaction data associated with a transaction initiated with a portable financial device at a merchant system. For example, merchant system 104 receives transaction data associated with a transaction initiated with user device 1 12 at merchant system 104.
[0149] As further shown in FIG. 5, at step 504, process 500 includes transmitting the transaction data associated with the transaction to a transaction processing network, wherein the transaction processing network comprises a plurality of systems in a communication path for processing the transaction. For example, merchant system 104 transmits the transaction data associated with the transaction to transaction processing network 102 (e.g., to acquirer system 106, transaction service provider system 108, and/or issuer system 1 10).
[0150] As further shown in FIG. 5, at step 506, process 500 includes receiving an indication that the transaction is declined by the transaction processing network via the communication path of the transaction processing network. For example, merchant system 104 receives an indication that the transaction is declined by transaction processing network (e.g., declined by acquirer system 106, transaction service provider system 108, and/or issuer system 1 10) via the communication path of transaction processing network 102. As an example, and referring also to implementation 1000 as shown in FIG. 10, issuer system 1 10 may decline the transaction.
[0151] As further shown in FIG. 5, at step 508, process 500 includes in response to receiving the indication that the transaction is declined by the transaction processing network, accessing decision data at a decision system via a communication path outside the communication path of the transaction processing network, wherein the decision data is associated with a user of the portable financial device. For example, merchant system 104, in response to receiving the indication that the transaction is declined by transaction processing network 102, accesses decision data at decision system 1 14 via a communication path outside the communication path of transaction processing network 102. As an example, and referring again to implementation 1000 as shown in FIG. 10, merchant system 104 accesses decision data at decision system 1 14 via the communication path outside the communication path of transaction processing network 102.
[0152] In some non-limiting embodiments or aspects, merchant system 104 may be implemented by a merchant that is willing to accept a risk associated with authorizing a transaction even if the transaction is not approved by or denied by other systems in transaction processing network 102 (e.g., the merchant may know the cardholder as a regular customer and be willing to accept a promise from the cardholder to pay for the transaction at some future time, the merchant may prefer not to pay for risk mitigation provided by authorization from transaction service provider system 108 and/or authorization from issuer system 1 10, etc.). For example, decision merchant system 104 can approve a transaction based on a customer being a known customer and determining a score for the transaction above a threshold score based on decision data accessed by merchant system 104 at decision system 1 14.
[0153] As further shown in FIG. 5, at step 510, process 500 includes authorizing the transaction based on the decision data. For example, merchant system 104, authorizes the transaction based on the decision data. As an example, merchant system 104 can override the decline in the transaction processing network 102 of the transaction by assuming the risk associated with the transaction. For example, merchant system 104 can transmit an authorization of the transaction to transaction processing network 102 that indicates that merchant system 104 is responsible for payment of the transaction in response to a default in payment by the user/customer.
[0154] Although the invention has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred embodiments or aspects, it is to be understood that such detail is solely for that purpose and that the invention is not limited to the disclosed embodiments or aspects, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present invention contemplates that, to the extent possible, one or more features of any embodiment or aspect can be combined with one or more features of any other embodiment or aspect.