Submitting a Transaction
There are two methods to submit a transaction to FraudShield: Batch Upload or API. Each method consumes a single credit per transaction and goes through the same rule processing flow, though the mode of submission differs.
For a full list of fields that can be submitted, see the Transaction Fields reference.
The banner at the top of the screen shows which Environment you are currently in: Production or Test. When submitting a batch file, the currently selected environment determines which environment the transactions are saved to. When submitting an API request, the API Key Type fulfils the same purpose.
For now, you probably only have test credits and should use the Test Environment.
Submission Methods​
Batch​
The Batch Upload method is suited to submitting multiple transactions on a schedule, or for transaction monitoring that doesn't require an instant response.
Batch upload allows you to submit a .CSV file through the FraudShield dashboard. The batch is verified for errors, then processed with live updates on screen. FraudShield sends an email notification to any user who has the relevant email preference enabled when the batch finishes.
For more detailed information on processing a batch file, see the Batch Upload page.
API​
The API method is suited to live environments where you need an instant response about the risk level and risk score of a transaction.
Integrating with the submit_transaction API allows you to send a JSON-formatted request to the FraudShield RESTful API endpoint. The API response includes the transaction analysis.
For more detailed information on submitting an API request, see the API Reference.
Transactions and Customer Profiles​
Once a transaction is uploaded, FraudShield saves it and makes it accessible at any time from the Transactions page.
FraudShield also automatically creates customer profiles based on the unique Customer Identifier provided in the transaction details. Each profile tracks the latest customer information, along with the transactions and cases they have been involved in, and can be accessed from the Customers page.
Case Processing​
Each transaction submitted to FraudShield is run through all enabled Rules in your Rule Plan. If one or more rules are flagged, FraudShield automatically generates a case for investigation, which can be viewed from the Cases page.
You can enable Email Notifications to be alerted when a batch finishes processing or a new case is created.
For more detailed information on investigating a case, see the Transaction Flow and Case Investigation guides.
See the Transaction Fields reference for a complete list of all fields you can include in a submission, then move on to Going Live when you're ready for production.