Onboarding
This document details the onboarding requirements for Forter's Predictive Routing solution.
Task 1: Processing Options and Constraints
For Forter to receive clear guidance on the available Payment processors for each Region and to detail any constraints relevant to their processing, please detail all available Payment processors and their processing constraints.
Required Information
Field | Description | Example |
|---|---|---|
Payment processor name | Name of the PSP | Adyen |
Acquirer | Acquiring bank | Adyen |
Available BIN country/Region | Countries or regions supported | US, IT, ES, UK |
Currencies | Supported currencies | USD, EUR, GBP |
PSD2 TRA (if relevant) | TRA threshold amount | EUR 500+ |
3DS supported | Whether 3DS is supported | Yes/No |
Merchant name | Your merchant identifier | |
Task 2: Business Commitments
Whenever making a Predictive routing decision, Forter has the ability to take into account your Business Commitments with a Payment processor.
For each Payment processor relevant, please state the Business Commitments you would like Forter to consider when making a Predictive routing decision.
Business Commitments are only relevant in case of a Predictive routing decision, and are not linked to any Routing Policies you may configure separately in the backend.
Commitment Structure
The commitment needs to be structured in the following way:
Min # (Amount of transactions) OR $ (Transaction volume) in currency (USD) per time frame (Monthly, Quarterly)
Note: The time frame is calendar-based, not rolling.
Example Format
Merchant Name | Payment Processor | Commitment | Amount | Timeframe |
|---|---|---|---|---|
Example Corp | Adyen | Minimum transaction # | 10,000 | Monthly |
Task 3: Define Routing Policies
As you extend to Forter the routing decision, you have the ability to dictate specific routing rules that you wish to not be subjected to any Predictive decision.
Example: Routing policy - all BinCountry US should be routed to Adyen
Policy Format
Please provide any routing policies you wish us to configure in the following format:
If [Attribute] [Operator] [Value] Route to [Processor_name] and retry with [Processor_name]Available Attributes
Attribute | Values | Comments |
|---|---|---|
BIN country | US, UK, IT, etc. | 2-letter format |
Currency | USD, GBP, EUR | 3-letter format |
Platform | Web / MobileApp | |
Card Scheme | Visa, MasterCard, Amex, etc. | |
Amount | | USD only |
BIN | | 4-8 digits format |
Card type | Debit, Credit | |
Merchant name | | |
Available Operators
- Equals
- Higher than
- Lower than
Processor Name
As defined in Task #1.
Processor name can also be N/A in case retry logic is not required for this policy.