Solving Forter Fraud-Detection Challenges

Forter is a fraud-detection layer used on checkout and payment flows. It collects device and behavior signals client-side, posts them to its own endpoint, and binds a session token (e.g. ftr__siteId) the merchant validates server-side. MeshPrivacy reproduces this flow and returns the resulting cookies.

Service Schema

FieldTypeRequiredDescription
urlstringYesTarget checkout/payment page URL
script_urlstringNoForter script URL
merchant_idstringNoForter merchant/site ID (ftr__siteId)
proxy_configstringNoProxy in http://user:pass@ip:port format
user_agentstringNoCustom user agent

Service ID: forter · Status: Stable

Real-time API status: trust.meshprivacy.com

Locating script_url and merchant_id

Inspect the page source on the checkout flow. Forter loads from a script URL such as https://cdn4.forter.com/...; the merchant ID appears in ftr__siteId cookie or the script's init payload.

Integration Example

forter.js
// Submit Forter task to MeshPrivacy
const response = await fetch('https://api.meshprivacy.com/v1/tasks/submit', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json', 'X-API-Key': API_KEY },
  body: JSON.stringify({
    service: 'forter',
    url: 'https://target-site.com/checkout',                  // required
    script_url: 'https://cdn4.forter.com/script.js',          // optional
    merchant_id: 'forter-merchant-id',                        // optional - ftr__siteId
    proxy_config: 'http://user:pass@ip:port',                 // optional
    user_agent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64)...'// optional
  })
});
const { task_id } = await response.json();

const result = await fetch(`https://api.meshprivacy.com/v1/tasks/result/${task_id}`, {
  headers: { 'X-API-Key': API_KEY }
});
const { cookies } = await result.json();
// Forter token cookie returned for checkout/payment flows

FAQ

When the merchant's checkout endpoint rejects requests missing valid Forter cookies, or when its response references ftr__siteId.

Related Services