ProPay may require that partners perform extra fraud monitoring steps when boarding new merchants. These additional steps are performed using ThreatMetrix® application monitoring.
Partners who are expected to use ThreatMetrix® should include a special widget on their website, into which they pass their own unique identifier. That same identifier must then be passed when the partner makes the boarding API call to ProPay.
You should generate your own unique identifier for each signup attempt. This will be known as a session id. The Session Id may be up to 128 bytes long and must consist of the following characters only:
In your signup interface web page header, you need to include the following additional html tag:
4uw65rkp' (In some special cases, ProPay may elect to provide partners with their own org id.)
In the body of your page, you should include the following:
<iframe style="width: 100px; height: 100px; border: 0; position: absolute; top: -5000px;"
ThreatMetrixPolicy (always default unless indicated otherwise) and
ThreatMetrixSessionId will need to be included in your boarding API request to ProPay. Click here to return to the boarding API description.