The integration flow consists of two events that must occur in order.
  1. You send a server-to-server request for a capture context. This request is fully authenticated for the JSON Web Token (JWT) and is necessary in order to invoke the front-end JavaScript library.
  2. You invoke the
    Unified Checkout
     JavaScript library using the JWT response from the capture context request.
The figure below illustrates the
Unified Checkout
 payment flow.

Figure:

Unified Checkout Payment Flow
Diagram that shows the sequence and flow of a Unified Checkout payment.

Server-Side Setup

The server-side component provides this information:
  • A transaction-specific public key. This key is used by the customer's browser to protect the
    Unified Checkout
     transaction.
  • An authenticated context description package that manages the payment experience on the client. It includes payment options available, payment interface styling, and interaction methods.
The functions are compiled in a JSON Web Token (JWT) object referred to as the
capture context
.