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