> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eat-now.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect online payments

> Link the merchant account before configuring deposits, prepayments or activities.

Under **Settings → Integrations → General → Payments**, use the provider
arranged for your restaurant: **Stripe**, **Payzone** or **CMI**.

## Connect

* **Stripe**: click **Connect** and complete the Stripe account flow in the
  offered window. Check that the merchant account belongs to the correct
  location.
* **Payzone**: enter Merchant ID, Merchant Key, Merchant API Key and
  Notification Key.
* **CMI**: enter Merchant ID, Merchant Key, Merchant API Key, Merchant API
  Secret and Notification Key.

Use the credentials supplied for your merchant integration. Ask your EatNow
contact to prepare the connection if you are unsure which to use. Do not include
these secrets in support screenshots.

## Configure what customers pay

The connection is a prerequisite, not a charging rule. Then configure the shift
or activity:

* [deposit or card imprint](/shifts/payments-deposits);
* [prepayment](/shifts/payments-prepayment);
* [extras](/shifts/payments-extras);
* [activity payment](/activities/add).

Set amounts, mandatory payment, deadlines and refund conditions in the relevant
workflow. Available modes depend on the provider; a “connected” card alone does
not mean card holds are supported.

## Check and troubleshoot

With EatNow, verify the full workflow for your setup: payment request display,
opening the payment page and receiving the payment status. A saved connection
does not prove that a real payment succeeded.

For a failure, provide the restaurant, reservation and displayed error, without
card details or merchant keys. If changing provider, have outstanding payments
and card holds reviewed before disconnecting.