Premium Fraud Management Tools
Overview
While it is a best practice to configure Basic Fraud Tools to protect your account from some of the more standard forms of payment fraud, more complex fraud schemes require more advanced capabilities. Braintree's Premium Fraud Management Tools provide a suite of fraud prevention and detection checks before a request is processed, which helps catch fraudulent activity before authorization requests ever reach your customers' banks.
Additional data is needed to provide adequate coverage for Risk and Fraud management. This can be accomplished by ensuring the fields below are part of all transactions passed to Braintree for processing. They are easily added during the API/SDK configuration and must be done at this time.
Field | Description | API Reference Link | Mandatory by Risk Tool |
---|---|---|---|
Email address composed of ASCII characters. 255 character maximum. | Non Vaulting | Vaulting |
| |
Phone | The value in the phone number field of a customer's statement. Phone must be 10-14 characters and can only contain numbers, dashes, parentheses and periods. | Non Vaulting | Vaulting |
|
Customer IP | The customer's IP address. Should be sent for customer-initiated transactions (i.e., when the transactionSource is empty or set to moto, recurring_first, or installment_first). |
Non Vaulting | Vaulting |
|
Device ID | Customer device information. This should be sent for customer-initiated transactions, such as when the transactionSource is empty or set to moto, recurring_first, or installment_first. Find more details in the Collecting device data section of the Client-Side Implementation page. |
Non Vaulting | Vaulting |
|
Billing Information | Billing address information associated with a specific customer ID. | Non Vaulting. | Vaulting or Vaulting |
|
Shipping Information | Shipping address information associated with a specific customer ID. | Non Vaulting | Vaulting or Vaulting |
|
Cardholder Name | The name associated with the credit card. Must be less than or equal to 175 characters. | Non Vaulting | Vaulting |
|
Line Item | The line items for this transaction. It can include up to 249 line items. | Non Vaulting | Vaulting |
|
Chargeback Protection Tools - submitting required evidence for eligible chargebacks
Merchants can automate the manual submission process to pass shipping and tracking IDs and any additional eligible evidence, according to PayPal's Seller Protection Program, as follows:
- Step 1: Set up webhooks to get notified about chargeback status updates, such as open, lost, or won. Refer to our webhooks guide for details on configuring webhooks. You will receive a notification when the status changes for a chargeback event.
- Step 2: Upon receiving a webhook, extract the
dispute_id
from the payload only for the chargebacks in the "Open" state. - Step 3: Verify the dispute's eligibility by utilizing the
dispute_id
to find the dispute in Braintree. The dispute is eligible ifchargeback_protection_level
field references any Chargeback Protection tool and is in an "Open" state. - Step 4: If the dispute is eligible, provide the necessary evidence. Preferably, use the
Dispute: Add Text Evidence
API for text evidence. For file-based evidence, first, upload the files using theDocument Upload: Create
API, then use theDispute: Add File Evidence
API to attach the files to thedispute_id
. - Step 5: Finalize the dispute by submitting the evidence using the
Dispute: Finalize
API before the reply-by date.
Read more about differences between our fraud protection options.
Compatibility
Premium Fraud Management Tools are compatible with all credit and debit cards and the following:
Next Page: Configuration →