Frequently Asked Questions about

Unified Checkout

Frequently Asked Questions

How do I enable

Unified Checkout

?

Unified Checkout

is enabled by your partner or through Client Support.

How do I enable the payment methods required for

Unified Checkout

?

Digital Payment options must be enrolled onto and configured by the merchant conducting the integration. Details on how to enable digital payment can be found in the

Unified Checkout

Configuration.

How do I add

Unified Checkout

to my mobile applications?

Unified Checkout

is primarily built for web pages. However, it can be integrated into mobile applications through use of a WebView. Additionally, the

Cybersource

Acceptance platform has a number of additional products such as

Flex API

that can be used to power acceptance in mobile apps. For more information, visit https://github.com/cybersource

What card types are supported on

Unified Checkout

?

Support is dependent on your processing capability. See the current list at

Unified Checkout

Card Types.

What payment methods are supported on

Unified Checkout

?

See the current list of supported payment methods at

Unified Checkout

Payment Methods .

Can I customize the look and feel of

Unified Checkout

to fit in with my web page branding?

Yes, this can be managed through both

Unified Checkout

configuration within the

Business Center

and using the

sessions

API request. For information about configuring the look and feel in the

Business Center

, see the

Customize the

Unified Checkout

Look and Feel

section of the

Unified Checkout

Developer Guide.

How does authentication work in

Unified Checkout

?

Unified Checkout

uses

Cybersource

REST HTTP signature authentication. Requests to the

sessions

API and other REST APIs are signed using merchant REST credentials.

I am using

Secure Acceptance

Checkout API

/ Silent Order Post. Can I keep my existing forms?

Unified Checkout

is designed by be highly customizable but does not provide a fully headless solution. For

Checkout API

migration, you can continue collecting most fields in your form but payment details such as the PAN, CVV, and expiration date are captured by

Unified Checkout

. Capture of the billing and shipping information is determined by capture context configuration. In addition, there are multiple ways to integrate

Unified Checkout

using the SDK. It is your choice to render or not render a payment button for card payments in

Unified Checkout

.

Do I need webhooks?

Cybersource

strongly recommends that you use webhooks for production integrations to retrieve final transaction status information.

Unified Checkout

provides a response to your browser to enable you to understand the result of the transaction, but webhooks provides all of the information that is returned from the payments request.