`Unified Checkout` Payment Page Options {#sa-uc-pymnt-page-options}
===================================================================

Implementation Options
----------------------

`Unified Checkout` is designed to be placed within your existing payment experience to offer a seamless payment journey without having to redirect your clients to external web pages.  
These are the options depending on your current `Secure Acceptance` integration:

Merchants leveraging `Secure Acceptance` through page redirects
---------------------------------------------------------------

Merchants leveraging `Secure Acceptance` through page redirects have two options:

1. Embed `Unified Checkout` on one of your existing pages
2. Create a new payments page to integrate `Unified Checkout`

Merchants leveraging `Secure Acceptance` through iframe implementation
----------------------------------------------------------------------

You should be able to replace your existing `Secure Acceptance` implementation with `Unified Checkout` with minimal changes to your page.

`Checkout API` migration
------------------------

`Unified Checkout` has been created to be highly configurable and can be tailored to have a very small form factor. If you are using Secure Acceptance `Checkout API`, you can continue to capture all the payment information from within your own form except for the Payment information (PAN, CVV, Expiration Date \& Cardholder Name). You should replace these elements with `Unified Checkout`. When loading `Unified Checkout`, you can set `BillingType=NONE` and `requestShipping=false`, but you must include the address information in the capture context to ensure that the payment is processed successfully.

#### Figure:

Manual Entry Payment Details ![](/content/dam/new-documentation/documentation/en-us/topics/payments-processing/card-processing/unified-checkout/images/uc-ui-manual-1.png/jcr:content/renditions/original)