FILTER BY TAG

Integration Methods

Unified Checkout
offers flexible integration methods for your page's checkout experience. This section contains information about each integration method and the JavaScript that is required for each one.
This table outlines the different integration methods offered by
Unified Checkout
:
Unified Checkout
Integration Methods
Checkout
Trigger
Components
What does it do?
Checkout renders all payment buttons in a checkout list. The list order is determined by the order they are passed in the Sessions API.
The trigger method launches into the payment screen without the need to have a separate
Unified Checkout
hosted payment button.
The components method enables the client to compartmentalize and embed the checkout UI without the need for a separate
Unified Checkout
hosted payment button.
What is it best for?
Clients that want to show all payment methods in a list within their checkout page.
Merchants that want to host their own payment button to launch into the
Click to Pay
/ Card Entry flow in a sidebar view.
Merchants that want to fully embed the payment form into their payment page without the
Unified Checkout
header.
Who owns the payment button(s)?
Unified Checkout
Merchant
Merchant
Display modes
Sidebar or embedded
Sidebar
Embedded
Supported payment methods
All configured methods
Card payment and
Click to Pay
Card payment,
Click to Pay
, and eCheck/ACH service
Example uses
A merchant that requires a button list of all accepted payment methods in
Unified Checkout
.
A merchant that has an existing pay by card/
Click to Pay
button that they want to launch into the payment UI using a sidebar view.
A merchant that wants to embed
Unified Checkout
payment components directly into their page without the standard header. This integration method is ideal for a user that offers a radio button/drop-down UI.
Summary
Full out-of-the-box checkout
Use own payment button to launch UC within a sidebar
Full embed payment UI without Unified Checkout Payment button
Documentation