Integration of 3DS authentication scripts and Silent Order Post (SOP)

3DS authentication can be combined with the Silent Order Post (SOP) script to perform authenticated and secure transactions. In this model, the authentication process occurs separately from authorization, allowing the data generated by the 3DS script to be included in the authorization request along with the PaymentToken generated via Silent Order Post.

Step 1 – 3DS Authentication

Authentication must be performed before the transaction authorization. To do this, run the 3DS authentication script on the checkout page.

After executing the script, the following data will be returned:

• eci;
• cavv;
• xid;
• referenceId

Include these values in the authorization request under the Payment.ExternalAuthentication node.

Set the Authenticate field to true to indicate that the transaction was authenticated via 3DS before authorization.

Step 2 – Run the Silent Order Post (SOP) Script

After obtaining the PaymentToken through the Silent Order Post script, proceed with the authorization process by sending the PaymentToken instead of the card data.

Below is the complete flow for the authorization step after executing the scripts:

ℹ️

This is an example of a credit card request using 3DS authentication and Silent Order Post (SOP), and the response follows the standard format of a credit transaction.