On This Page
pilot
Server-Side Set Up
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.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, payment interface styling, and payment methods.
The functions are compiled in a JSON Web Token (JWT)
object referred to as the
capture context
. For information JSON Web Tokens, see
JSON Web Tokens.Capture Context
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
{ // -------- REQUIRED VALUES ---------- "data": { "orderInformation": { "amountDetails": { "totalAmount": "123.94", "currency": "USD" } } }, "allowedCardNetworks": [ "VISA", "MASTERCARD", "AMEX" ], "billingType": "FULL", "country": "US", "locale": "en_US", "version":"0.6" }