External 3Ds

This is only applicable if -

• you have your own 3ds vendor / supplier / gateway and can obtain the required data
• you are using Async / Sync payments and not Hosted Payments

Follow your vendor guidelines to take a 3d secure transaction to its final state
Then populate the ThreeDSData item in the Sync / Async payment

Important

It is important that if you populate ThreeDSData, then you do not populate ThreeDSConfig

Normally all data items are required

• Cavv
• ECI
• Version
• AuthenticationType
• TransStatus
• DsId
• AcsId
• SId

Warning

Please note that only minimal validation is performed on this input data, and data items are passed to the payment provider. This may have effect of causing declines, errors, and/or possibly settling transactions without the necessary 3dsecure coverage which may result in fines and/or liability shifts by the card schemes / issuer / acquirer / processor.

Note

Please note that some payment providers may not support this.

Recurring and registering payments

• For a payment that registers a card (CIT with recurrence OneClick, also when it carries the agreement object, see Agreements) the issuer is expected to authenticate the cardholder with a challenge. Your 3DS vendor must request it (challenge indicator 04, challenge mandated) and the TransStatus you send must be the result of that challenge.
• Later merchant initiated payments (MIT) are not authenticated again: they are sent as sync payments with a token and traceId (or an agreementId) and without ThreeDSData, see Payment Actions.
• Async and hosted payments are always customer initiated (CIT); MIT and MOTO are rejected with VAL13.