# Checkout configuration

**Configure Checkout applications, payment integrations, and user agreements in the Merchant Center.**

Checkout configuration in the Merchant Center sets up the Checkout experience for your customers. Configure Checkout applications, define payment methods, and manage user agreements and compliance requirements.

## Enable Checkout

The first time you access Checkout, you must enable it for your Project:

1. Select **Checkout** from the main menu.
2. Click **Get started**.
3. Review the permissions and message subscriptions required for Checkout:
   - API scopes for managing orders, payments, subscriptions, and sessions
   - Message subscriptions for payment transaction tracking
4. Click **Confirm creation**.

The system automatically creates two sample applications:

- **Checkout DE**: Complete checkout
- **Checkout EN**: Payment only

## Manage Checkout applications

After enabling Checkout, you can view and configure Checkout applications.

### View applications

1. Select **Checkout** from the main menu.
2. The **List of applications** tab displays all configured Checkout applications with:
   - Application Name
   - Application Key
   - Application type (Complete checkout or Payment only)
   - Active
   - Countries
   - Date created and Date modified

To review the permissions and message subscriptions used by Checkout, click the **Permissions and subscription** tab.

### Create a Checkout application

To add a new Checkout application:

1. On the Checkout overview page, click **Add application**.
2. Select the application type: click **Add complete checkout** or **Add payment only**.
3. Enter the application details in the General tab.
4. Click **Create** to save the application.

### Configure application settings

Each checkout application has three configuration tabs:

#### General tab

Configure basic application properties and checkout behavior:

- **Application name** (required): display name for the application
- **Application key** (required, read-only once created): unique identifier set when creating the application
- **Application description** (optional): multi-language description for internal reference
- **Logo URL** (required): URL to the logo displayed on the checkout page
- **Select countries** (required): countries where this application is available (must be pre-configured in your Project)
- **Origin URLs** (required): define which domains can access this application:
  - Select **Allow all** to permit any origin
  - Select **Specify URLs** to restrict to specific domains (for example, your storefront domain)
- **Payment return URL** (optional): URL where customers return after payment processing
- **Discount code function** (optional toggle): activate or deactivate discount code entry on the checkout page

#### User Agreement tab

Configure legal agreements and compliance documents:

1. Click **Add user agreement** to create a new agreement.
2. Enter:
   - **Agreement identifier**: unique name for the agreement (for example, "terms\_of\_service")
   - **Agreement status**: toggle to activate or deactivate the agreement
   - **Agreement content**: multi-language text for the agreement (terms, privacy policy, etc.)
3. Save your changes.

Users must accept all active agreements before completing the checkout.

#### Payment integrations tab

Add payment connectors for payment processing:

1. If no payment connector is available, the button is deactivated. First, install a payment Connector from the Connect marketplace.
2. Once Connectors are available, click **Add payment integration**.
3. Select the payment Connector for your payment service provider.
4. Configure Connector-specific settings.
5. Save your changes.

Payment Connectors must be installed and configured separately before they appear here.

## Activate or deactivate applications

Open the application and use the **Status** toggle at the top of the page to activate or deactivate it. Deactivated applications are not available to customers.

## Checkout modes

The Merchant Center supports two checkout modes for different integration scenarios:

- **Complete checkout**: full checkout experience including cart review, shipping method selection, and payment. Suitable for standalone checkout implementations.
- **Payment only**: payment page only, for Projects that handle checkout flow in their own storefront and need only payment processing.

## Checkout types and flows

### Complete checkout flow

Customers experience:

1. Cart review with product quantities and totals
2. Shipping address entry
3. Shipping method selection (if available)
4. Billing address (can match shipping)
5. Discount code entry (if enabled)
6. Payment method selection
7. Order confirmation

### Payment-only flow

For projects with existing checkout systems, Payment Only checkout provides:

1. Payment method selection
2. Payment processing
3. Return to merchant site with payment status

## Permissions and subscriptions

Checkout requires the following permissions to function:

- Order management (create, read, update orders)
- Payment management (manage payments and payment methods)
- Subscription management
- Session management
- Product and customer data access
- Payment transaction event subscriptions

These permissions are automatically configured when you enable Checkout.

## Multi-country support

Checkout applications support multiple countries. When creating or configuring an application:

1. In the **Select countries** field, choose all countries where the application is available.
2. Currency and tax settings are configured per country in Project settings.
3. Checkout automatically applies correct tax rates and currency formatting per country.

Countries must be pre-configured in your Project settings before assigning them to checkout applications.

## Test your Checkout

After configuration:

1. Note the **Application key** for your checkout application.
2. Use this key to integrate checkout into your storefront.
3. Test with the provided sample applications (Checkout DE, Checkout EN).
4. Create your own applications with your domain configuration before going live.

For more information about integrating Checkout, see the [Checkout documentation](/checkout/connectors-and-applications.md).

## Related pages

- [Area overview page with navigation](/merchant-center.md)
- [Previous page: Tax management](/merchant-center/taxes.md)
- [Search documentation and API specs](/search.md)