Troubleshooting

First Checks

Start by separating browser progress, MagicPay request state, and provider payment state. Most failures become clear once you know which boundary is waiting.

• Confirm the session id and client request id are stable and visible in logs.
• Confirm the user has at least one enabled approval channel.
• Check whether the agent is waiting on MagicSearch, MagicBrowse, a request artifact, or a provider callback.
• Never retry by asking the user to paste Memory values into chat.

MagicBrowse Cannot Reach Checkout

If MagicBrowse cannot reach a checkout, reduce the task to a browser-only milestone. Ask it to reach the cart, provider handoff, or visible Memory-managed boundary before involving MagicPay Memory fill.

• Use a precise merchant URL when possible.
• Prefer MagicSearch when the provider choice is ambiguous.
• Treat CAPTCHA, login, and payment pages as handoff points instead of failures.

Request Not Appearing

If a request is created but not visible to the user, check request channel configuration and whether the request is scoped to the expected user, agent, and session.

Memory Value Not Resolving

If MagicPay Memory cannot resolve a value, verify the field purpose, merchant context, candidate item, and user approval path. Missing data should become a write request, not an LLM-visible chat question.

Payment Action Stuck

If a payment action is stuck, distinguish user approval from provider execution. A fulfilled request may still wait for a Mercuryo callback, webhook replay protection, or card/provider state update.

Mercuryo Account Or Card State

For Mercuryo-backed issues, check account link status, KYC status, questionnaire and phone prerequisites, spend-card issuance, balance sync, top-up transaction state, and signed webhook ingress.

Related Docs