Integration of 3DS authentication scripts and Silent Order Post (SOP)
This integration is legacyThis flow combines the browser-based 3DS authentication script (MPI V2) with the Silent Order Post (SOP) script, and it works only with the legacy integration. For new integrations, use the current version, MPI V3, with a server-to-server architecture.
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.
The following flow describes the steps of 3DS with Silent Order Post:

- The shopper chooses to pay with a card (credit or debit) and fills in the details;
- The merchant runs the 3DS authentication script, which checks with the card brand and issuer to validate the transaction;
- The Cielo 3DS Server returns the authentication data (
ECI,Cavv,Xid,Version,ReferenceId) in theOnSuccessevent; - The merchant runs the Silent Order Post script, which uses OAuth2 for authentication before sending the data;
- The Silent Order Post returns the tokenized card data (
Payment.Token); - The merchant requests authorization from the API Cielo E-commerce, providing:
- 3DS authentication data (
ECI,Cavv,Xid, etc.) in thePayment.ExternalAuthenticationparameter; - Card token (
Payment.Token).
- 3DS authentication data (
- The API Cielo E-commerce returns the authorization response;
- The merchant confirms the shopper order, if desired.
This is a simplified flow. For full details, see:
Updated about 1 month ago