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

# Integration approaches

> Compare Tilta's integration methods – from no-code Checkout Links to the full REST API and the MCP server – and choose the right fit.

Tilta offers several integration approaches so you can match the level of control and implementation effort to the work at hand. Whether you want a working integration in minutes, a fully bespoke checkout experience, or an AI client driving your receivables, there is a path designed for you.

Nothing here depends on whether the receivables are your own or a third party's. The approaches are the same for a trading business financing its own sales ledger and for a platform acting on behalf of its merchants.

<CardGroup cols={2}>
  <Card title="Checkout Link" icon="link">
    The simplest option – no code required. Generate payment links directly from the Tilta Portal and share them with buyers via email, WhatsApp, or any channel you choose. Ideal for low-volume or manual workflows where a developer integration is not needed.
  </Card>

  <Card title="Hosted redirect" icon="square-arrow-out-up-right">
    The fastest developer integration. Redirect your merchant or buyer to a Tilta-hosted, authenticated session. Tilta handles all onboarding and checkout UI, so you can go live with minimal front-end work.
  </Card>

  <Card title="Web Elements" icon="square-mouse-pointer">
    Tilta's embeddable SDK renders Widgets (inline) and Modals (overlay) natively inside your application. You get a customised look and feel without building the underlying flows from scratch. Ideal when you want a branded experience with low implementation overhead.
  </Card>

  <Card title="REST API" icon="chevrons-left-right-ellipsis">
    Full access to every Tilta endpoint. You build all UI yourself, giving you complete control over the buyer experience. Best suited to teams with engineering capacity and complex integration requirements.
  </Card>

  <Card title="MCP server" icon="sparkles">
    Connect Claude or another MCP client to your Tilta account and work through onboarding, financing, and analytics in natural language. Ideal for operational and exploratory work rather than unattended, high-volume flows.
  </Card>
</CardGroup>

## Approach comparison

Use the table below to see how each developer-facing approach stacks up across the dimensions that matter most.

| Feature                    | Hosted redirect | Web Elements | REST API | MCP server |
| -------------------------- | --------------- | ------------ | -------- | ---------- |
| **Ease of implementation** | ⭐⭐⭐⭐⭐           | ⭐⭐⭐          | ⭐        | ⭐⭐⭐⭐⭐      |
| **Customisability**        | ⭐               | ⭐⭐⭐          | ⭐⭐⭐⭐⭐    | ⭐          |
| **Buyer onboarding**       | ✅               | ✅            | ✅        | ✅          |
| **Merchant onboarding**    | ✅               | ✅            | ✅        | ❌          |
| **Order checkout**         | ✅               | Upcoming     | ✅        | ❌          |
| **Unattended operation**   | ✅               | ✅            | ✅        | ❌          |

<Note>
  The **Checkout Link** approach is portal-only and requires no developer work. It is not listed in the comparison table above because it does not involve an API or SDK integration.
</Note>

## Choosing the right approach

<Tabs>
  <Tab title="I want the fastest go-live">
    Start with **Hosted redirect**. You only need to generate an authenticated URL on your server and redirect the user. Tilta hosts all onboarding and checkout screens, so your front-end work is minimal. You can layer in a more customised approach later once you are live.
  </Tab>

  <Tab title="I want a branded experience">
    Use **Web Elements**. The SDK renders Tilta's onboarding and payment flows as Widgets or Modals inside your existing UI. You control placement, theming, and the surrounding page, while Tilta handles the complex financial flows. Order Checkout support is coming soon.
  </Tab>

  <Tab title="I need full control">
    Choose the **REST API**. Every Tilta feature is exposed as a REST endpoint, and you build all UI yourself. This approach takes the most engineering effort but places no constraints on your user experience or tech stack.
  </Tab>

  <Tab title="I don't want to write code">
    Use **Checkout Links** from the Tilta Portal. You generate a link and send it directly to the buyer – no integration required.
  </Tab>

  <Tab title="I want to work in natural language">
    Connect the **MCP server** to Claude or another MCP client. You can onboard a buyer, submit an invoice for financing, and ask questions about your ledger without writing any code. Best for operational work you do yourself, not for automated flows.
  </Tab>
</Tabs>

## Integration guides

Once you have chosen your approach, follow the corresponding guide to get started.

<CardGroup cols={2}>
  <Card title="Hosted redirect" icon="square-arrow-out-up-right" href="/docs/integration-server-side">
    Redirect buyers and merchants to Tilta-hosted sessions.
  </Card>

  <Card title="Web Elements" icon="square-mouse-pointer" href="/docs/integration-web-elements">
    Embed Widgets and Modals in your platform with the JS SDK.
  </Card>

  <Card title="REST API" icon="chevrons-left-right-ellipsis" href="/docs/integration-server-side">
    Integrate directly with the Tilta REST API.
  </Card>

  <Card title="MCP server" icon="sparkles" href="/docs/integration-mcp">
    Connect an AI client to your Tilta account.
  </Card>

  <Card title="Shopware 6 plugin" icon="plug" href="/docs/integration-shopware-plugin">
    Install the ready-made Shopware 6 payment plugin.
  </Card>
</CardGroup>