Skip to main content
Claude renders MCP UIs inside the chat, so customers see SolvaPay’s plan and account views without leaving the conversation. Claude does not allow the card form inside that UI, so checkout opens as a SolvaPay-hosted page in Claude’s built-in browser. Account pages open there too.

What works

  • Text and links: supported.
  • MCP UIs: rendered inline in the chat.
  • Payment form: hosted page, in Claude’s built-in browser.
  • Account pages: hosted page, in Claude’s built-in browser.

Checkout

When a paid tool is blocked, the response text states the limit and links to hosted checkout. If the customer opens checkout from the MCP UI, the UI hands the link to Claude, which opens it in its built-in browser. After payment, the customer returns to the chat and the next call to the paid tool runs.

Account pages

Plan, usage and billing history always live on SolvaPay-hosted pages. Claude opens them in its built-in browser.

MCP UIs

Claude supports MCP Apps, so the SolvaPay account tool renders its plan, checkout and top-up views inline. See the MCP App integration guide to build or customize them.

Connect your MCP server

  1. In Claude, go to Customize > Connectors.
  2. Select +, then Add custom connector.
  3. Enter your MCP server URL and select Add.
  4. Select Connect and sign in when prompted.
Team and Enterprise owners add the connector under Organization settings > Connectors first. See Claude’s custom connector guide for plan-specific steps.

Known limitations

  • Claude’s sandbox blocks the embedded card form, so card entry always happens on the hosted page.
  • Claude’s sandbox also blocks pop-ups. Links inside the MCP UI open through Claude rather than a new browser tab. The SolvaPay React components handle this for you.
  • Hosted checkout links expire after 15 minutes. Ask the assistant for a new link if one has expired.
Last tested: 2026-09-30