Overview

onboard your merchants to provide them forter services integration steps provide forter with an outline of your merchant portfolio this should include information about verticals, traffic, and payment methods accepted on your merchant sites forter will use this information to start training its models register merchants in order to use forter services on behalf of your merchants, you'll first need to register them with forter using the merchant https //docs forter com/reference/merchant api endpoint in the api response, forter will return to you an id that forter will use as that merchant's subsite id, and they will be enrolled for fraud management services forter allows up to 10k sites to be created via the api please reach out to your forter team if you need to exceed the 10k default site limit merchant api response { "merchantid" "eh629dk9", // internal id in your system provided in request "defaultmerchantcategorycode" "5655", "merchantaccountcreation" { "timestamp" 1415273179, "ip" "10 0 0 128" }, "id" "abcde1234567", // forter id to be included in a dedicated header in api requests "name" "t shirts express" } enroll merchants in 3ds services if you are utilizing forter's 3ds recommendation or execution services as part of your element integration, you'll also need to enroll each merchant that will be using these services through the 3ds recommendation enrollment https //docs forter com/reference/3ds recommendation enrollment and 3ds execution enrollment https //docs forter com/reference/3ds execution enrollment api endpoints include the merchant's subsite id as the id in the url path curl x post https //api forter secure com/merchants/\[id]/3ds recommendation u "{secret key value}" h "api version 10 1" h "x forter siteid {your site id}" h "content type application/json" d '{ "offerings" { "policy 3ds" true, "psd2" true, "risk 3ds" true } }' the api response will indicate whether the request was received, but does not yet indicate if the enrollment is complete you can follow up on the request by calling the 3ds recommendation enrollment status https //docs forter com/reference/3ds recommendation enrollment status or 3ds execution enrollment status https //docs forter com/reference/3ds execution enrollment status endpoints to confirm that the merchant is successfully onboarded to this feature front end integration https //docs forter com/front end integration with merchant's subsite id for forter element, the minimum requirement is that the javascript is added to the checkout page so that the forter token can be retrieved and included in the backend order data for each of your merchants' sites be sure to include the merchant's subsite id in the script placed on their website checkout integration with merchant's subsite id complete the checkout integration https //docs forter com/checkout integration for fraud management, 3ds recommendation https //docs forter com/3ds recommendation , or 3ds execution https //docs forter com/3ds execution , depending on the services you are offering to your merchants when sending api calls to forter on behalf of a merchant, include their subsite id as the x forter sub merchant siteid in the header of the api request curl x post "https //{site id} api forter secure com/{endpoint}" u "{api key} " h "api version 10 1" h "content type application/json" h "x forter siteid {site id}" h "x forter sub merchant siteid {subsite id}" d @filepost datapost purchase updates https //docs forter com/post purchase updates with merchant's subsite id as you receive payment authentication updates (pre auth flows) and the order fulfillment status changes, it's important to keep forter notified, so that this information can be used in future decisions please also include dispute notifications https //docs forter com/dispute notifications with merchant's subsite id notifying forter of disputes (also called claims, chargebacks, or fraud alerts) is extremely important because it enables forter's system to learn and continually improve future decisions, tailoring our system to your company's needs you can send these updates to forter via a webhook from your psp or via forter's dispute api endpoint share historical data https //docs forter com/historical data share historical order data (approximately last 12 months) from your first 50 sites