This section contains the information you need to
set up your server. Initializing
Unified Checkout
within your webpage
begins with a server-to-server call to the sessions API. This step authenticates your
merchant credentials, and establishes how the
Unified Checkout
frontend
components will function. The sessions API request contains parameters that define how
Unified Checkout
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 interaction methods.
The functions are compiled in a JSON Web Token (JWT) object referred to as the
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, the target origin to the
Unified Checkout
integration in addition to allowed card networks and
payment types (card or check). The capture context request includes these elements:
You can define the payment cards and digital payments that you want
to accept in the capture context.
Allowed Card Networks
Use the
allowedCardNetworks
field to define the
card types.
These card networks are available for card entry:
American Express
Cartes Bancaires
Carnet
China UnionPay
Diners Club
Discover
EFTPOS
ELO
JCB
JCrew
Mada
Maestro
Mastercard
Meeza
Visa
To support dual-branded or co-badged cards, you must list your
supported card types values for the
allowedCardNetworks
field based on your
preference for processing card numbers. For example, if a card is
dual-branded as Visa and Cartes Bancaires and Cartes Bancaires is
listed first, the card type is set to Cartes Bancaires after the
card number is entered in your