> 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/integrations.md).

# Checkout Integrations

Use our different checkout integration options and accept seamless payments online.

The integration mode decides where and how your customer enters their payment details. All modes end up creating the same transaction, so your order handling stays the same — see [Transaction States](/documentation/payments/overview/transaction-states.md).

The **machine name** in the table below is the value you pass to the API when you fetch the available payment methods for a transaction.

| Name                                                                                       | Description                                                                                                                                                                                             | Machine name             |
| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| [Payment Page](/documentation/payments/integrations/integrations/wallee-payment-page.md)   | The user enters the payment details on a page hosted by us in a secure environment.                                                                                                                     | `payment_page`           |
| [iFrame](/documentation/payments/integrations/integrations/iframe-integration.md)          | The user enters the payment details in an iFrame hosted by us. The iFrame can be integrated into the merchant's website.                                                                                | `iframe`                 |
| [Lightbox](/documentation/payments/integrations/integrations/lightbox.md)                  | The user enters the payment details in an overlay. The form for the payment details overlays the merchant's website.                                                                                    | `lightbox`               |
| [Mobile Web View](https://{inject-platform-url}/doc/payment/mobile-sdk-web-service-api)    | The user enters the payment details in a web view on a mobile device.                                                                                                                                   | `mobile_web_view`        |
| [Terminal](/documentation/payments/in-store-payments.md)                                   | A physical terminal processes the transaction. The user taps or inserts the card into the terminal.                                                                                                     | `terminal`               |
| [Payment Link](/documentation/payments/integrations/features/payment-links.md)             | By opening a static URL the user starts the payment. A hosted payment page collects the payment details.                                                                                                | `payment_link`           |
| [Charge Flow](/documentation/payments/integrations/features/charge-flows.md)               | The payment does not require the user to be present to conduct the payment. An automated process requests the payment details from the user via a message (e.g. email) with a payment URL in it.        | `charge_flow`            |
| [Direct Card Processing](https://{inject-platform-url}/doc/payment/direct-card-processing) | The user enters the debit or credit card number directly within a form provided by the merchant. The card schemes require special security measurements from the merchant for this integration variant. | `direct_card_processing` |

### Choosing an online integration

Three of these modes cover the classic webshop checkout. They differ in how much of the checkout you build yourself:

| Mode             | Customer experience                              | Effort                                     |
| ---------------- | ------------------------------------------------ | ------------------------------------------ |
| **Payment Page** | Redirect to a page hosted by us, then back.      | Lowest — no payment form in your frontend. |
| **Lightbox**     | Overlay on top of your page, no redirect.        | Moderate — one JavaScript handler.         |
| **iFrame**       | Payment form embedded directly in your checkout. | Highest — callbacks and state handling.    |

{% hint style="info" %}
All three keep the payment data on our PCI DSS Level 1 compliant infrastructure, so your PCI scope stays minimal. See [PCI DSS](/documentation/payments/overview/transaction-states/pci-dss.md).
{% endhint %}

{% hint style="warning" %}
**Direct card processing** is the exception: the card number is entered in your own form, so the card data reaches your systems. The card schemes then require additional security measures and a broader PCI certification from you.
{% endhint %}

### Modes for other scenarios

* **Terminal** — card-present payments in your store or at an unattended machine. See [In-Store](/documentation/payments/in-store-payments.md).
* **Payment link** — collect payments without any shop system, through a URL or QR code. See [Payment Links](/documentation/payments/integrations/features/payment-links.md).
* **Charge flow** — collect a payment when the customer is not present, for example for recurring or deferred payments. See [Charge Flows](/documentation/payments/integrations/features/charge-flows.md).
* **Mobile web view** — payments inside your mobile app. See the [mobile SDK documentation](https://{inject-platform-url}/doc/payment/mobile-sdk-web-service-api).