Credit Card Verification Guide - SCA parameters

Please find below our set of CustomSupplierParameters which are going to be supported where your application carries out the pre-authentication on behalf of the supplier.

In this regard, please note the set of SCA parameters below are defined based on the EMVCo specifications, but are not exhaustive as a few additional parameters may later be introduced.

What is important to denote here is that these parameters will be returned as Supported within the RequiredParameterList of ProcessDetails response whenever the supplier supports pre-authentication. If these are returned and you have carried out the pre-authentication, please submit their respective values in the StartBooking request. Suppliers may not always support pre-authentication and a redirect as described in our ‘Credit Card Verification Guide - Redirect’ may be required. If the CSPs are not returned in the ProcessDetails response, then only the ‘Card verification’ redirect may be prompted by the supplier based on the specific nature of the transaction.

Please make sure you are able to divert traffic via tfPay as a fall back. Please confirm your application will be ready with the ‘Card verification’ redirect solution.

We have also introduced the SCACorporateExempt CSP in order to reflect SCA exemption rules. This CSP is to be submitted for genuine cards coming from a non-consumer environment which are eligible for secure corporate exemption. You will also need to acknowledge that you'll only submit the flag if it genuinely qualifies for corporate secure exemption.

StartBooking request XML example containing the set of Pre-Authentication CustomSupplierParameters

<CommandList>

<StartBooking>

<XmlLoginId>****</XmlLoginId>

<LoginId>****</LoginId>

<TFBookingReference>YYYYYY</TFBookingReference>

<BookingProfile>

<CustomSupplierParameterList>

<CustomSupplierParameter>

<Supplier>ezy</Supplier>

<Name>SCAAResTransStatus</Name>

<Value>Y</Value>

</CustomSupplierParameter>

<CustomSupplierParameter>

<Supplier>ezy</Supplier>

<Name>SCAAv</Name>

<Value>3q2+78r+ur7erb7vyv66vv////8=</Value>

</CustomSupplierParameter>

<CustomSupplierParameter>

<Supplier>ezy</Supplier>

<Name>SCACResTransStatus</Name>

<Value>Y</Value>

</CustomSupplierParameter>

<CustomSupplierParameter>

<Supplier>ezy</Supplier>

<Name>SCADSTransID</Name>

<Value>bc26909a-9a97-4eb4-a56a-aa590dba3c9f</Value>

</CustomSupplierParameter>

<CustomSupplierParameter>

<Supplier>ezy</Supplier>

<Name>SCAECI</Name>

<Value>05</Value>

</CustomSupplierParameter>

<CustomSupplierParameter>

<Supplier>ezy</Supplier>

<Name>SCAMessageVersion</Name>

<Value>2.1.0</Value>

</CustomSupplierParameter>

<CustomSupplierParameter>

<Supplier>ezy</Supplier>

<Name>SCAThreeDSServerTransID</Name>

<Value>f8062b92-66e9-4c5a-979a-f465e66a6e48</Value>

</CustomSupplierParameter>

</CustomSupplierParameterList>

</BookingProfile>

</StartBooking>

</CommandList>

Below is the table containing the relevant SCA CSPs for both 3DS 1.0 and 3DS 2.0 versions: