Outlines making a Custom 3D secure integration using an external merchant plug-in (MPI).
Authorise the payment
Submitting API payments with an external3D MPI is implemented as a SOAP service using the same URL, WSDL, username and password as used for normal API payments.
- Make an
- For custom 3D secure integrations specifically, pass the following fields:
shopperIP: IP address of the shopper.
browserInfo.acceptHeader: The user agent and accept header value of the shopper's browser.
mpiData: A container for the data retrieved from the external 3D MPI. For more information, see ThreeDSecureData.
authorisationMid: These values will be supplied to you by the support department. By default Adyen dynamically routes transactions to multiple acquirers depending on configuration or availability. When using an external MPI the authorisation must be processed over the same acquirer and MID (account at the acquirer) as used by the MPI. Therefore, the
authorisationMidmust be passed in the