Documentation v1.24
Last updated 2026-05-25 Give feedback

Getting Started

Choose the UI-first path to manage MagicPay surfaces, or the agent-first path to connect a runtime and start a low-risk payment session.

Get Started With UI

Use this path when you want to set up the human control surface first. The UI lets you manage MagicCard state, review sessions, respond to requests, and choose the platform where approvals should arrive.

  1. Create an account with email, Apple, or Google. Email signup uses an OTP.
  2. Create or link the Mercuryo payment account for the same email.
  3. Pass KYC through SumSub. The current public flow supports EU citizens first.
  4. Top up the MagicCard balance. Crypto top-up is available now; fiat top-up is planned.
  5. Open the Web app, iOS app, Android app, ChatGPT app, Claude app, or Telegram miniapp and choose the request channels you want to use.
  6. Add useful Memory such as delivery addresses, logins, or passport details from the UI before a session needs them.

Get Started With The Agent

Use this path when you already know which agent runtime should pay for you. The agent setup flow connects the runtime to MagicPay, then relies on requests whenever user approval or Memory data is needed.

  1. Prepare the account, KYC, and MagicCard balance first, or keep the UI open while you complete those steps.
  2. Copy the generated setup prompt into a supported runtime such as OpenClaw, Hermes, Codex, Claude, or another Agent Skill compatible agent.
  3. Ask for a small, specific first task with a clear success condition, such as a low-risk checkout or a page you already trust.
  4. Let the agent create the payment session and wait for MagicPay requests when approval, choice, login, identity data, or payment execution is required.
  5. Approve or deny requests in your preferred UI surface.
  6. Review the session events after the run and save any reusable Memory or preferences that would make the next session smoother.

What Both Paths Need

Both paths lead to the same operating model: the user owns payment authority, MagicPay owns Memory request handling, and the agent continues only after the required approvals or Memory-managed actions complete.

  • A user account with a linked Mercuryo payment account.
  • Completed KYC for the supported region.
  • A funded MagicCard balance.
  • At least one enabled request channel for approvals and confirmations.
  • A constrained first purchase that is easy to verify.
MagicPay public documentation.