On this page
No Headings
Fraud Protection Advanced
Last updated: July 10, 2026
CURRENT
DOCS
Fraud Protection Advanced
Fraud Protection Advanced (FPA) is a robust fraud protection tool integrated into PayPal's core processing services. It enables your fraud teams to conduct in-depth risk analysis and investigations to help identify and mitigate fraud.
Fraud Protection Advanced combines decades of intelligence from the PayPal network with advanced machine learning (ML) and analytics to continuously adapt to changes in both a merchant's business and evolving fraud tactics. It is integrated with PayPal Complete Payments (PPCP) for merchants who are on the Advanced Checkout integration.
Notes:
- FPA is now available in the US and multiple global regions. For a complete list of supported countries, see Targeted users, eligible markets, and pricing details.
- Fraud Protection Advanced is available through your merchant's PayPal business account and can be enabled easily. For more information on how your merchants can set up FPA, see Getting started with FPA.
Fraud Protection Advanced is available through your merchant's PayPal business account and can be enabled easily. For more information on how your merchants can set up FPA, see Getting started with FPA.
Why is FPA essential?
FPA provides a range of powerful capabilities:
- Fraud profile identification: Initial fraud strategies are customized based on historical risk patterns. The effectiveness of these profiles is monitored post-onboarding and adjusted as needed to enhance performance.
- Fraud detection and risk scoring: Mitigate fraud by declining high-risk transactions using advanced features, including:
- Custom filters: Tailor rules to identify and block fraudulent activities.
- Manual review: Assess and review flagged transactions manually for further validation.
- Blocklists, allowlists, and reviewlists: Enhance filters with supplementary lists to manage trusted and suspicious entities.
- Activity tracking and audit trail: Track changes and user actions and maintain a detailed audit trail.
- ML-based AI model: Utilize machine learning techniques to analyze data points such as card details, buyer information, purchasing patterns, and device intelligence to generate a risk score.
Hence, we strongly recommend that your merchants choose FPA as their fraud protection tool.
What are the benefits?
FPA provides the following benefits on top of Fraud Protection (FP) for merchants enrolling in PPCP capabilities:
- It is a self-serve tool that your merchants can customize to meet their specific business requirements. It is not pre-configured to fit any business needs by default.
- PayPal can view both merchant and consumer activities across 25 billion transactions annually. This rich data fuels PayPal's machine learning models, which adapt to new transactions as they occur and historical fraud trends seen across the network, leading to more accurate fraud detection.
- Due to enhanced fraud decision-making by merchants, consumers will experience fewer declines, less friction, and faster order processing.
Additionally, PayPal enhances the onboarding experience for fraud protection tools by offering:
- The right product recommendation for fraud prevention tools, better discoverability, and comprehension of products.
- A streamlined, guided setup and activation experience.
- A better description of the advanced capabilities and flexibility of the fraud tools.
Essential prerequisites for optimal FPA performance
To enhance risk and fraud management, we strongly recommend that your merchants provide additional data. This data is incorporated into PayPal's machine learning models, allowing them to analyze historical transactions and to improve the model's efficiency in detecting fraud. This approach optimizes the performance of your merchant's risk and fraud management processes. To include this data, your merchant must pass the following fields to all requests sent to the Orders v2 API for processing.
Create order
The following table shows the required parameters for optimal FPA performance when making a POST call to the Create order endpoint of the Orders v2 API.
Device ID
- If your merchant is integrated through PayPal JS SDK, the device ID will be passed by default.
- If your merchant is integrated through APIs, they would need to do the following so that the device ID is passed in the request:
- Integrate Fraudnet if they are on a browser. The device ID is sent as
PAYPAL-CLIENT-METADATA-IDin the request data. - Integrate Magnes if they are on an app.
- If merchants do not want to use Fraudnet or Magnes, they can pass the device ID information directly through the Orders API requests in the
PAYPAL-CLIENT-METADATA-IDfield. For more information, see the Client-Metadata-Id in the Create order endpoint of the Orders v2 API.
- Integrate Fraudnet if they are on a browser. The device ID is sent as
Header
| Field name | Description | Type | Notes |
|---|---|---|---|
PayPal-Client-Metadata-Id | The device ID for this purchase. See the parameter definition for more information. | String |
|
Body
| Field name | Description | Type | Notes |
|---|---|---|---|
payment_source.card.attributes.customer.email_address | Email address of the buyer as provided to the merchant or on file with the merchant. Email Address is required if you are processing the transaction using PayPal Guest Processing, which is offered to select partners and merchants. For all other use cases, we do not expect partners or merchant to send email_address of their customer. See the parameter definition for more information. | string |
|
payment_source.card.attribues.customer.phone | The phone number of the buyer as provided to the merchant or on file with the merchant. The phone.phone_number supports only national_number. See the parameter definition for more information. | object | |
payment_source.card.billing_address | The billing address for this card. Supports only the address_line_1, address_line_2, admin_area_1, admin_area_2, postal_code, and country_code properties. See the parameter definition for more information. | object | |
purchase_units.shipping.address | The address of the person to whom to ship the items. Supports only the address_line_1, address_line_2, admin_area_1, admin_area_2, postal_code, and country_code properties. See the parameter definition for more information. | object | |
purchase_units.items | An array of line items that the customer purchases from the merchant. See the parameter definition for more information. | array of objects | |
purchase_units[].supplementary_data.risk.customer.ip_address | An Internet Protocol address (IP address). This address assigns a numerical label to each device that is connected to a computer network through the Internet Protocol. Supports IPv4 and IPv6 addresses.
"supplementary_data": { "risk": { "customer": { "ip_address": "192.158.1.38" } } } | string | Minimum characters: 7 Maximum characters: 39 Pattern: ^(([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])$|^(([a-zA-Z]|[a-zA-Z][a-zA-Z0-9\-]*[a-zA-Z0-9])\.)*([A-Za-z]|[A-Za-z][A-Za-z0-9\-]*[A-Za-z0-9])$|^\s*((([0-9A-Fa-f]{1,4}:){7}([0-9A-Fa-f]{1,4}|:))|(([0-9A-Fa-f]{1,4}:){6}(:[0-9A-Fa-f]{1,4}|((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){5}(((:[0-9A-Fa-f]{1,4}){1,2})|:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){4}(((:[0-9A-Fa-f]{1,4}){1,3})|((:[0-9A-Fa-f]{1,4})?:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){3}(((:[0-9A-Fa-f]{1,4}){1,4})|((:[0-9A-Fa-f]{1,4}){0,2}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){2}(((:[0-9A-Fa-f]{1,4}){1,5})|((:[0-9A-Fa-f]{1,4}){0,3}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){1}(((:[0-9A-Fa-f]{1,4}){1,6})|((:[0-9A-Fa-f]{1,4}){0,4}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(:(((:[0-9A-Fa-f]{1,4}){1,7})|((:[0-9A-Fa-f]{1,4}){0,5}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:)))(%.+)?\s*$ |
Capture payment for order
| Field name | Description | Type | Notes |
|---|---|---|---|
payment_source.card.name | The cardholder's name as it shows up on the card. See the parameter definition for more information. | string |
|
payment_source.card.number | The primary account number (PAN) for the payment card. See the parameter definition for more information. | string |
|
Targeted users, eligible markets, and pricing details
FPA is available for both direct merchants and through marketplaces, which are payment platforms that host merchants. The following table outlines the pricing details for each FPA-screened transaction across the available markets:
| Country code | Country | Headline price |
|---|---|---|
| US | United States | 0.07 USD |
| CA | Canada | 0.09 CAD |
| AU | Australia | 0.1 AUD |
| AT | Austria | 0.06 EUR |
| DE | Germany | 0.06 EUR |
| GB | United Kingdom | 0.06 GBP |
| FR | France | 0.06 EUR |
| ES | Spain | 0.06 EUR |
| IT | Italy | 0.06 EUR |
| PL | Poland | 0.3 PLN |
| PT | Portugal | 0.06 EUR |
| IE | Ireland | 0.06 EUR |
| BG | Bulgaria | 0.06 EUR |
| CY | Cyprus | 0.06 EUR |
| CZ | Czech Republic | 1.6 CZK |
| DK | Denmark | 0.5 DKK |
| EE | Estonia | 0.06 EUR |
| FI | Finland | 0.06 EUR |
| GR | Greece | 0.06 EUR |
| HU | Hungary | 25 HUF |
| LT | Lithuania | 0.06 EUR |
| LV | Latvia | 0.06 EUR |
| MT | Malta | 0.06 EUR |
| RO | Romania | 0.35 RON |
| SE | Sweden | 0.7 SEK |
| SI | Slovenia | 0.06 EUR |
| SK | Slovakia (Slovak Republic) | 0.06 EUR |
| BE | Belgium | 0.06 EUR |
| LU | Luxembourg | 0.06 EUR |
| NL | Netherlands | 0.75 EUR |
| LI | Lichtenstein | 0.06 EUR |
| NO | Norway | 0.75 NOK |
| SM | San Marino | 0.06 EUR |
| SG | Singapore | 0.1 SGD |
| HK | Hong Kong | 0.6 HKD |
Discovery and access
Your merchants can find FPA using either of the following options:
- In Business Tools, navigate to the Manage Risk section. Select the Fraud Tools tile.
- Alternatively, go to your Account Settings, and select Payment preferences. Next to the Manage fraud section, select Choose a fraud tool.
Enable FPA
Your merchants can enable FPA using the following steps:
- Select Do it yourself using PayPal's fraud tool and select Next.
- You will see a recommended solution based on your business metrics. However, you can modify the selection if you want. Choose Fraud Protection Advanced Tool and select Next.
- Confirm your details to set up automatic bank payments for your fraud tool, and select Next.
- Select Let's Go to go to the Fraud Protection Advanced tool and begin customizing your fraud tool.
View the FPA Dashboard
Once activated, Fraud Protection Advanced will open in a new tab. The D****ashboard will display fraud metrics related to your merchant's business over the past 180 days.
After onboarding to FPA, your merchants should set up FPA for their accounts.
Features
FPA offers a range of powerful features designed to help you reduce fraud:
-
Fraud profile identification: Provides automated filter recommendations based on onboarding data and historical transaction data. Use these to make informed decisions and strengthen your overall fraud prevention strategy.
-
Risk score calculation: PayPal's machine learning model analyzes various data points, including card details, buyer information, purchasing patterns, and device intelligence, among others, to calculate a Risk Score. The risk score ranges from 0 to 100, where 0 indicates no risk, and 100 represents a highly risky transaction.
-
Fraud detection: Mitigates fraud by declining risky transactions through advanced features such as:
- Filters: Rules that determine whether FPA approves, rejects, or flags a transaction for review. Merchants can enable, adjust, or create their own filters.
- Lists: Collections used to apply actions to a group of attributes. Merchants can use Allowlists to ensure their trusted customers can check out smoothly and Blocklists to prevent known bad actors. Reviewlists enable merchants to automatically queue transactions with specific attributes for manual review, allowing their team to decide whether to approve or reject them. Merchants can create lists, view the number of items on each list, and check if an active filter is associated with each attribute list.
- Review: Transactions flagged for review are placed in a single queue, where merchants can view the filters that triggered the review, the time the transaction occurred, and the associated risk score. Merchants can manually review transactions and determine whether to approve or reject them.
- ActivityHistory of all actions associated with the FPA tool, including changes to filters, fields, lists, and case reviews. It helps merchants also track who made changes and when they occurred.
