> For the complete documentation index, see [llms.txt](https://wallee.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wallee.gitbook.io/documentation/payments/integrations.md).

# E-Commerce

This section covers everything you need to accept payments online: how the customer enters their payment details, how to add recurring billing, which payment features you can switch on, and how to connect an existing shop system.

### Before you start

Two things must be in place before your first online payment:

* A **payment contract** — either through wallee payments or with an external acquirer. See [Payment Contracts](/documentation/payments/integrations/payment-contracts.md).
* A configured **processor and connector** for each payment method you want to offer. See [Processors](/documentation/payments/overview/processors-payment-methods-and-connectors/processors.md) and [Connector Configuration](/documentation/payments/overview/processors-payment-methods-and-connectors/connectors.md).

### What is in this section

| Topic                                                                          | What you will find                                                                                                       |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| [Payment Contracts](/documentation/payments/integrations/payment-contracts.md) | How to obtain the contract you need to accept payments — through us or through an external acquirer.                     |
| [Checkout Integrations](/documentation/payments/integrations/integrations.md)  | The integration modes: payment page, iFrame, lightbox and the other ways the customer can enter their payment details.   |
| [Subscriptions](/documentation/payments/integrations/subscriptions.md)         | Recurring billing: products, subscribers, billing cycles, coupons and the subscription lifecycle.                        |
| [Features](/documentation/payments/integrations/features.md)                   | Payment features you can switch on, such as 3-D Secure, tokenization, wallets, payment links, fraud prevention and MOTO. |
| [Plugins](/documentation/payments/integrations/plugins.md)                     | Ready-made connections for shop and hospitality systems, so you can accept payments without building an integration.     |

### Choosing your approach

{% tabs %}
{% tab title="I use a shop system" %}
If your shop runs on a platform we support — such as Shopware, WooCommerce, Magento, OpenCart or Shopify — install the [plugin](/documentation/payments/integrations/plugins.md) instead of building an integration. The plugin handles the checkout, the transaction states and the order updates for you.
{% endtab %}

{% tab title="I build my own checkout" %}
Create the transaction via the [Web Service API](/documentation/developer-tools/api-reference/web-service-api.md) — using one of our [SDKs](/documentation/developer-tools/sdks.md) if you prefer — and choose a [checkout integration](/documentation/payments/integrations/integrations.md) for the payment step. Track the result with [webhooks](/documentation/developer-tools/webhooks.md) and the [transaction states](/documentation/payments/overview/transaction-states.md).
{% endtab %}

{% tab title="I have no shop at all" %}
You do not need a website to get paid online: [Payment Links](/documentation/payments/integrations/features/payment-links.md) let you collect payments through a URL or QR code, and [MOTO Payments](/documentation/payments/integrations/features/moto-payments.md) cover orders you take by phone or mail.
{% endtab %}
{% endtabs %}

{% hint style="info" %}
Whichever route you take, the payment itself always ends up as a transaction that moves through the same [transaction states](/documentation/payments/overview/transaction-states.md) — that is what your order handling should react to.
{% endhint %}

### Accepting payments in person as well?

Online and in-store payments run in the same space, so all transactions appear in one list and one settlement. See [In-store Payments](/documentation/payments/in-store-payments.md) for terminals, till integrations and unattended machines.