On This Page

Introduction to
Unified Checkout

Unified Checkout
 provides a single interface with which you can accept numerous types of digital payments.
Unified Checkout
 calls other follow-on services such as Payments,
Decision Manager
, and
Payer Authentication
.
Unified Checkout
 consists of a server-side component and a client-side JavaScript library.
The server-side component authenticates your merchant identity and instructs the system to act within your payment environment. The response contains limited-use public keys. The keys are for end-to-end encryption and contain merchant-specific payment information that drives the interaction of the application. The client-side JavaScript library dynamically and securely places digital payment options onto your e-commerce page.
The provided JavaScript library enables you to securely accept many payment options within your e-commerce environment.
Unified Checkout
 can be embedded seamlessly into your existing webpage, simplifying payment acceptance.
When a customer selects a payment method from the button widget,
Unified Checkout
 handles all of the interactions with the digital payment that was chosen.
Unified Checkout
 is also able to orchestrate requests for to follow-on services such as Payments,
Decision Manager
, and
Payer Authentication
 before it provides a response to your e-commerce system.
The figure below shows
Unified Checkout
 with customer checkout payment options.

Figure:

Button Widget
Example of the button widget interface and flow with various payment options.
For examples of different payment method UIs through
Unified Checkout
, see Unified Checkout UI.
IMPORTANT
Each request that you send to
National Australia Bank
 requires header information. For information about constructing the headers for your request, see the
Getting Started with REST Developer Guide
.