Step 1: Setup Service {#pa2-ccdc-setup-intro}
=============================================

Request the Setup service before selecting the button to submit payment. Request the Setup service separately without including other services. The Setup service response will include a JSON Web Token (JWT) that contains credentials to create a secure channel with you. The Setup response also includes a reference ID to use during the authentication and a URL to use when transferring the device data that is collected in the next step.  
IMPORTANT The Setup service is used only in the Direct API integration. The SDK integration does not use this step.  
Run the Setup service as soon as the customer enters their card number to avoid any delay in the customer experience. The next step in the process, device data collection, cannot start until the Setup response is received because the response has the URL where the device data will be sent.

#### Figure: {#pa2-ccdc-setup-intro_fig_tdp_pzj_ldc}

Process Flow for Setup for Payer Authentication ![Process Flow Diagram for Setup for Payer Authentication](/content/dam/documentation/cybs/en-us/topics/risk/payer-authentication/payer-auth/images/pa-setup-3.svg/jcr:content/renditions/original)

Best Practices
--------------

This practice should be followed so that this step achieves optimal performance and to minimize potential operating issues.  
After the customer credit card is entered, immediately begin device data collection.

Endpoint
--------

**Production:** `POST ``https://api.cybersource.com``/risk/v1/authentication-setups`  
**Test:** `POST ``https://apitest.cybersource.com``/risk/v1/authentication-setups`

Request Fields {#pa-ccdc-setup-service-request-fields}
======================================================

When requesting the Setup service, you must send the customer's payment information. This can be either the actual encrypted card information or a token associated with the payment data.  
These fields are required:
* paymentInformation.card.expirationMonth

* paymentInformation.card.expirationYear

* paymentInformation.card.number

* paymentInformation.card.type
  {#pa-ccdc-setup-service-request-fields_ul_q2m_xjk_nhc}  
  Besides the required fields, the request might also include any of these fields:

* paymentInformation.tokenizedCard.number

* paymentInformation.customer.customerId

* tokenInformation.transientToken

{#pa-ccdc-setup-service-request-fields_ul_lhq_5ml_xpb}  
The paymentInformation.card.type field is required when the card type is JCB, Cartes Bancaires, or China UnionPay.

Important Response Fields {#concept_am2_mnl_xpb}
================================================

The response from the issuing bank might include these API fields.

* consumerAuthenticationInformation.accessToken is used in [Step 2: Device Data Collection](/content/cybsdeveloper2021/amer/en/docs/cybs/en-us/payer-authentication/developer/all/rest/payer-auth/pa2-ccdc-ddc-intro.md "").
* consumerAuthenticationInformation.deviceDataCollectionUrl is used in [Step 2: Device Data Collection](/content/cybsdeveloper2021/amer/en/docs/cybs/en-us/payer-authentication/developer/all/rest/payer-auth/pa2-ccdc-ddc-intro.md "").
* consumerAuthenticationInformation.referenceId is used in [Step 3: Payer Authentication Check Enrollment Service](/content/cybsdeveloper2021/amer/en/docs/cybs/en-us/payer-authentication/developer/all/rest/payer-auth/pa2-ccdc-enroll-intro.md "").

{#concept_am2_mnl_xpb_ul_nxn_lzw_vyb}  
For further details on examples, see [REST Example: Setting Up Data Collection](/content/cybsdeveloper2021/amer/en/docs/cybs/en-us/payer-authentication/developer/all/rest/payer-auth/pa2-use-cases-intro/pa2-set-up-use-intro/pa2-use-setup-rest-ex.md "")