Client Class

Properties   Methods   Events   Config Settings   Errors  

The Client class is designed for use on mobile devices and facilitates EMV® 3-D Secure authentication.

Syntax

ipworks3ds.Client

Remarks

The Client class is a counterpart to the 3DS Server class. It is designed for use on mobile devices and supports operations that facilitate EMV® 3-D Secure authentication in both frictionless and challenge flows.

Preparing the Authentication Request

To begin, device specific information must be collected and prepared for transmission to the directory server. This can be done by calling the AddDeviceParam method. Consult the EMV® 3-D Secure Specifications for more details about applicable device parameters for each particular operating system.

The GetAuthRequest method is used to obtain the request message to be send to the directory server. GetAuthRequest encrypts the device info and prepares all the data necessary to be sent by the 3DS Server class in the SendAuthRequest method.

After calling this method, the returned data must be transmitted via a separate secure channel to the server where 3DS Server is being used.

The following properties are required before calling the method:

Calling this method returns required information used by 3DS Server to send the authentication request. Transmit the value returned by this method to the system where 3DS Server is used. The method used to transmit this value is outside the scope of the class.

See SendAuthRequest for details on sending the authentication request after transmitting the data to the 3DS Server.

Calling this method also populates SDKTransactionId which uniquely identifies this transaction and must be used in subsequent calls relating to this transaction, such as SendChallengeRequest.

Interaction With the 3DS Server Class

As mentioned above, the request to the Directory Server must be made by the 3DS Server class which resides on a server under control of the merchant. A web server is required even for app-based authentication both to send the authentication request and to be notified of authentication results later in the flow.

It is expected that a secure channel can be established between the app using the Client class and the server where the 3DS Server class resides in order to transfer information freely.

Sending the Authentication Request

The act of sending the authentication request takes place with the 3DS Server class.

SendAuthRequest begins the 3-D Secure transaction flow by sending an authentication request to the DirectoryServerURL.

After calling this method, check TransactionStatus to determine if the cardholder is authenticated (frictionless flow) or further cardholder interaction is required to complete the authentication (challenge flow).

Prior to calling SendAuthRequest, data must to be collected to facilitate fraud checks by the ACS. The following properties are applicable for both app-based and browser-based flows:

• AcquirerBIN (required)
• AcquirerMerchantId (required)
• CardholderName (required)
• CardNumber (required)
• DirectoryServerURL (required)
• MerchantCategoryCode (required)
• MerchantCountryCode (required)
• MerchantName (required)
• MessageVersion (required)
• PurchaseAmount (required)
• PurchaseDate (required)
• RequestorId (required)
• RequestorName (required)
• RequestorURL (required)
• ResultsURL (required)
• AccountType
• AuthenticationIndicator
• BillingAddress
• CardholderEmail
• CardholderHomePhone
• CardholderMobilePhone
• CardholderWorkPhone
• DecoupledMaxTimeout
• DecoupledRequestIndicator
• DeviceChannel
• MessageCategory
• PurchaseCurrency
• PurchaseExponent
• ServerOperatorId
• ServerTransactionId
• ShippingAddress
• ThreeRIIndicator

App-Based Flow

In the app-based flow, device specific information is prepared by the 3DS SDK on the customer's device. This is transmitted to the 3DS Server class via a secure channel, the specifics of which are outside the scope of the classs. Set ClientAuthRequest to this data prepared by the 3DS SDK.

Browser-Based Flow

Before calling this method, first check the cached card-range data to determine if a MethodURL has been set by the ACS. Card range data may be retrieved by calling RequestCardRanges.

If no MethodURL is present for the given card, set MethodCompletionIndicator to U.

If a MethodURL has been specified by the ACS for the card number, the URL must be loaded in the cardholder's browser to allow the ACS to collect additional browser information for risk-based decision making. See the GetMethodData for further details.

Once the method URL invocation is complete, the authentication request may be sent. If the method URL invocation failed, set MethodCompletionIndicator to N before calling SendAuthRequest.

The following additional properties are applicable in browser-based flow:

• NotificationURL (required)
• BrowserAcceptHeader (required)
• BrowserLanguage (required)
• BrowserScreenHeight (required in 2.1.0, required in 2.2.0 and 2.3.1 if BrowserJavaScriptEnabled is true)
• BrowserScreenWidth (required in 2.1.0, required in 2.2.0 and 2.3.1 if BrowserJavaScriptEnabled is true)
• BrowserTimeZone (required in 2.1.0, required in 2.2.0 and 2.3.1 if BrowserJavaScriptEnabled is true)
• BrowserUserAgent (required)
• BrowserIPAddress (conditional)
• BrowserJavaEnabledVal (required in 2.1.0, required in 2.2.0 and 2.3.1 if BrowserJavaScriptEnabled is true)
• BrowserJavaScriptEnabledVal (not valid in 2.1.0, required in 2.2.0 and 2.3.1)
• BrowserScreenColorDepth (required in 2.1.0, required in 2.2.0 and 2.3.1 if BrowserJavaScriptEnabled is true)
• AcceptLanguage (2.3.1 only)
• AcquirerCountryCode (2.3.1 only)

Response Handling

After calling this method the TransactionStatus property holds the result. Possible values are:

If the transaction is authenticated (Y or A), no further steps are required. The flow is considered frictionless and the 3-D Secure processing is complete. If processing a payment, the AuthenticationValue and AuthenticationECI values can be included as proof of 3-D Secure authentication.

If the transaction requires a cardholder challenge (C, D or S), further steps are required.

If the transaction is not authenticated, TransactionStatusReason may contain details about the reason.

The following properties are applicable after calling this method:

• AuthenticationECI
• AuthenticationValue
• TransactionStatus
• TransactionStatusReason
• CardholderInformation
• ACSURL (if challenge required)
• ACSChallengeMandatedIndicator (if challenge required)
• AuthenticationType (if challenge required)
• DecoupledConfirmationIndicator

Response Handling - App-Based Flow

After calling this method, ClientAuthResponse is populated with data to be transmitted back to the 3DS SDK. If a challenge is required, the ClientAuthResponse data is used by the 3DS SDK to start when initiating the challenge process.

The 3DS Server is responsible for indicating to the 3DS SDK the results of the SendAuthRequest process, and whether or not a challenge is required. Exactly how this is done is outside the scope of the classs themselves. The response to the 3DS SDK over the secure channel should include information on what to do next.

Note: The TransactionStatus is also populated in the 3DS Server class and may be inspected prior to transmitting ClientAuthResponse back to the 3DS SDK.

Response Handling - Browser-Based Flow

If TransactionStatus is C, then additional steps are required to complete the authentication. The GetChallengeRequest method should be called next to obtain data to be sent to the ACSURL in an authentication window in the customer's browser. Once authentication is complete, the ACS will post the results to the ResultsURL value that was specified when calling SendAuthRequest.

See the GetChallengeRequest method for more details.

If TransactionStatus is D, then decoupled authentication has been accepted by the ACS. DecoupledConfirmationIndicator will have a value of Y as well. Authentication will happen outside of the 3-D Secure flow and, when complete, the ACS will post the results to the ResultsURL that was specified when calling SendAuthRequest.

The DecoupledTimeRemaining value, which is calculated based on the DecoupledMaxTimeout value sent in the initial authentication request, can be checked to see the amount of time remaining before decoupled authentication must be completed. If the ACS does not post the results before this value runs out, it can be assumed that decoupled authentication was not successful.

SPC-Based Authentication

SPC (Secure Payment Confirmation) provides a method to perform a challenge using preestablished FIDO credentials when using a Browser. The SPC authentication can be initiated by the 3DS Requestor via an extra AReq/ARes message pair or by the ACS via a standard Browser Challenge Flow.

For an SPC authentication to execute correctly, the following prerequisites apply:

1. The ACS has an enrolled FIDO authenticator on the device for this Cardholder.
2. The 3DS Requestor and/or the ACS have detected that the Cardholder Browser supports the related SPC APIs (allow="payment *; publickey-credentialsget *"). For the ACS, this information can be obtained via the Browser User Agent data element or via data obtained via the 3DS Method.

SPC-based authentication can be enabled with the following additions:

Prior to sending the initial authentication request packet (AReq) using the SendAuthRequest method, the ThreeDSRequestorSpcSupport configuration setting should be set to True to indicate that SPC is supported by the 3DS Requestor.

If SPC is accepted by the ACS, the resulting TransactionStatus should be S. The response will also contain a list of enrolled FIDO (WebAuthn) credentials associated with the cardholder, and SPC transaction data. This data is available in the following configuration settings:

• WebAuthnCredentialListCount
• WebAuthnCredentialListWebAuthnCredential
• WebAuthnCredentialListRelyingPartyId
• SPCTransactionAdditionalData
• SPCTransactionChallenge
• SPCTransactionChallengeInfoText
• SPCTransactionCurrency
• SPCTransactionDisplayName
• SPCTransactionIcon
• SPCTransactionIssuerImage
• SPCTransactionIssuerImageDark
• SPCTransactionIssuerImageMonochrome
• SPCTransactionPayeeName
• SPCTransactionPayeeOrigin
• SPCTransactionPSImage
• SPCTransactionPSImageDark
• SPCTransactionPSImageMonochrome
• SPCTransactionTimeout
• SPCTransactionValue

This information is relayed to the 3DS Requestor implementation, and the 3DS Requestor invokes the SPC authentication (SPC API) against the WebAuthn Credential list. The cardholder authenticates using the FIDO authenticator on their device, and the 3DS Requestor retrieves the Assertion Data from the SPC API call.

The 3DS Server is then configured to includes this FIDO Assertion Data is then included in a new authentication request by setting the ReqAuthData[Index] and a ReqAuthMethod[Index] of 09. If the AuthenticationInformation value was saved earlier, it can be set via the same configuration setting. If the 3DS Requestor encounters an error during SPC API invokation, this can be indicated using the SPCIncompletionIndicator.

The SendAuthRequest method should then be called again to transmit this data to the ACS (by way of the DS) in a second AReq.

When SendAuthRequest returns, the 3DS Server proceed the same as the regular browser-based flow when the ARes is returned.

When SPC authentication is to be performed, the authenticaton must be completed within 9 minutes. The component will automatically start an internal timer that can be checked using the CheckSPCTimeout configuration setting. This will return the number of seconds left for SPC authentication to complete. If the time has expired before receiving the Assertion Data from the 3DS Requestor, checking this configuration setting will cause the component to automatically send the second AReq message with an SPCIncompletionIndicator value of 03, indicating that SPC authentication timed out.

Note that SPC-based authentication is only available when a MessageVersion of 2.3.1 is used.

Processing the Authentication Response

After the response to the authentication request is received from the 3DS Server class, call CheckAuthResponse to verify and parse the response. See the 3DS Server's SendAuthRequest method for details about obtaining the response.

Before calling this method, ACSRootCerts must be populated with the root certificates used by the ACS to sign the response. This method will validate the signature of the signed content if present.

After calling this method, inspect TransactionStatus to determine if the transaction requires a challenge. If TransactionStatus is C, a challenge is required and SendChallengeRequest should be called to proceed with the challenge flow. If TransactionStatus is D, decoupled authentication will take place outside of the 3-D Secure flow and the results will be posted to the 3DS Server.

If TransactionStatus is Y or A, the transaction is complete.

Challenge Interaction

If TransactionStatus is C, a challenge is required. The challenge takes place between the cardholder and the ACS. During this interaction the class will communicate directly with the ACS from the app where it is used to exchange information.

SendChallengeRequest begins the challenge flow. SendChallengeRequest sends the Challenge Request to the ACS when a challenge is required.

When the TransactionStatus is C after calling CheckAuthResponse, a challenge to the cardholder is required. This method sends the challenge request and parses the response. The ACS may provide multiple challenges to the cardholder during this process. As a result this method may need to be called multiple times throughout the authentication process.

After this method is called, check ChallengeComplete to determine if the challenge process is complete. If it is complete (True), check TransactionStatus to determine the outcome. If ChallengeComplete is False, additional challenge interaction is required.

First Request

The first time this method is called, information about the required challenge is obtained from the ACS. The ACS connection information is automatically set when CheckAuthResponse is called; there is no need to specify any ACS connection information.

All required properties for the first call to this method are automatically set after CheckAuthResponse is called. If the transaction has been canceled, set ChallengeCancellationIndicator to inform the ACS.

After calling this method, the ACS will respond with details about the challenge to be presented to the cardholder. The ACSUIType property indicates the way the ACS will interact with the cardholder. The ChallengeComplete property will be False after the first call to this method since the challenge interaction is not yet complete.

The following properties are applicable when ACSUIType is Text (01), Single-Select (02), or Multi-Select (03):

• ChallengeSelectInfo
• ChallengeInfoHeader
• ChallengeInfoLabel
• ChallengeInfoText
• EnableChallengeInfoTextIndicator
• ExpandableInformationLabel
• ExpandableInformationText
• IssuerImage1
• IssuerImage2
• IssuerImage3
• PaymentSystemImage1
• PaymentSystemImage2
• PaymentSystemImage3
• ResendInformationLabel
• SubmitAuthenticationLabel
• WhyInformationLabel
• WhyInformationText

Use the values in the above properties to populate values in the native UI in the app. The UI must follow the guidelines defined in the EMV® 3-D Secure specification.

The following properties are applicable when ACSUIType is Out-of-Band (04):

• ChallengeAdditionalInformation
• ChallengeInfoHeader
• ChallengeInfoLabel
• ChallengeInfoText
• EnableChallengeInfoTextIndicator
• ExpandableInformationLabel
• ExpandableInformationText
• IssuerImage1
• IssuerImage2
• IssuerImage3
• OOBContinueLabel
• PaymentSystemImage1
• PaymentSystemImage2
• PaymentSystemImage3
• ResendInformationLabel
• WhyInformationLabel
• WhyInformationText

Use the values in the above properties to populate values in the native UI in the app. The UI must follow the guidelines defined in the EMV® 3-D Secure specification.

The following properties are applicable when ACSUIType is HTML (05):

• ACSHTML
• ACSHTMLRefresh

In the case of an HTML interaction, the app should create a webview and populate this with the HTML in ACSHTML.

As per the EMV® 3-D Secure specification, the HTML UI is presented to the cardholder via a web view which remains in control of the app. The app must intercept any remote URL requests made from within the web view, and instead handle them within the app. Preventing the cardholder from making requests in the web view to another server is critical to the security of the environment. According to the EMVCo specification, intercepting these requests has two effects:

• Prevents malicious HTML from redirecting a user to a phishing site.
• Conceptually puts the web view form under the control of the ACS, rather than the app.

• Navigation attempts from within the web view must be captured by the app and handled internally. This includes all requests including images, javascript files, css, etc.
• The web view element is not utilized as a browser, but as a UI element whose content is provided by the ACS.

Second Request

The second time this method is called, the purpose is to provide a response to the ACS. At this point the customer should have responded to the challenge provided by the ACS in the response to the first call. If the transaction has been canceled, set ChallengeCancellationIndicator to inform the ACS. The following properties are applicable when calling this method the second time:

• ChallengeDataEntry
• OOBContinuationIndicator

When ACSUIType is Text (01) or HTML (05), set ChallengeDataEntry to the data exactly as it was specified by the cardholder. Do not format or otherwise change the data.

When ACSUIType is Single-Select (02), set ChallengeDataEntry to the name of the selected option. For instance the ACS may provide the user with a selection like:

mobile: **** **** 329
email: s******k**@g***.com

When ACSUIType is Multi-Select (03), set ChallengeDataEntry to a comma-separated list of names of the selected options. For instance if ChallengeSelectInfo contains elements with names like chicago_illinois, st_louis_missouri, and portland_oregon, and the user chose two options, the value specified in ChallengeDataEntry would be chicago_illinois,portland_oregon.

When ACSUIType is OOB (04), set OOBContinuationIndicator to True to indicate the cardholder has pressed the button signaling their completing of the OOB process.

Completing the Challenge

After calling SendChallengeRequest a second time with the cardholder's responses, the ACS may require additional challenges. Check the ChallengeComplete property to determine if the challenge is complete. If False, more challenges are required by the ACS and the same process of displaying the challenge info, collecting the response, and submitting it to the ACS should be performed again.

If ChallengeComplete is True, the challenge interaction is complete and TransactionStatus can be inspected to determine whether the transaction was successful.

Note: As part of the challenge completion the ACS also notifies the 3DS Server of the results. This is done by posting the results to the URL defined by the ResultsURL property of the 3DS Server class.

Logging Notes

Logging in the component is handled through the Log event. This will fire anytime a message is built or a response is parsed, including error messages.

When the Log event is fired, the message in question is made available via the Message event parameter. Properties such as EphemeralKey and DeviceParams are also available when they are gathered by the Client. The other event arguments are LogType and LogLevel:

The LogType parameter indicates the type of the log entry. Possible values are:

• "Info"
• "RequestHeaders"
• "ResponseHeaders"
• "RequestBody"
• "ResponseBody"
• "ProxyRequest"
• "ProxyResponse"
• "FirewallRequest"
• "FirewallResponse"
• "AReq"
• "ARes"
• "CReq"
• "CRes"
• "RReq"
• "RRes"
• "PReq"
• "PRes"
• "Erro"
• "EphemeralKey"
• "DeviceParams"

It is recommended to output all messages raised in this event to a file for record keeping purposes, or for later debugging issues that may have come up.

The Server and Client components also have DataPacketIn and DataPacketOut events that fire anytime a data packet is received or sent, respectively. The entire data packet is then accessible in the DataPacket event parameter. For encrypted packets, this would contain the full encrypted data. This parameter may be inspected for advanced troubleshooting.

Property List

The following is the full list of the properties of the class with short descriptions. Click on the links for further details.

Method List

The following is the full list of the methods of the class with short descriptions. Click on the links for further details.

Event List

The following is the full list of the events fired by the class with short descriptions. Click on the links for further details.

Config Settings

The following is a list of config settings for the class with short descriptions. Click on the links for further details.

ACSHTML Property (Client Class)

HTML provided by the ACS.

Syntax

public String getACSHTML();

Default Value

""

Remarks

This field contains HTML provided by the ACS in the Challenge Response Message (CRes). This will be populated when the ACSUIType is HTML.

As per the EMV® 3-D Secure specification, the HTML UI is presented to the cardholder via a web view which remains in control of the app. The app must intercept any remote URL requests made from within the web view, and instead handle them within the app. Preventing the cardholder from making requests in the web view to another server is critical to the security of the environment. According to the EMVCo specification, intercepting these requests has two effects:

• Prevents malicious HTML from redirecting a user to a phishing site.
• Conceptually puts the web view form under the control of the ACS, rather than the app.

• Navigation attempts from within the web view must be captured by the app and handled internally. This includes all requests including images, javascript files, css, etc.
• The web view element is not utilized as a browser, but as a UI element whose content is provided by the ACS.

This property is read-only.

ACSHTMLRefresh Property (Client Class)

ACS HTML refresh.

Syntax

public String getACSHTMLRefresh();

Default Value

""

Remarks

Optional HTML provided by the ACS in response to SendChallengeRequest when ACSUIType is HTML (05).

If the ACS HTML Refresh is present in the CRes message, the app should display this in the web view when the app is moved to the foreground.

This property is read-only.

ACSRootCerts Property (Client Class)

A collection of trusted CA certificates.

Syntax

public CertificateList getACSRootCerts();
public void setACSRootCerts(CertificateList ACSRootCerts);

Remarks

This setting holds a collection of Certificates used to verify data sent by the ACS.

Set this property to one or more Root certificates from the ACS before calling CheckAuthResponse.

This property is not available at design time.

ACSUIType Property (Client Class)

UI type rendered by the 3DS SDK.

Syntax

public int getACSUIType();

Default Value

0

Remarks

This field is returned in the Challenge Response Message (CRes) from the ACS and contains the User Interface type that the 3DS SDK will render. 1 = Text 2 = Single Select 3 = Multi Select 4 = OOB 5 = HTML 6 = HTML OOB 7 = Information

This property is read-only.

ChallengeAdditionalInformation Property (Client Class)

Challenge additional information text.

Syntax

public String getChallengeAdditionalInformation();

Default Value

""

Remarks

Text provided by the ACS/Issuer to the cardholder during OOB authentication to replace challenge information text and challenge information text indicator in the OOB template.

This property is read-only.

ChallengeAdditionalLabel Property (Client Class)

Challenge Additional Label.

Syntax

public String getChallengeAdditionalLabel();

Default Value

""

Remarks

UI label for the additional choice button provided by the ACS.

This property is read-only.

ChallengeCancellationIndicator Property (Client Class)

Challenge Cancellation Indicator.

Syntax

public String getChallengeCancellationIndicator();
public void setChallengeCancellationIndicator(String challengeCancellationIndicator);

Default Value

""

Remarks

This field is an indicator informing the ACS and the DS that the authentication has been canceled. This is required to be set if the authentication transaction was canceled by the user. This may also be received in the Results Request from the directory server if the ACS identifies that the authentication transaction was canceled for reasons as indicated.

Possible values include:

ChallengeComplete Property (Client Class)

Whether or not the challenge cycle is complete.

Syntax

public boolean isChallengeComplete();

Default Value

False

Remarks

Present in the Challenge Response Message (CRes) and indicates whether the challenge cycle is complete or will require additional messages. If true, the TransactionStatus will be populated as well.

This property is read-only.

ChallengeDataEntry Property (Client Class)

Cardholder entered data.

Syntax

public String getChallengeDataEntry();
public void setChallengeDataEntry(String challengeDataEntry);

Default Value

""

Remarks

This field contains the data that the cardholder entered into the UI.

When ACSUIType is Text (01) or HTML (05), set ChallengeDataEntry to the data exactly as it was specified by the cardholder. Do not format or otherwise change the data.

When ACSUIType is Single-Select (02), set ChallengeDataEntry to the name of the selected option. For instance the ACS may provide the user with a selection like:

mobile: **** **** 329
email: s******k**@g***.com

When ACSUIType is Multi-Select (03), set ChallengeDataEntry to a comma-separated list of names of the selected options. For instance if ChallengeSelectInfo contains elements with names like chicago_illinois, st_louis_missouri, and portland_oregon, and the user chose two options, the value specified in ChallengeDataEntry would be chicago_illinois,portland_oregon.

ChallengeDataEntryTwo Property (Client Class)

Cardholder entered data.

Syntax

public String getChallengeDataEntryTwo();
public void setChallengeDataEntryTwo(String challengeDataEntryTwo);

Default Value

""

Remarks

This field contains the data that the cardholder entered into the UI.

When ACSUIType is Text (01) or HTML (05), set ChallengeDataEntry to the data exactly as it was specified by the cardholder. Do not format or otherwise change the data.

When ACSUIType is Single-Select (02), set ChallengeDataEntry to the name of the selected option. For instance the ACS may provide the user with a selection like:

mobile: **** **** 329
email: s******k**@g***.com

When ACSUIType is Multi-Select (03), set ChallengeDataEntry to a comma-separated list of names of the selected options. For instance if ChallengeSelectInfo contains elements with names like chicago_illinois, st_louis_missouri, and portland_oregon, and the user chose two options, the value specified in ChallengeDataEntry would be chicago_illinois,portland_oregon.

ChallengeEntryBox Property (Client Class)

First entry box settings.

Syntax

public ChallengeTextBox getChallengeEntryBox();

Remarks

Defines the settings for the first entry box in the Native UI OTP/Text Template.

This property is read-only and not available at design time.

ChallengeEntryBoxTwo Property (Client Class)

Second entry box settings.

Syntax

public ChallengeTextBox getChallengeEntryBoxTwo();

Remarks

Defines the settings for the second entry box in the Native UI OTP/Text Template.

This property is read-only and not available at design time.

ChallengeInfoHeader Property (Client Class)

Challenge information screen header.

Syntax

public String getChallengeInfoHeader();

Default Value

""

Remarks

This field contains the header text for the challenge information screen that is being presented.

This property is read-only.

ChallengeInfoLabel Property (Client Class)

Challenge information label.

Syntax

public String getChallengeInfoLabel();

Default Value

""

Remarks

This field contains the label to modify the challenge data entry field provided by the issuer. If this field is populated, it should be displayed to the cardholder.

This property is read-only.

ChallengeInfoText Property (Client Class)

Challenge information text.

Syntax

public String getChallengeInfoText();

Default Value

""

Remarks

This field contains text provided by the ACS/Issuer to the cardholder during the challenge message exchange. If this field is populated, it should be displayed to the cardholder.

This property is read-only.

ChallengeSelectInfo Property (Client Class)

Challenge selection information.

Syntax

public ChallengeSelectInfoList getChallengeSelectInfo();

Remarks

This property holds a collection of name/value pairs to be displayed to the cardholder as selectable options when ACSUIType is Single-Select (02) or Multi-Select (03).

This property is read-only and not available at design time.

DataPacketOut Property (Client Class)

Contains the data packet sent to the server.

Syntax

public String getDataPacketOut();

Default Value

""

Remarks

After calling either the RequestCardRanges, or SendAuthRequest methods, this property will contain the entire data packet that was sent. Also, after calling the GetChallengeRequest or GetResultsResponse method, this property will contain the constructed messages. The contents of this property should be logged for each transaction.

This property is read-only and not available at design time.

DeviceBindingDataEntry Property (Client Class)

Device Binding Data Entry.

Syntax

public boolean isDeviceBindingDataEntry();
public void setDeviceBindingDataEntry(boolean deviceBindingDataEntry);

Default Value

False

Remarks

Indicator provided by the 3DS SDK to the ACS to confirm whether the Cardholder gives consent to bind the device.

DeviceBindingInformationText Property (Client Class)

Device binding information text.

Syntax

public String getDeviceBindingInformationText();

Default Value

""

Remarks

Text provided by the ACS to the Cardholder during the Device Binding process.

This property is read-only.

DeviceParams Property (Client Class)

Device information parameters.

Syntax

public DeviceParamList getDeviceParams();
public void setDeviceParams(DeviceParamList deviceParams);

Remarks

This collection contains device information parameters that are used in the app flow to provide device information to the directory server. Parameters can be added manually or using the AddDeviceParam method. More information can be found in the documentation for the AddDeviceParam method.

DirectoryServerCert Property (Client Class)

Directory Server public key certificate.

Syntax

public Certificate getDirectoryServerCert();
public void setDirectoryServerCert(Certificate directoryServerCert);

Remarks

Public key generated by the DS Certificate Authority, which is typically operated by the Payment System responsible for a specific DS. The key is identified based on the DirectoryServerId. Required to encrypt DeviceParams when building AReq.

DirectoryServerId Property (Client Class)

Value of the Registered Application Provider Identifier (RID) unique to the payment system.

Syntax

public String getDirectoryServerId();
public void setDirectoryServerId(String directoryServerId);

Default Value

""

Remarks

Registered Application Provider Identifier (RID) value defined by the ISO 7816-5 standard for uniquely registering such providers. This value is unique to the Payment System involved and must be known by the 3DS Requestor App so that it may be passed to the SDK on when it invokes the createTransaction method within the SDK. Used to identify the DirectoryServerCert for the given DS which is used by the SDK to encrypt the Device Information. Required when DirectoryServerCert is an EC key.

DirectoryServerKeyId Property (Client Class)

Directory Server Key Identifier (kid).

Syntax

public String getDirectoryServerKeyId();
public void setDirectoryServerKeyId(String directoryServerKeyId);

Default Value

""

Remarks

Used to specify the Directory Server Key Identifier. There may be multiple keys for each DS, with each key having a unique identifier.

EnableChallengeInfoTextIndicator Property (Client Class)

Challenge information text indicator.

Syntax

public boolean isEnableChallengeInfoTextIndicator();

Default Value

False

Remarks

This field indicates when the ACS/Issuer would like a warning icon or similar visual indicator to draw attention to the ChallengeInfoText that is being displayed. If this field is populated, it should affect the information being displayed to the cardholder.

This property is read-only.

ErrorPacket Property (Client Class)

The error packet.

Syntax

public String getErrorPacket();

Default Value

""

Remarks

If an error is encountered while parsing a received packet using the CheckResponse method, this field will be populated with an error packet to be sent back to the server.

If the message being parsed is an error, this field will be populated with the received error packet itself.

This property is read-only.

ExpandableInformationLabel Property (Client Class)

Expandable information label.

Syntax

public String getExpandableInformationLabel();

Default Value

""

Remarks

Label displayed to the cardholder for the content in ExpandableInformationText.

This property is read-only.

ExpandableInformationText Property (Client Class)

Expandable information text.

Syntax

public String getExpandableInformationText();

Default Value

""

Remarks

This field contains text provided by the Issuer from the ACS to be displayed to the cardholder for additional information. The format should be an expandable text field.

This property is read-only.

Extensions Property (Client Class)

Extensions to be included in the next outgoing packet.

Syntax

public ExtensionList getExtensions();
public void setExtensions(ExtensionList extensions);

Remarks

Data necessary to support requirements not otherwise defined in the 3-D Secure message are carried in Message Extensions. This collection contains extension data to be included in the next outgoing request. Extensions can be added manually or using the AddExtension method.

Note: The maximum number of extensions is 10.

IssuerImage1 Property (Client Class)

Issuer image URL 1.

Syntax

public String getIssuerImage1();

Default Value

""

Remarks

Sent in the initial CRes message from the ACS to the 3DS SDK to provide the URL(s) of the issuer logo or image to be used in the Native UI. before 2.3.1: Medium Density Image in 2.3.1: Default Image

This property is read-only and not available at design time.

IssuerImage2 Property (Client Class)

Issuer image URL 2.

Syntax

public String getIssuerImage2();

Default Value

""

Remarks

Sent in the initial CRes message from the ACS to the 3DS SDK to provide the URL(s) of the issuer logo or image to be used in the Native UI. before 2.3.1: High Density Image in 2.3.1: Dark Mode Image

This property is read-only and not available at design time.

IssuerImage3 Property (Client Class)

Issuer image URL 3.

Syntax

public String getIssuerImage3();

Default Value

""

Remarks

Sent in the initial CRes message from the ACS to the 3DS SDK to provide the URL(s) of the issuer logo or image to be used in the Native UI. before 2.3.1: Extra High-Density Image in 2.3.1: Monochrome Image

This property is read-only and not available at design time.

MessageVersion Property (Client Class)

Message version.

Syntax

public String getMessageVersion();
public void setMessageVersion(String messageVersion);

Default Value

"2.1.0"

Remarks

This field indicates the protocol version. This should be the protocol version number of the specification utilized by the system creating this message.

Possible values are:

OOBAppLabel Property (Client Class)

OOB App label.

Syntax

public String getOOBAppLabel();

Default Value

""

Remarks

Label to be displayed for the link to the OOB App URL. For example: "Click here to open Your Bank App."

This property is read-only.

OOBAppStatus Property (Client Class)

OOB App status.

Syntax

public int getOOBAppStatus();
public void setOOBAppStatus(int OOBAppStatus);

Default Value

0

Remarks

Status code indicating the problem type encountered when using the OOB App URL. 1 = Open OOB App URL failed

OOBAppURL Property (Client Class)

OOB App label.

Syntax

public String getOOBAppURL();

Default Value

""

Remarks

Universal App Link to an authentication app used in the OOB authentication. The OOB App URL will open the appropriate location within the OOB Authentication App.

This property is read-only.

OOBAppURLIndicator Property (Client Class)

OOB App URL Indicator.

Syntax

public int getOOBAppURLIndicator();
public void setOOBAppURLIndicator(int OOBAppURLIndicator);

Default Value

1

Remarks

Indicates if the 3DS SDK supports the OOB App URL. 01 = Supported 02 = Not supported by the device 03 = Not supported by the 3DS Requestor

OOBContinuationIndicator Property (Client Class)

OOB continuation indicator.

Syntax

public int getOOBContinuationIndicator();
public void setOOBContinuationIndicator(int OOBContinuationIndicator);

Default Value

0

Remarks

An indicator notifying the ACS that the cardholder has completed the authentication as requested by selecting the continue button in an out-of-band (OOB) authentication method. This is exclusive to the app flow and required when the ACSUIType is set to OOB when the user has selected the continue option on the device.

OOBContinueLabel Property (Client Class)

OOB continuation label.

Syntax

public String getOOBContinueLabel();

Default Value

""

Remarks

Label to be used in the UI for the button that the user selects when they have completed the OOB authentication.

This property is read-only.

PaymentSystemImage1 Property (Client Class)

Payment system image URL 1.

Syntax

public String getPaymentSystemImage1();

Default Value

""

Remarks

Sent in the initial CRes message from the ACS to the 3DS SDK to provide the URL(s) of the directory server or payment system logo or image to be used in the Native UI. before 2.3.1: Medium Density Image in 2.3.1: Default Image

This property is read-only and not available at design time.

PaymentSystemImage2 Property (Client Class)

Payment system image URL 2.

Syntax

public String getPaymentSystemImage2();

Default Value

""

Remarks

Sent in the initial CRes message from the ACS to the 3DS SDK to provide the URL(s) of the directory server or payment system logo or image to be used in the Native UI. before 2.3.1: High Density Image in 2.3.1: Dark Mode Image

This property is read-only and not available at design time.

PaymentSystemImage3 Property (Client Class)

Payment system image URL 3.

Syntax

public String getPaymentSystemImage3();

Default Value

""

Remarks

Sent in the initial CRes message from the ACS to the 3DS SDK to provide the URL(s) of the directory server or payment system logo or image to be used in the Native UI. before 2.3.1: Extra High-Density Image in 2.3.1: Monochrome Image

This property is read-only and not available at design time.

Proxy Property (Client Class)

A set of properties related to proxy access.

Syntax

public Proxy getProxy();
public void setProxy(Proxy proxy);

Remarks

This property contains fields describing the proxy through which the class will attempt to connect.

RequestorAppURL Property (Client Class)

3DS Requestor App URL.

Syntax

public String getRequestorAppURL();
public void setRequestorAppURL(String requestorAppURL);

Default Value

""

Remarks

3DS Requestor App declaring its URL within the CReq message so that the Authentication app can call the 3DS Requestor App after OOB authentication has occurred. Note: When providing the 3DS Requestor App URL, the 3DS Requestor needs to properly register the URL with the Operating System.

ResendInformationLabel Property (Client Class)

Label for UI button allowing users to request that authentication information be resent.

Syntax

public String getResendInformationLabel();

Default Value

""

Remarks

Value of text to be displayed on the UI label on the button users click for authentication information to be resent. Sent in CRes if the ACS allows the Cardholder to request such information to be resent. App-based only.

This property is read-only.

SDKAppId Property (Client Class)

The unique SDK App Id.

Syntax

public String getSDKAppId();
public void setSDKAppId(String SDKAppId);

Default Value

""

Remarks

This property must be set to a universally unique Id created for a specific installation of the app on a consumer device. The app is responsible for generating and storing the SDKAppId for each installation or update. This property must be set before calling GetAuthRequest.

The value assigned here must be 36 characters and be in the format defined in IETF RFC 4122. For example: 8a880dc0-d2d2-4067-bcb1-b08d1690b26e.

SDKTransactionId Property (Client Class)

SDK Transaction ID.

Syntax

public String getSDKTransactionId();
public void setSDKTransactionId(String SDKTransactionId);

Default Value

""

Remarks

This field contains the universally unique transaction identifier assigned by the 3DS SDK to identify a single transaction. This is generated by the class when calling the GetAuthRequest method. Shall be provided to the 3DS Server for the purpose of uniquely identifying this transaction within all messages of the authentication process, beginning with the AReq sent by the Server.

SSLAcceptServerCert Property (Client Class)

Instructs the class to unconditionally accept the server certificate that matches the supplied certificate.

Syntax

public Certificate getSSLAcceptServerCert();
public void setSSLAcceptServerCert(Certificate SSLAcceptServerCert);

Remarks

If it finds any issues with the certificate presented by the server, the class will normally terminate the connection with an error.

You may override this behavior by supplying a value for SSLAcceptServerCert. If the certificate supplied in SSLAcceptServerCert is the same as the certificate presented by the server, then the server certificate is accepted unconditionally, and the connection will continue normally.

Note: This functionality is provided only for cases in which you otherwise know that you are communicating with the right server. If used improperly, this property may create a security breach. Use it at your own risk.

SSLCert Property (Client Class)

The certificate to be used during Secure Sockets Layer (SSL) negotiation.

Syntax

public Certificate getSSLCert();
public void setSSLCert(Certificate SSLCert);

Remarks

This property includes the digital certificate that the class will use during SSL negotiation. Set this property to a valid certificate before starting SSL negotiation. To set a certificate, you may set the Encoded field to the encoded certificate. To select a certificate, use the store and subject fields.

SSLServerCert Property (Client Class)

The server certificate for the last established connection.

Syntax

public Certificate getSSLServerCert();

Remarks

This property contains the server certificate for the last established connection.

SSLServerCert is reset every time a new connection is attempted.

This property is read-only.

SubmitAuthenticationLabel Property (Client Class)

Label for UI button users select to submit authentication.

Syntax

public String getSubmitAuthenticationLabel();

Default Value

""

Remarks

Value of text to be displayed on the UI label on the button users click to submit the authentication information they have entered. Sent in CRes if ACSUIType is 01 (Text), 02 (Single Select) or 02 (Multi Select). App-based only.

This property is read-only.

Timeout Property (Client Class)

A timeout for the class.

Syntax

public int getTimeout();
public void setTimeout(int timeout);

Default Value

30

Remarks

If the Timeout property is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered.

If Timeout is set to a positive value, the class will wait for the operation to complete before returning control.

The class will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive.

If Timeout expires, and the operation is not yet complete, the class throws an exception.

Note: By default, all timeouts are inactivity timeouts, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.

The default value for the Timeout property is 30 seconds.

TogglePositionIndicator Property (Client Class)

Toggle Position Indicator.

Syntax

public int getTogglePositionIndicator();

Default Value

0

Remarks

Indicates if the Trust List and/or Device Binding prompt should be presented below or above the action buttons.

This property is read-only.

TransactionStatus Property (Client Class)

The transaction status from the last parsed message (ARes, RReq, or CRes).

Syntax

public String getTransactionStatus();

Default Value

""

Remarks

Indicates whether a transaction qualifies as an authenticated transaction or account verification. Possible values are:

Note: The CRes message can contain only a value of Y or N. Values of D and I are only applicable for 3DS version 2.2.0.

This property is read-only.

UseAdditionalChallenge Property (Client Class)

Whether or not the additional choice button is selected.

Syntax

public boolean isUseAdditionalChallenge();
public void setUseAdditionalChallenge(boolean useAdditionalChallenge);

Default Value

False

Remarks

Indicates to the ACS that the Cardholder selected the additional choice.

UseInformationContinuation Property (Client Class)

Whether or not the Information Continue button is selected.

Syntax

public boolean isUseInformationContinuation();
public void setUseInformationContinuation(boolean useInformationContinuation);

Default Value

False

Remarks

Indicator notifying the ACS that the Cardholder selected the Information Continue button in the Information UI template.

WhitelistingDataEntry Property (Client Class)

Whitelisting Data Entry.

Syntax

public boolean isWhitelistingDataEntry();
public void setWhitelistingDataEntry(boolean whitelistingDataEntry);

Default Value

False

Remarks

An indicator provided by the SDK to the ACS to confirm whether whitelisting was opted by the cardholder (true or false). This is required to be sent after a challenge response is received containing WhitelistingInformationText.

WhitelistingInformationText Property (Client Class)

Whitelisting information text.

Syntax

public String getWhitelistingInformationText();

Default Value

""

Remarks

Text provided by the ACS/Issuer to Cardholder during a Whitelisting transaction. For example: "Would you like to add this Merchant to your whitelist?"

If present in the challenge response, this must be displayed by the SDK.

This property is read-only.

WhyInformationLabel Property (Client Class)

Label for why information section.

Syntax

public String getWhyInformationLabel();

Default Value

""

Remarks

Label provided by the Issuer for the UI "why" information section. Can be sent in CRes. App-based only.

This property is read-only.

WhyInformationText Property (Client Class)

Text to explain the authentication task to the user.

Syntax

public String getWhyInformationText();

Default Value

""

Remarks

Text provided by the Issuer for UI to explain the authentication task to the user in the "why" information section. Can be sent in CRes. App-based only.

This property is read-only.

AddDeviceParam Method (Client Class)

Adds a device parameter to the collection.

Syntax

public void addDeviceParam(String field, String value, int valueType, int category);

Remarks

AddDeviceParam adds a new device parameter to the DeviceParams collection. These parameters should be obtained from the consumer device and a full list of available parameters can be found in the EMV® 3-D Secure SDK-Device Information document provided by EMVCo.

The ValueType parameter specifies the type of the value. Possible values are:

• 1 (Array)
• 2 (String)

Most parameters will have a value type of 2 (String), which will contain a single, string value. Some parameters, however, may require an array of strings. For example, the A040 parameter is defined as containing a set of paired Bluetooth devices. All of these devices can be specified via an array like so: client.addDeviceParam("A040", "[\"firstDevice\", \"secondDevice\", \"thirdDevice\"]", 1, 1);

There are four categories of device information parameters:

DV - Data Version

This is the version of the data being specified. This is 1.0 by default, but can be set to a different value as shown below. When setting the data version, only the value of the parameter needs to be specified. client1.AddDeviceParam("", "1.1", 2, 0);

DD - Device Data

This category is used to specify the device parameters collected from the mobile platform. // the device platform is Android client1.AddDeviceParam("C001", "Android", 2, 1); // the device model is an HTC One (M8) client1.AddDeviceParam("C002", "HTCOne_M8", 2, 1);

DPNA - Device Parameter Not Available

This category is used to specify reasons for unavailable device parameters. // IP Address couldn't be specified because of a "market or regional restriction on the parameter." client1.AddDeviceParam("C010", "RE01", 2, 2);

SW - Security Warning

This category of parameter is used to specify security warnings. These are used to let the directory server know of the result of checks made by the application upon initialization. When setting security warning parameters, only the name of the parameter needs to be specified. // the device is jailbroken client1.AddDeviceParam("SW01", "", 2, 3); // A debugger is attached to the app client1.AddDeviceParam("SW04", "", 2, 3);

AddExtension Method (Client Class)

Adds an extension to the collection.

Syntax

public void addExtension(String id, String name, boolean critical, String data);

Remarks

Data necessary to support requirements not otherwise defined in the 3-D Secure message are carried in Message Extensions. AddExtension adds a new extension to the Extensions collection.

Note: The maximum number of extensions is 10.

AddRequestField Method (Client Class)

Adds a field to the data in the request.

Syntax

public void addRequestField(String name, String value, int valueType);

Remarks

This method can be used to extend the requests constructed by the class. When this method is called, the component will add the specified field to the end of the request.

CheckAuthResponse Method (Client Class)

Checks the received packet.

Syntax

public void checkAuthResponse(String authResponse);

Remarks

After the response to the authentication request is received from the 3DS Server class, call CheckAuthResponse to verify and parse the response. See the 3DS Server's SendAuthRequest method for details about obtaining the response.

Before calling this method, ACSRootCerts must be populated with the root certificates used by the ACS to sign the response. This method will validate the signature of the signed content if present.

After calling this method, inspect TransactionStatus to determine if the transaction requires a challenge. If TransactionStatus is C, a challenge is required and SendChallengeRequest should be called to proceed with the challenge flow. If TransactionStatus is D, decoupled authentication will take place outside of the 3-D Secure flow and the results will be posted to the 3DS Server.

If TransactionStatus is Y or A, the transaction is complete.

Config Method (Client Class)

Sets or retrieves a configuration setting.

Syntax

public String config(String configurationString);

Remarks

Config is a generic method available in every class. It is used to set and retrieve configuration settings for the class.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

GetAuthRequest Method (Client Class)

Prepares data to be sent by the 3DS Server.

Syntax

public String getAuthRequest();

Remarks

GetAuthRequest encrypts the device info and prepares all the data necessary to be sent by the 3DS Server class in the SendAuthRequest method.

After calling this method, the returned data must be transmitted via a separate secure channel to the server where 3DS Server is being used.

The following properties are required before calling the method:

Calling this method returns required information used by 3DS Server to send the authentication request. Transmit the value returned by this method to the system where 3DS Server is used. The method used to transmit this value is outside the scope of the class.

See SendAuthRequest for details on sending the authentication request after transmitting the data to the 3DS Server.

Calling this method also populates SDKTransactionId which uniquely identifies this transaction and must be used in subsequent calls relating to this transaction, such as SendChallengeRequest.

Interrupt Method (Client Class)

Interrupts the current action.

Syntax

public void interrupt();

Remarks

This method interrupts any processing that the class is currently executing.

Reset Method (Client Class)

Clears all properties to their default values.

Syntax

public void reset();

Remarks

This method clears all properties to their default values.

ResetTransactionInfo Method (Client Class)

Resets transaction specific information.

Syntax

public void resetTransactionInfo();

Remarks

This method must be called between transactions when using the same class instance.

Each transaction that is attempted uses transaction specific values that should not be re-used in subsequent transactions. Call this method to make sure that any transaction specific information is cleared between transactions.

This method resets only the transaction specific information without resetting any other values which have been configured. This allows re-use of the same component instance.

In an App-Based flow the following are reset:

• Internal ephemeral encryption keys
• Values added by AddRequestField
• ACSHTML
• ACSHTMLRefresh
• ACSUIType
• ChallengeAdditionalInformation
• ChallengeComplete
• ChallengeDataEntry
• ChallengeInfoHeader
• ChallengeInfoLabel
• ChallengeInfoText
• EnableChallengeInfoTextIndicator
• ChallengeSelectInfo
• DataPacketOut
• DeviceParams
• ErrorPacket
• ExpandableInformationLabel
• ExpandableInformationText
• IssuerImage1
• IssuerImage2
• IssuerImage3
• OOBContinuationIndicator
• OOBContinueLabel
• PaymentSystemImage1
• PaymentSystemImage2
• PaymentSystemImage3
• ResendInformationLabel
• SDKTransactionId
• SubmitAuthenticationLabel
• TransactionStatus
• WhyInformationLabel
• WhyInformationText
• WhitelistingDataEntry
• WhitelistingInformationText
• ACSSignedContent
• ACSTransactionId
• ACSURL
• ChallengeCancellationIndicator
• DSTransactionId
• DecoupledRequestIndicator
• IncomingRawExtensions
• OutgoingRawExtensions
• Extensions
• IncomingExtensionCount
• IncomingExtensionId
• IncomingExtensionName
• IncomingExtensionCritical
• IncomingExtensionData
• OOBAppLabel
• OOBAppURL
• ResendChallengeInfo
• TransactionStatusReason
• MerchantAppURL

SendChallengeRequest Method (Client Class)

Builds and sends the Challenge Request in an app-based challenge flow.

Syntax

public void sendChallengeRequest();

Remarks

SendChallengeRequest sends the Challenge Request to the ACS when a challenge is required.

When the TransactionStatus is C after calling CheckAuthResponse, a challenge to the cardholder is required. This method sends the challenge request and parses the response. The ACS may provide multiple challenges to the cardholder during this process. As a result this method may need to be called multiple times throughout the authentication process.

After this method is called, check ChallengeComplete to determine if the challenge process is complete. If it is complete (True), check TransactionStatus to determine the outcome. If ChallengeComplete is False, additional challenge interaction is required.

First Request

The first time this method is called, information about the required challenge is obtained from the ACS. The ACS connection information is automatically set when CheckAuthResponse is called; there is no need to specify any ACS connection information.

All required properties for the first call to this method are automatically set after CheckAuthResponse is called. If the transaction has been canceled, set ChallengeCancellationIndicator to inform the ACS.

After calling this method, the ACS will respond with details about the challenge to be presented to the cardholder. The ACSUIType property indicates the way the ACS will interact with the cardholder. The ChallengeComplete property will be False after the first call to this method since the challenge interaction is not yet complete.

The following properties are applicable when ACSUIType is Text (01), Single-Select (02), or Multi-Select (03):

• ChallengeSelectInfo
• ChallengeInfoHeader
• ChallengeInfoLabel
• ChallengeInfoText
• EnableChallengeInfoTextIndicator
• ExpandableInformationLabel
• ExpandableInformationText
• IssuerImage1
• IssuerImage2
• IssuerImage3
• PaymentSystemImage1
• PaymentSystemImage2
• PaymentSystemImage3
• ResendInformationLabel
• SubmitAuthenticationLabel
• WhyInformationLabel
• WhyInformationText

Use the values in the above properties to populate values in the native UI in the app. The UI must follow the guidelines defined in the EMV® 3-D Secure specification.

The following properties are applicable when ACSUIType is Out-of-Band (04):

• ChallengeAdditionalInformation
• ChallengeInfoHeader
• ChallengeInfoLabel
• ChallengeInfoText
• EnableChallengeInfoTextIndicator
• ExpandableInformationLabel
• ExpandableInformationText
• IssuerImage1
• IssuerImage2
• IssuerImage3
• OOBContinueLabel
• PaymentSystemImage1
• PaymentSystemImage2
• PaymentSystemImage3
• ResendInformationLabel
• WhyInformationLabel
• WhyInformationText

Use the values in the above properties to populate values in the native UI in the app. The UI must follow the guidelines defined in the EMV® 3-D Secure specification.

The following properties are applicable when ACSUIType is HTML (05):

• ACSHTML
• ACSHTMLRefresh

In the case of an HTML interaction, the app should create a webview and populate this with the HTML in ACSHTML.

As per the EMV® 3-D Secure specification, the HTML UI is presented to the cardholder via a web view which remains in control of the app. The app must intercept any remote URL requests made from within the web view, and instead handle them within the app. Preventing the cardholder from making requests in the web view to another server is critical to the security of the environment. According to the EMVCo specification, intercepting these requests has two effects:

• Prevents malicious HTML from redirecting a user to a phishing site.
• Conceptually puts the web view form under the control of the ACS, rather than the app.

• Navigation attempts from within the web view must be captured by the app and handled internally. This includes all requests including images, javascript files, css, etc.
• The web view element is not utilized as a browser, but as a UI element whose content is provided by the ACS.

Second Request

The second time this method is called, the purpose is to provide a response to the ACS. At this point the customer should have responded to the challenge provided by the ACS in the response to the first call. If the transaction has been canceled, set ChallengeCancellationIndicator to inform the ACS. The following properties are applicable when calling this method the second time:

• ChallengeDataEntry
• OOBContinuationIndicator

When ACSUIType is Text (01) or HTML (05), set ChallengeDataEntry to the data exactly as it was specified by the cardholder. Do not format or otherwise change the data.

When ACSUIType is Single-Select (02), set ChallengeDataEntry to the name of the selected option. For instance the ACS may provide the user with a selection like:

mobile: **** **** 329
email: s******k**@g***.com

When ACSUIType is Multi-Select (03), set ChallengeDataEntry to a comma-separated list of names of the selected options. For instance if ChallengeSelectInfo contains elements with names like chicago_illinois, st_louis_missouri, and portland_oregon, and the user chose two options, the value specified in ChallengeDataEntry would be chicago_illinois,portland_oregon.

When ACSUIType is OOB (04), set OOBContinuationIndicator to True to indicate the cardholder has pressed the button signaling their completing of the OOB process.

Completing the Challenge

After calling SendChallengeRequest a second time with the cardholder's responses, the ACS may require additional challenges. Check the ChallengeComplete property to determine if the challenge is complete. If False, more challenges are required by the ACS and the same process of displaying the challenge info, collecting the response, and submitting it to the ACS should be performed again.

If ChallengeComplete is True, the challenge interaction is complete and TransactionStatus can be inspected to determine whether the transaction was successful.

Note: As part of the challenge completion the ACS also notifies the 3DS Server of the results. This is done by posting the results to the URL defined by the ResultsURL property of the 3DS Server class.

DataPacketIn Event (Client Class)

Fired when receiving a data packet from the server.

Syntax

public class DefaultClientEventListener implements ClientEventListener {
  ...
  public void dataPacketIn(ClientDataPacketInEvent e) {}
  ...
}

public class ClientDataPacketInEvent {
  public byte[] dataPacket;
}

Remarks

This event fires when a packet is received. The entire data packet (including all framing and error detection characters) is contained in the DataPacket parameter. This parameter may be inspected for advanced troubleshooting, or to extract additional response properties beyond the scope of this component.

DataPacketOut Event (Client Class)

Fired when sending a data packet to the server.

Syntax

public class DefaultClientEventListener implements ClientEventListener {
  ...
  public void dataPacketOut(ClientDataPacketOutEvent e) {}
  ...
}

public class ClientDataPacketOutEvent {
  public byte[] dataPacket;
}

Remarks

This event fires right before each data packet is sent. The entire data packet (including all framing and error detection characters) is contained in the DataPacket parameter. This parameter may be inspected for advanced troubleshooting, or may be modified to support additional features beyond the scope of this component.

Error Event (Client Class)

Information about errors during data delivery.

Syntax

public class DefaultClientEventListener implements ClientEventListener {
  ...
  public void error(ClientErrorEvent e) {}
  ...
}

public class ClientErrorEvent {
  public int errorCode;
  public String description;
}

Remarks

The Error event is fired in case of exceptional conditions during message processing.

ErrorCode contains an error code and Description contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

Log Event (Client Class)

Fires once for each log message.

Syntax

public class DefaultClientEventListener implements ClientEventListener {
  ...
  public void log(ClientLogEvent e) {}
  ...
}

public class ClientLogEvent {
  public int logLevel;
  public String message;
  public String logType;
}

Remarks

Logging in the component is handled through the Log event. This will fire anytime a message is built or a response is parsed, including error messages.

When the Log event is fired, the message in question is made available via the Message event parameter. Properties such as EphemeralKey and DeviceParams are also available when they are gathered by the Client. The other event arguments are LogType and LogLevel:

The LogType parameter indicates the type of the log entry. Possible values are:

• "Info"
• "RequestHeaders"
• "ResponseHeaders"
• "RequestBody"
• "ResponseBody"
• "ProxyRequest"
• "ProxyResponse"
• "FirewallRequest"
• "FirewallResponse"
• "AReq"
• "ARes"
• "CReq"
• "CRes"
• "RReq"
• "RRes"
• "PReq"
• "PRes"
• "Erro"
• "EphemeralKey"
• "DeviceParams"

It is recommended to output all messages raised in this event to a file for record keeping purposes, or for later debugging issues that may have come up.

The Server and Client components also have DataPacketIn and DataPacketOut events that fire anytime a data packet is received or sent, respectively. The entire data packet is then accessible in the DataPacket event parameter. For encrypted packets, this would contain the full encrypted data. This parameter may be inspected for advanced troubleshooting.

SSLServerAuthentication Event (Client Class)

Fired after the server presents its certificate to the client.

Syntax

public class DefaultClientEventListener implements ClientEventListener {
  ...
  public void SSLServerAuthentication(ClientSSLServerAuthenticationEvent e) {}
  ...
}

public class ClientSSLServerAuthenticationEvent {
  public byte[] certEncoded;
  public String certSubject;
  public String certIssuer;
  public String status;
  public boolean accept; //read-write
}

Remarks

During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.

When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.

SSLStatus Event (Client Class)

Fired when secure connection progress messages are available.

Syntax

public class DefaultClientEventListener implements ClientEventListener {
  ...
  public void SSLStatus(ClientSSLStatusEvent e) {}
  ...
}

public class ClientSSLStatusEvent {
  public String message;
}

Remarks

The event is fired for informational and logging purposes only. This event tracks the progress of the connection.

Certificate Type

This is the digital certificate being used.

Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

Fields

Constructors

public Certificate();

public Certificate( certificateFile);

public Certificate( encoded);

public Certificate( storeType,  store,  storePassword,  subject);

public Certificate( storeType,  store,  storePassword,  subject,  configurationString);

public Certificate( storeType,  store,  storePassword,  encoded);

public Certificate( storeType,  store,  storePassword,  subject);

public Certificate( storeType,  store,  storePassword,  subject,  configurationString);

public Certificate( storeType,  store,  storePassword,  encoded);

ChallengeSelectInfo Type

Challenge Selection Information.

Remarks

Selection information that will be presented to the cardholder if the option is single or multi select. Name will contain the name of the field and Value will contain the corresponding value.

Fields

Constructors

public ChallengeSelectInfo();

ChallengeTextBox Type

Entry box settings.

Remarks

Defines the settings related to an entry box in the Native UI OTP/Text Template.

Fields

Constructors

public ChallengeTextBox();

DeviceParam Type

Device information parameter.

Remarks

Device information parameter used in the app flow to provide device information to the directory server.

Fields

Constructors

public DeviceParam();

public DeviceParam( fieldName,  value,  valueType,  category);

Extension Type

This type contains extension details.

Remarks

Data necessary to support requirements not otherwise defined in the 3-D Secure message are carried in Message Extensions. This type is used to define extensions to be sent in the next outgoing request.

Fields

Constructors

public Extension();

public Extension( id,  name,  critical,  data);

Proxy Type

The proxy the class will connect to.

Remarks

When connecting through a proxy, this type is used to specify different properties of the proxy, such as the Server and the AuthScheme.

Fields

Constructors

public Proxy();

public Proxy( server,  port);

public Proxy( server,  port,  user,  password);

Config Settings (Client Class)

Client Config Settings

<firstlevel>
  <one>value</one>
  <two>
    <item>first</item>
    <item>second</item>
  </two>
  <three>value three</three>
</firstlevel>

{
  "firstlevel": {
    "one": "value",
    "two": ["first", "second"],
    "three": "value three"
  }
}

SSL Config Settings

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
... Intermediate Cert ...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
... Root Cert ...
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
... Intermediate Cert ...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
... Root Cert ...
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
... Intermediate Cert...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
... Root Cert...
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

Trappable Errors (Client Class)

Client Errors

HTTP Errors

TCPClient Errors

SSL Errors

TCP/IP Errors