On This Page
FILTER BY TAG

Introduction to
Unified Checkout

Unified Checkout
 provides a single interface with which you can accept numerous types of card, digital, and alternative payments.
Unified Checkout
 calls other follow-on services such as Payments,
Decision Manager
,
Payer Authentication
, and
Token Management Service
 (
TMS
).
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 interactions with the payment method that was chosen.
Unified Checkout
 is also able to orchestrate requests for to follow-on services such as Payments,
Decision Manager
,
Payer Authentication
, and
TMS
 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 these topics:.
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
.

Key Features

  • Low-code integration
    : You can use as few as three lines of JavaScript to accept payments, as well as add or remove payment methods through portal configuration without changing your integration code.
  • PCI SAQ-A compliant
    : Payment data never touches your systems.
  • Fully customizable
    : You can match the payment experience to your brand with theming, fonts, and layout options. Embed inline or display as a sidebar overlay.
  • Service orchestration
    : You can use
    Decision Manager
    ,
    Payer Authentication
     (
    3-D Secure
    ), and
    Token Management Service
     (
    TMS
    ) throughout the session.