Forter

Service Overview

Forter is a US fraud-prevention provider that describes itself as the identity intelligence expert, which in plainer terms means: helping brands know who they are doing business with. It does not acquire payments, hold funds or settle money. It sits between the merchant and the acquirer and answers one question - who is behind this order, and should they be allowed through.

Its origin explains the product shape. Founders Michael Reitblat and Liron Damri are childhood friends who worked early on at an Israeli manual-review risk company that later became part of PayPal. During that PayPal period they led an experiment replacing a rules-based risk workflow with AI models, which sharply improved fraud detection accuracy. Once the experiment held up, they concluded the capability could stand as its own product, and Forter followed.

There are 6 product lines: Fraud Management, Payment Optimization, Dispute Management, Account Protection, Abuse Prevention and Forter Element. Together they cover 4 moments - registration, login, checkout and after-sale - over a single identity layer underneath.

The boundary has to be stated up front: Forter does not lend, does not acquire, does not run onboarding checks and does not absorb chargeback losses. What it delivers is a decision, and the money loss stays on the merchant's books. If the requirement is offloading chargeback exposure to a third party, Forter is not the answer - that is where financially guaranteed providers sit. If the requirement is seeing who the customer is and letting good orders through, it becomes an option.

The more important point is what it judges. It is not asking whether a transaction looks fraudulent but who the person is. Device identifiers, IP addresses and shipping addresses on a single order can all be forged; the behavioural trail of one identity across merchants is much harder to fake at the same time. The same consumer being a two-year repeat buyer at 3 other merchants while being a first-time buyer with you is a signal your own order table can never produce.

Key Strengths

• Identity adds information you cannot generate yourself: a single-merchant system is bounded by its own order history. Forter folds in payment history, dispute history and account-change records for the same identity from other merchants, effectively letting you see a longer history before deciding. For categories with a high share of new customers but a broader footprint, that history is the basis for approving.
• 6 product lines share one judgement: fraud management, payment optimization, dispute management, account protection and abuse prevention are not 6 stitched-together systems but different exits of one identity signal. The benefit is consistency - two orders treated as the same person at checkout will not be treated as two people during a dispute, which cuts cross-system explanation work.
• False declines are treated as a measurable loss: payment optimization is a standalone product line, which signals that declined good revenue is an optimizable revenue line rather than a by-product of fraud control. For merchants that already hold fraud rates low but face growth pressure, a few points of false-decline reduction is direct revenue.
• Judgement happens before checkout: registration, login and checkout live in the same identity view, so account takeover followed by orders from a new device, or bulk promo-code abuse, can be stopped before checkout instead of being reconstructed after a chargeback.
• There is an ROI path before purchase: the official calculator lets a merchant plug in its own order volume, average ticket and current false-decline rate to build an estimate. That makes budget approval easier than a pay-first-then-validate model.
• A clean integration surface: a standalone documentation site, API-first integration, and no requirement to switch acquirer or gateway, so both custom builds and SaaS platforms can adopt it.

Product Ecosystem

Fraud Management

The core product, covering card misuse, orders placed after account takeover and return fraud. It issues approve or decline decisions at checkout with the reasoning attached, and high-risk orders can route to manual review, though the design intent is to shrink that queue rather than grow it.

Payment Optimization

A dedicated line aimed at false declines. The goal is letting good customers who would otherwise be rejected through, reducing the trade-off between suppressing fraud and sacrificing conversion. For high-ticket, long-repurchase-cycle categories this often matters more to profit than the block rate does.

Dispute Management

Covers evidence assembly and representment after a chargeback. It is important to be precise here: it assists with evidence, it does not absorb the loss. Whatever cannot be recovered still lands on the merchant.

Account Protection

Covers login, registration, password change and contact-detail changes, blocking credential stuffing, account takeover and bulk registration. For platform businesses with membership systems these are a different attack surface from payment fraud.

Abuse Prevention

Covers promo-code abuse, coupon arbitrage, refund-policy abuse and unauthorised resale. These losses never appear in chargeback reports; they hide inside marketing spend and after-sales cost, and are the easiest to overlook.

Forter Element

A checkout-facing integration component that embeds identity judgement into the payment flow so merchants do less front-end rework of their own.

Limitations

• The two error directions cost differently: approving a fraudulent order costs goods plus chargeback fees and card-network fines, and can damage the merchant's dispute-rate monitoring position. Declining a good customer costs this order's margin plus future repeat purchases. Both sides sit with the merchant because there is no loss guarantee, which is the essential difference from guaranteed providers.
• Data sharing is a hard prerequisite: the graph's value comes from cross-merchant signals, which means continuously contributing and sharing consumer behaviour data. Cross-border operations turn this directly into GDPR and personal data export assessments, with separate compliance paths where export applies; legal and security review usually takes much longer than integration.
• Cold start and a scale threshold: network effects cut both ways. With enough volume and high audience overlap with other merchants in the network the graph carries real information; in narrow verticals or at very low order volume the output approaches a generic rules model and the price premium buys little.
• Duplicate spend against an existing risk stack: merchants already running acquirer risk controls, 3DS policies and in-house rules must re-divide who judges first, who backstops and whose decision wins. Without that, the same order gets declined twice and conversion drops.
• No coverage of regulated obligations: AML transaction monitoring, onboarding KYC and sanctions screening are not among the 6 product lines. Banks, payment institutions and licensed businesses cannot satisfy supervisors with it and still need a separate compliance system, meaning two risk back offices to run.

Use Cases

• Mid-to-large cross-border e-commerce stores (★★★★★): order volume is high and audience overlap with the network is strong, so the identity graph genuinely works and both fraud rate and false-decline rate can improve at once.
• Platform businesses with membership systems (★★★★☆): registration, login, checkout and after-sale all sit in one identity view, so account takeover and promo abuse get handled alongside payment fraud.
• Digital goods and subscriptions (★★★★☆): no logistics and sensitive refund policies, while abuse prevention and dispute management cover the non-payment losses that are often larger than card fraud.
• Mainland China operations (★★☆☆☆): usable when a mainland entity runs cross-border business, but any export of personal data from within the mainland must follow the Personal Information Protection Law and the applicable data export rules, so a data compliance assessment comes first. Purely domestic business does not need overseas risk tooling of this kind, and equivalent domestic providers cost less to buy and to clear.
• Very small merchants (★☆☆☆☆): least suitable. Cold-start network effects plus volume-based pricing make the effective unit cost far higher than a generic rules tool, and the acquirer's built-in controls are the better first step.
• Institutions needing AML and licensing compliance (☆☆☆☆☆): least suitable. No AML transaction monitoring, onboarding review or watchlist screening, so a regulated entity cannot meet its obligations with this product.

Pricing

The main cost drivers are reviewed order volume, GMV, how many modules are enabled, whether manual review support is included and the integration approach. Forter does not publish standard pricing; the headings above and any final rate follow the current official quote and your contract.

FAQ

• How do I choose between Forter and a guaranteed fraud provider?
  Decide whether you are buying judgement or insurance. Forter delivers decisions and leaves chargeback exposure with the merchant, which suits teams with in-house risk capability that accept the exposure and care more about false declines. A guaranteed provider takes the chargeback loss but requires you to follow its decisions and comes with exclusions. They are not mutually exclusive; some merchants run both.

• Is it worth it at modest order volume?
  Start with audience overlap. If your customers overlap heavily with other merchants in the network - standard categories, typical DTC stores - mid-size volume can still produce useful signal. In a narrow vertical at a few thousand orders a month, the graph adds nothing and the premium buys little, so acquirer controls plus rule tooling is the more rational first step.

• We already run acquirer risk controls and 3DS. Do we need another layer?
  The question is where the increment is. Acquirer controls see the issuing side and transaction features but not cross-merchant identity trails, and they ignore account takeover and promo abuse. If losses are mostly card fraud, the acquirer controls are enough; if a meaningful share comes from friendly fraud, orders placed after account takeover and coupon abuse, this fills that gap.

• Do we have to hand over customer data?
  The graph logic means yes, otherwise it degrades into a generic model. What you can control is the compliance around it: define the minimum field set transferred, sign a data processing agreement and assess whether the transfer constitutes personal data export. For cross-border operations that step is not optional, and "technically transferable" is not a compliance argument.

• Does it pay out when a chargeback cannot be recovered?
  No. Dispute management helps assemble evidence and run representment to improve recovery odds, but loss ownership does not move. If the requirement is transferring chargeback risk, look at providers offering guarantees or recovery-based pricing, and pin down guarantee scope and exclusions in the contract.

Source: original 16IDC content. Product capabilities, supported countries and fee definitions follow the official documentation and your contract.