Abstract: A method for fraud control of a transaction account based on geolocation includes: storing, in an account database, an account profile including data related to a transaction account including a first profile rule associated with a first geographic area and a second profile rule associated with a second geographic area different from the first; receiving an authorization request for a first transaction involving a first payment card, the request including a first geographic location; receiving an authorization request for a second transaction involving a second payment card, the request including a second geographic location; determining validation for each authorization request, wherein each is determined to be valid if the geographic location is in a geographic area corresponding to the first geographic area or the second geographic area; and transmitting the determination of validation for each authorization request to a payment network for processing of the associated payment transaction.

Abstract: A method for retrying processing of a controlled payment transaction includes: storing, in a first database, account profiles, each including data related to a transaction account including an account identifier and account controls; storing, in a second database, the account profiles stored in the first database, wherein data in each account profile in the second database corresponds to data in the corresponding account profile in the first database; receiving an authorization request for a transaction, the request including a specific account identifier and transaction data; determining an approval or denial of the transaction based on the account controls included in a profile in the second database including the specific account identifier and the transaction data if an attempt to determine approval or denial based on the account controls included in a corresponding account profile in the first database fails; and processing the payment transaction based on the determination.

Abstract: A method for automatic generation of transaction controls includes: storing account profiles, each including a primary account number, communication data, and transaction controls, where payment transactions are subject to the transaction controls; receiving a transaction message for a declined payment transaction including a specific primary account number and additional data elements configured to store transaction data; identifying a specific account profile that includes the specific primary account number; generating a transaction control including one or more controls based on the transaction data; transmitting the generated transaction control to a computing device based on the communication data included in the specific account profile; receiving a confirmation from the computing device indicating approval of the generated transaction control; and updating the specific account profile to include the generated transaction control.

Abstract: A method for fraud control of a transaction account based on geolocation includes: storing, in an account database, an account profile including data related to a transaction account including a first profile rule associated with a first geographic area and a second profile rule associated with a second geographic area different from the first; receiving an authorization request for a first transaction involving a first payment card, the request including a first geographic location; receiving an authorization request for a second transaction involving a second payment card, the request including a second geographic location; determining validation for each authorization request, wherein each is determined to be valid if the geographic location is in a geographic area corresponding to the first geographic area or the second geographic area; and transmitting the determination of validation for each authorization request to a payment network for processing of the associated payment transaction.

Abstract: A method for retrying processing of a controlled payment transaction includes: storing, in a first database, account profiles, each including data related to a transaction account including an account identifier and account controls; storing, in a second database, the account profiles stored in the first database, wherein data in each account profile in the second database corresponds to data in the corresponding account profile in the first database; receiving an authorization request for a transaction, the request including a specific account identifier and transaction data; determining an approval or denial of the transaction based on the account controls included in a profile in the second database including the specific account identifier and the transaction data if an attempt to determine approval or denial based on the account controls included in a corresponding account profile in the first database fails; and processing the payment transaction based on the determination.