SecurePay 3DS v.2.0 Implementation

For users of SECUREPAY, minimal additional effort is required compared to the current integration. The workflow is identical to the current 3D Secure 1.0 implementation. OPP SECUREPAY will handle the entire additional communication and will be responsible for collecting required browser based information automatically. Following data must be collected by the merchant and send in via:

  • Server/Server, create checkoutId
  • being collected by adding additional input fields to the payment widget
===
  • billing.city - Required - Cardholder (via widget or API)
  • billing.country - Required - Cardholder (via widget or API)
  • billing.street1  - Required - Cardholder (via widget or API)
  • billing.postcode - Required - Cardholder (via widget or API)
  • customer.email - Required - Cardholder (via widget or API)
  • card.holder - Required - Cardholder (via widget or API)