Abstract: Described herein are techniques and systems directed to using context data provided by supplemental devices to reduce false declines during transaction authorization. In some embodiments, upon a transaction being declined based on a level of risk associated with the transaction, a service provider may obtain context data from a number of supplemental devices associated with a user, resource provider, location, or other suitable factor. This context data may then be assessed by the service provider to determine a degree to which the context data supports that the user conducting the transaction is the owner of the account used to conduct the transaction. The level of risk may then be adjusted based on that degree and the adjusted level of risk is used to determine whether to approve or decline the transaction.

Abstract: A method for processing a potentially fraudulent electronic payment transaction includes: receiving a first fraud detection rule configured to identify a potentially fraudulent electronic payment transaction; storing the first fraud detection rule in a fraud rules database; receiving a transaction request message; generating and storing a first case record associated with the first transaction in a case management database; receiving an updated fraud detection rule superseding the first fraud detection rule; applying the updated fraud detection rule to the first transaction to determine whether the first transaction does not satisfy the at least one updated fraud detection rule; and deleting the first case record from the case management database before the first transaction is further analyzed for fraud.

Abstract: A method for processing a potentially fraudulent electronic payment transaction includes: receiving a first fraud detection rule configured to identify a potentially fraudulent electronic payment transaction; storing the first fraud detection rule in a fraud rules database; receiving a transaction request message; generating and storing a first case record associated with the first transaction in a case management database; receiving an updated fraud detection rule superseding the first fraud detection rule; applying the updated fraud detection rule to the first transaction to determine whether the first transaction does not satisfy the at least one updated fraud detection rule; and deleting the first case record from the case management database before the first transaction is further analyzed for fraud.

Abstract: A method for processing a potentially fraudulent electronic payment transaction includes: receiving a first fraud detection rule configured to identify a potentially fraudulent electronic payment transaction; storing the first fraud detection rule in a fraud rules database; receiving a transaction request message; generating and storing a first case record associated with the first transaction in a case management database; receiving an updated fraud detection rule superseding the first fraud detection rule; applying the updated fraud detection rule to the first transaction to determine whether the first transaction does not satisfy the at least one updated fraud detection rule; and deleting the first case record from the case management database before the first transaction is further analyzed for fraud.

Abstract: A method for processing a potentially fraudulent electronic payment transaction includes: receiving a first fraud detection rule configured to identify a potentially fraudulent electronic payment transaction; storing the first fraud detection rule in a fraud rules database; receiving a transaction request message; generating and storing a first case record associated with the first transaction in a case management database; receiving an updated fraud detection rule superseding the first fraud detection rule; applying the updated fraud detection rule to the first transaction to determine whether the first transaction does not satisfy the at least one updated fraud detection rule; and deleting the first case record from the case management database before the first transaction is further analyzed for fraud.

Abstract: A software program for initiating a payment transaction from a sender to a recipient and that the recipient lacks a destination account with a financial institution. The sender via the software program installed on a mobile device sends an instruction from a funding source account of the sender. The sender captures a biometric parameter of the recipient via the mobile device as an in-person capture. The mobile device via the software program stores at least a portion of the biometric parameter thereon. The sender sends an instruction via the software program to initiate the payment transaction to transmit funds from the funding source account to the recipient as identified by the biometric parameter. The mobile device transmits via the software program the biometric parameter and the user instruction to a payment server to complete the payment transaction.

Abstract: Described herein are techniques and systems directed to using context data provided by supplemental devices to reduce false declines during transaction authorization. In some embodiments, upon a transaction being declined based on a level of risk associated with the transaction, a service provider may obtain context data from a number of supplemental devices associated with a user, resource provider, location, or other suitable factor. This context data may then be assessed by the service provider to determine a degree to which the context data supports that the user conducting the transaction is the owner of the account used to conduct the transaction. The level of risk may then be adjusted based on that degree and the adjusted level of risk is used to determine whether to approve or decline the transaction.