3DS - AuthenticateBrowser

post https://api.staging.pungle.co/api/v1/transactions/pull/3D-Secure-2/authenticate/browser

Authentication endpoint to initiate 3D Secure transaction.

For information on the flow and steps needed to call this endpoint please see the https://developers.berkeleypayment.com/reference/3dsecure page.

Authentication Request

Parameters

authentication_ind string

Indicates the type of Authentication request. This data element provides additional information to the ACS to determine the best approach for handing an authentication request.

01 = Payment transaction

amount * number

Transaction total

financial_account * string

Financial account Token.

currency * string

ISO 4217 three-digit currency code

shipping object

Shipping details (optional)

{
	"line1": "string",
	"line2": "string",
	"line3": "string",
	"postCode": "string",
	"city": "string",
	"state": "string",
	"country": "string"
}

billing object

{

	"line1": "string",
	"line2": "string",
	"line3": "string",
	"postCode": "string",
	"city":	"string",
	"state": "string",
	"country": "string"
}

email string

Email of payee (optional)

three_ri_indicator string

Indicates the type of 3RI request. This is required for all 3RI requests

01 = Recurring transaction
02 = Installment transaction
03 = Add card
04 = Maintain card information
05 = Account verification

trans_type string

Values accepted:

01 = Goods/ Service Purchase
03 = Check Acceptance
10 = Account Funding
11 = Quasi-Cash Transaction
28 = Prepaid Activation and Load

message_category string

The message Category - requesting Payment Authentication (PA) or Non Payment Authentication (NPA)

01 = PA
02 = NPA

browser * object

{
    "browser_ip": "string",
    "browser_accept_header": "string",
    "browser_java_enabled": "boolean", // Boolean that represents the ability of the cardholder browser to execute Java
    "browser_javascript_enabled": "boolean", // Boolean that represents the ability of the cardholder browser to execute JavaScript
    "browser_language": "string", // Value representing the browser language as defined in IETF BCP47
    "browser_color_depth": "string",
        Value representing the bit depth of the colour palette for displaying images, in bits per pixel.
	    - 1 = 1 bit
	    - 4 = 4 bits
	    - 8 = 8 bits
	    - 15=15bits
	    - 16=16bits
	    - 24=24bits
	    - 32=32bits
	    - 48=48bits

    "browser_screen_width": "string", // Total height of the Cardholder's screen in pixels.
    "browser_screen_height": "string", // Total width of the cardholder's screen in pixels.
    "browser_tz": "string", // Time difference between UTC time and the Cardholder browser local time, in minutes.
    "browser_user_agent": "string", // Browser and OS details of the cardholder
}

challenge_indicator * string
Indicates whether a challenge is requested for this transaction.

Options:

01 - No preference
02 - No challenge requested
03 - Challenge requested (3DS Requestor preference)
04 - Challenge requested (Mandate)

challenge_window_size * string

Window Sizes:

01 - 250x400
02 - 390x400
03 - 500x600
04 - 600x400
05 - Fullscreen

merchant_risk_indicator object

{	
    "ship_indicator": "string`", //Required for AMEX transactions. Indicates shipping method chosen for the transaction

    01 = Ship to cardholder's billing address
    02 = Ship to another verified address on file with merchant
    03 = Ship to address that is different than the cardholder's billing address
    04 = “Ship to Store” / Pick-up at local store (Store address shall be populated in shipping address fields)
    05 = Digital goods (includes online services, electronic gift cards and redemption codes)
    06 = Travel and Event tickets, not shipped
    07 = Other (for example, Gaming, digital services not shipped, emedia subscriptions, etc.)

    "delivery_time_frame":"string", //Indicates the merchandise delivery timeframe. Required for AMEX Values accepted

    01 = Electronic Delivery
    02 = Same day shipping
    03 = Overnight shipping
    04 = Two-day or more shipping enum:

    "reorder_items_ind":"string", // Indicates whether the cardholder is reordering previously purchased merchandise. Values accepted

    01 = First time ordered
    02 = Reordered
}

acct_info object

{
    "ch_acc_age_ind": "string",
	Length of time that the cardholder has had the account with the 3DS Requestor. Values accepted

    01 = No account (guest check-out)
    02 = Created during this transaction
    03 = Less than 30 days
    04 = 30-60 days
    05 = More than 60 days

    "ch_acc_date":"string", // Date that the cardholder opened the account with the 3DS Requestor. YYYYMMDD

    "ch_acc_change_ind": "string",
	Length of time since the cardholder's account information with the 3DS Requestor was last changed, including Billing or Shipping address, new payment account, or new user(s) added. Values accepted

    01 = Changed during this transaction
    02 = Less than 30 days
    03 = 30-60 days
    04 = More than 60 days

    "ch_acc_change":"string",
	Date that the cardholder's account with the 3DS Requestor was last changed, including Billing or Shipping addres,new payment account, or new user(s) added. YYYYMMDD

    "ch_acc_pw_change_ind":	"string",
	Indicates the length of time since the cardholder's account with the 3DS Requestor had a password change or account reset. Values accepted

    01 = No change
    02 = Changed during this transaction
    03 = Less than 30 days
    04 = 30-60 days
    05 = More than 60 days

    "ch_acc_pw_change":	"string", // Date that cardholder's account with the 3DS Requestor had a password change or account reset. YYYYMMDD

    "ship_address_usage_ind": "string",
	Indicates when the shipping address used for this transaction was first used with the 3DS Requestor. Values accepted

    01 = This transaction
    02 = Less than 30 days
    03 = 30-60 days
    04 = More than 60 days

    "ship_address_usage": "string", // Date when the shipping address used for this transaction was first used with the 3DS Requestor.

    "txn_activity_day": "string", // Number of transactions (successful and abandoned) for this cardholder account with the 3DS Requestor across all payment accounts in the previous 24 hours.

    "txn_activity_year": "string", // Number of transactions (successful and abandoned) for this cardholder account with the 3DS Requestor across all payment accounts in the previous year.

    "provision_attempts_day":"string", //Number of Add Card attempts in the last 24 hours.

    "nb_purchase_account": "string", // Number of purchases with this cardholder account during the previous six months

    "suspicious_acc_activity": "string",
	Indicates whether the 3DS Requestor has experienced suspicious activity (including previous fraud) on the cardholder account. Values accepted

    01 = No suspicious activity has been observed
    02 = Suspicious activity has been observed


    "ship_name_indicator": "string", //Indicates if the Cardholder Name on the account is identical to the shipping Name used for this transaction.

    "payment_acc_ind":	"string`". //Indicates the length of time that the payment account was enrolled in the cardholder's account with the 3DS Requestor.

    "payment_acc_age": "string", // Date that the payment account was enrolled in the cardholder's account with the 3DS Requestor.
}

Response

`string`

authenticate_initiated - Authentication process has started

tds_vs_unsupported - Issuer does not currently support 3DSecure V2

authenticate_browser_failed - Failed to start authentication status

chargeback_protection_available `boolean`

Value indicating if chargeback protection is available at this point in 3DSecure V2 Authentication Process

protocol_version `string`

The protocol version used for the authentication request

method_url `string`

This is the url used to gather device information

correlation_id `string`

This is used to link recurring transactions

three_ds_method_data `string`

Base64 encoded json with the noficationUrl, transactionId to send to the ACS for device fingerprinting. This should be setup in a 1x1 iframe

Errors

400 Aborted

Please ensure that request is valid json and the content type is set to 'application/json'.

Issuer's Not Supporting EMV 3DS (v2.1)

If you are using 3DSecure v2.1 in an area where it had been mandated and you receive a response with a status of tds_v2_unsupported. You can stop at this step in the process and send in the ID returned in the response in the payload of a Pull transaction as the three_d_secure_id. This will attach the 3DSecure Authentication attempt to the transaction.