A clear path
from here to Mitte.

Your first connection.

1. Create your account and verify your email. Enrollment is free, with no card or billing setup.
2. Attach your website’s exact public HTTPS origin. A subdomain is a separate origin.
3. Choose your platform and map your business to a Mitte collection.
4. Add the DNS TXT record shown in Connect, then check verification. Your DNS provider may only need _mitte-challenge in the name field if it automatically appends your domain.
5. Install your SDK or plugin, import or sync your catalog, and test your enabled capabilities.

Unverified sites remain private setup spaces. Email verification unlocks server keys; publishing also requires domain verification. Verification never needs your store password.

Put your business in context.

Choose Shopping, Services or Experiences, then add a category in your own words. Map search, cart and checkout paths to your site. These describe the connection; installed handlers perform actual actions through your store.

The catalog importer lets you match your own JSON field names to Mitte’s product fields. Set whether prices are major or minor currency units before importing. Imports replace the catalog, so include the complete collection you want to share.

{
  "id": "product-01",
  "title": "Your product",
  "description": "A useful, accurate description.",
  "price": 2400,
  "currency": "EUR",
  "url": "https://your-store.com/products/product-01",
  "available": true
}

Your merchant checkout remains authoritative for price and stock. Keep your catalog fresh through the server SDK or plugin sync.

You decide what’s possible.

Official adapters refresh permissions before every action and again after confirmation. Your server must still enforce authentication, stock and price. These settings control the Mitte connection; they do not disable your store’s normal shopping flows.

Your story, in a new shape.

Choose an editorial collection, product grid or concierge layout. Set your name, tagline, story and accent colour. Your real catalog appears in the live design preview.

Save a draft as often as you like. After verifying your email and domain, turn on publishing to make the web experience available at its own partner app URL and in the ecosystem discovery feed.

Native Mitte app visibility uses the existing app review, publishing and installation process. Publishing a partner web experience does not automatically install a native app or give it permission to transact.

One profile. Several ways to connect.

WebMCP exposes structured tools inside a running website when the browser supports it. Agent Web Protocol describes site actions at /agent.json. W2A describes discoverable capabilities at /.well-known/agents.json.

The integrations follow the local draft references used for this build: AWP 0.2 and W2A’s required manifest version 1.0. HTTP manifests advertise implemented search endpoints. Cart and checkout remain in the browser with the customer’s own session and confirmation.

WooCommerce includes the discovery routes. Next.js examples show how to add them. Shopify themes require additional root routing for JSON manifests; a theme script alone does not create those routes.

Keep your connection in your hands.

Account settings let you update your profile, verify your email, change your password, end all sessions or delete your account. Password resets and verification links expire and can be used once. Password changes end other sessions.

Your workspace session stays in an HTTP-only cookie. Site API keys are shown once, stored as hashes and restricted to one catalog and its commerce-event ingestion. Key rotation invalidates the old key immediately. Never place one in public code or a NEXT_PUBLIC_ environment variable.

Deleting a site revokes its keys, removes its catalog and unpublishes its partner app. Deleting an account removes all its partner sites. Sites with a connected payment account or financial records must be retained for outstanding purchases, refunds and reconciliation. Pause their connection instead.

Understand the moment.
See what becomes possible.

Your Intelligence workspace brings together attributed revenue, completed orders, intent categories, customer journeys and returning-customer cohorts. Filter by site, period and currency to explore each connection.

Connect the server SDK to your merchant order lifecycle to record real activity. Revenue comes from merchant-confirmed attributed orders, including confirmed managed payments. Checkout starts stay a separate journey metric. Refunds are recorded against their original order, and currencies are never combined into one money total.

Intent categories describe explicit signals such as comparison, gifting or availability. Customer types reflect observed behaviour, such as first observed purchase or repeat purchase. Reports use aggregate, site-scoped cohorts and do not infer sensitive personal traits.

Projections show what may happen under your selected order-volume assumption, using the recorded net-revenue run rate. They require sufficient history and remain scenarios, separate from actual results. An empty workspace shows no data until your integration sends real events.

From payment to a delivered result.

Open your website’s Payments tab to connect Stripe, review its requirements and choose manual or automated fulfilment. Verify your email and domain, then enable checkout permission and payments when your business is ready. Test and live payment records remain separate.

1. Your server creates a fixed quote from your own prices, availability, taxes and delivery charges.
2. The customer reviews and authorizes payment on Stripe’s hosted checkout.
3. Mitte confirms payment through Stripe. Your business then delivers the purchase, service or action and records a receipt.
4. Eligible proceeds transfer to your connected Stripe balance after fulfilment. Bank payouts follow your Stripe schedule.

After payment is confirmed, the order panel shows private recipient and delivery details for manual fulfilment. Contact details, shipping addresses and internal notes stay off the customer’s public receipt.

Mitte’s platform fee is zero during early access. Stripe fees still apply; the workspace shows whether processing fees are deducted from partner proceeds or covered by Mitte. Refunds and transfer recovery appear separately so an unresolved financial step stays visible.

import { createPaymentClient } from '@mitte/partners/payments';

// Server only. Use the dedicated key from your website’s Payments tab.
const payments = createPaymentClient({
  siteId: process.env.MITTE_SITE_ID,
  portalOrigin: process.env.MITTE_PARTNERS_ORIGIN,
  paymentKey: process.env.MITTE_PAYMENT_KEY,
});

const checkout = await payments.createCheckout(savedMerchantQuote);
// Send checkout.checkoutUrl to the customer for approval.

Automated fulfilment uses a separate server worker. It claims paid orders, completes your actual business operation and acknowledges the resulting receipt. Store each result using the Mitte order ID so retries cannot deliver the same action twice. The integration package includes a working digital-access example. Returning from checkout alone never marks an order paid or fulfilled.

Managed payments support one partner per purchase. Existing Shopify and WooCommerce native checkouts continue to work; connecting a discovery plugin does not automatically replace their payment gateway.