pilot

Server-Side Set Up {#uctp-ss-setup}
===================================

This section contains the information you need to set up your server. Initializing `Unified Click to Pay` within your webpage begins with a server-to-server call to the sessions API. This step authenticates your merchant credentials, and establishes how `Unified Click to Pay` manages your capture context configuration. This includes supported locales, currencies, and country availability. The sessions API request contains parameters that define how `Unified Click to Pay` performs.  
For information about sessions API requests, see [Generate Unified Click to Pay Capture Context](https://developer.cybersource.com/api-reference-assets/index.md#unified-checkout_unified-click-to-pay-capture-context_generate-unified-click-to-pay-capture-context "") in the `Cybersource` API Reference.  
The server-side component provides this information:

* A transaction-specific public key is used by the customer's browser to protect the transaction.
* An authenticated context description package that manages the payment experience on the client side. It includes available payment options such as card networks, and payment methods.

{#uctp-ss-setup_ul_atq_bwq_npb}  
The functions are compiled in a JSON Web Token (JWT) object referred to as the *capture context* . The header of each JWT header contains a key ID field (`kid`) that references the specific RSA public key that `Cybersource` used to sign that token. The integrator must retrieve this public key from `Cybersource` and use it to verify the JWT's signature. If the signature is invalid, the JWT must be rejected. For information about JWTs, JWT validation keys, and API authentication keys, see these topics:

* [JSON Web Tokens](/docs/cybs/en-us/unified-click-to-pay/developer/all/rest/unified-click-to-pay/uctp-appendix-intro/uc-appendix-jwts.md "")
* [JWT Validation Keys](/docs/cybs/en-us/unified-click-to-pay/developer/all/rest/unified-click-to-pay/uctp-appendix-intro/uctp-keys/uctp-keys-jwt-keys.md "")
* [API Authentication Keys](/docs/cybs/en-us/unified-click-to-pay/developer/all/rest/unified-click-to-pay/uctp-appendix-intro/uctp-keys/uctp-keys-api-keys.md "")
  {#uctp-ss-setup_ul_nrx_r2t_w3c}

Capture Context {#uctp-capture-context-intro}
=============================================

The capture context request is a signed JSON Web Token (JWT) that includes all of the merchant-specific parameters. This request tells the frontend JavaScript library how to behave within your payment experience. The request provides authentication, one-time keys, in addition to allowed card networks and payment types. The capture context, at a minimum, requires these elements:

* allowedCardNetworks
* amountDetails
* billingType
* country
* currency
* data.orderInformation.amountDetails.totalAmount
* data.orderInformation.amountDetails.currency
* locale
* totalAmount
* version

Capture Context Example {#uctp-capture-context-intro_example}
-------------------------------------------------------------

```
{
    // -------- REQUIRED VALUES ----------
    "data": {
        "orderInformation": {
            "amountDetails": { 
                "totalAmount": "123.94", 
                "currency": "USD" 
            }
        }
    }, 
    "allowedCardNetworks": [ 
        "VISA",
        "MASTERCARD",
        "AMEX"
    ],
    "billingType": "FULL",
    "country": "US",
    "locale": "en_US",
    "version":"0.6" 
}
```