# Integrations

Two kinds of thing live here. Some services Mercemur talks to natively, where you paste
a credential and it works. Everything else connects through webhooks or the API, which
is how anything with an HTTP endpoint gets in.

## Payments

You connect your own account, and the money settles there. Mercemur adds no
per-transaction fee.

<CardGroup cols={3}>
  <Card title="Stripe" icon="credit-card" href="/guides/take-payments">
    A restricted key on your own account. No `Stripe-Account` header, no application
    fee.
  </Card>
  <Card title="Razorpay" icon="indian-rupee-sign" href="/guides/take-payments">
    Your key id and secret. UPI, cards and netbanking. No Route transfer attached.
  </Card>
  <Card title="Dodo Payments" icon="globe" href="/guides/take-payments">
    Merchant of record. Dodo handles tax and chargebacks and charges you for that
    directly. Cannot serve a cart that needs shipping.
  </Card>
  <Card title="Adyen" icon="building-columns" href="/guides/take-payments">
    An API key on your own account. Card acquiring, 3D Secure, and risk scoring. No
    split attached.
  </Card>
</CardGroup>

## Shipping

<CardGroup cols={2}>
  <Card title="Shiprocket" icon="truck">
    Indian courier aggregation. Credentials are sealed under their own encryption key,
    separate from every other secret in the system.
  </Card>
  <Card title="Manual fulfilment" icon="box">
    No carrier account needed. Mark shipped yourself and the customer is notified the
    same way.
  </Card>
</CardGroup>

## Marketing

<CardGroup cols={2}>
  <Card title="Klaviyo" icon="envelope">
    Connected by OAuth rather than a pasted key. Syncs profiles and events, and can
    import an existing list.
  </Card>
  <Card title="Built-in campaigns" icon="paper-plane">
    Campaigns, flows, forms and preferences without a third party. See the **Marketing**
    tab in the reference.
  </Card>
</CardGroup>

<Note>
  SMS, WhatsApp and push are deliberately not native. They ride your own provider
  through the integration surface below, so the sending relationship, and the
  deliverability reputation, stays yours.
</Note>

## Migrating in

<CardGroup cols={2}>
  <Card title="Shopify catalogue" icon="arrow-right-arrow-left" href="/guides/migrate-from-shopify">
    Products, variants, collections, customers and orders.
  </Card>
  <Card title="Shopify theme" icon="palette" href="/cli/theme">
    Translated into a Mercemur storefront rather than rebuilt. Built from Dawn and
    Horizon.
  </Card>
</CardGroup>

## Connect anything else

These two are the general case, and most integrations are one of them.

<CardGroup cols={2}>
  <Card title="Webhooks" icon="bolt" href="/cli/webhooks">
    Mercemur calls you when something happens. Signed, retried, and replayable from the
    CLI while you are building the receiver.
  </Card>
  <Card title="The REST API" icon="code" href="/api-reference/introduction">
    You call Mercemur. 567 operations, one key, scoped per grant.
  </Card>
</CardGroup>

<Card title="MCP" icon="sparkles" href="/mcp/overview">
  The third door, and the one worth knowing about if the other side is an AI client. An
  agent connects once and can read and write the store directly, without anyone writing
  an integration at all.
</Card>