Skip to main content

Best practices

Following these best practices is essential for ensuring both security and maximum conversion performance.

Careful integration​

While MCP Certify is designed for straightforward integration, effective compliance monitoring and verification still depend on careful implementation.

MCP Certify needs complete and consistent visibility across the live payment journey in order to compare what users actually experience against the approved implementation.

A well-executed integration improves monitoring accuracy, reduces false alerts, and gives operators and partners clearer evidence when live pages drift from their approved state. The effort invested in proper implementation helps ensure reliable visibility without disrupting the intended user experience.

Fallback snippet​

Implement fallback logic to ensure the fraud detection snippet loads even when the JS API fails:

(function(s, o, u, r, k){
    b = s.URL;
    v = (b.substr(b.indexOf(r)).replace(r + '=', '')).toString();
    r = (v.indexOf('&') !== -1) ? v.split('&')[0] : v;
    a = s.createElement(o),
    m = s.getElementsByTagName(o)[0];
    a.async = 1;
    a.setAttribute('crossorigin', 'anonymous');
    a.src = u+'script.js?ak='+k+'&lpi='+r+'&lpu='+encodeURIComponent(b)+'&key=$uniqid&_headers=".base64_encode($h)."';
    m.parentNode.insertBefore(a, m);
})(document, 'script', '".ApiSnippetUrl."', 'uniqid', '".ServiceKey."');

Parameters:

  • ServiceKey - Your service ID provided during provisioning
  • ApiSnippetUrl - MCP Certify's regional endpoint (see API reference)
  • uniqid - Unique identifier for session tracking

Placement: This script should be placed in the <head> section of your web page.