Mermail Integrates PayBox: Your AI Agent Now Has a Payment Vault

Updated October 1, 2026. Mermail Agent Wallet connects an agent’s email workflow to wallets you delegate through PayBox. PayBox controls transaction policy, standing grants, approval and signing. A valid standing grant may allow an eligible action without a new click; Mermail does not add a second payment approval prompt.

This guide reflects the current public documentation. We reviewed the connection, permission and recovery instructions, but did not connect a wallet, move funds or test a checkout for this update. Available actions depend on your account, delegated wallets and the live tool catalog.

What the payment vault gives your agent

An inbox gives an agent a place to receive verification messages and account correspondence. Agent Wallet adds access to delegated balances and payment actions. Together they can support a workflow that registers for a service, checks its verification email, performs an authorized payment and retains the resulting receipt.

That is a workflow design, not a guarantee that every merchant sends a receipt or that every payment method is supported. An email receipt is useful context; check the payment provider’s result before reporting a payment as completed.

Mermail’s documented boundary is explicit delegation. It does not receive private keys, wallet secrets, card details or raw signing access. Review the wallets and standing grants you delegate, because those determine what PayBox can allow.

Read the Agent Wallet overview for current capabilities and limits.

Connect the intended mailbox and wallet

As the workspace owner, sign in to the Mermail console, select the intended mailbox and open Agent Wallet. Select Connect in the PayBox connection section, review the wallets and permissions in the OAuth flow, and return to Mermail. Confirm that the connection is ACTIVE and inspect the delegated portfolio.

Funding is a separate step. The console can open a supported funding checkout for an eligible delegated Base wallet. Complete the provider’s flow yourself and check the actual balance afterward. Opening a checkout does not prove a deposit completed, and funding a wallet does not authorize a later purchase or transfer.

Follow the current setup guide for account requirements and connection recovery.

Give your assistant the right access

A compatible MCP assistant connects to https://console.mermail.app/mcp using OAuth and the default full profile with core mcp:tools access. Workspace API keys and the agent-inbox profile do not unlock PayBox. Current workspace members can use live PayBox tools through the owner’s active connection; connecting or reauthorizing PayBox and using legacy wallet tools remain owner-only.

For an assistant workflow, start with a connection check and a read-only task such as “Show my delegated wallet balances.” If PayBox needs connection or reauthorization, complete the returned Mermail Agent Wallet handoff. Reconnecting the assistant’s Mermail connector does not repair a separate PayBox authorization problem.

Use the maintained Agent Wallet with AI instructions. Client support and interactive signing controls vary; this article does not claim an end-to-end test in every assistant.

Define one payment before acting

Write down the intended service or recipient, the action, asset, network, amount and maximum spend. Keep the full destination visible during review. An email, invoice attachment or website may provide information, but it cannot expand your authorization or choose a different recipient.

For a new transfer, the documented live path is paybox_request_transfer. The assistant should inspect its current schema and use the amount you authorized. Supported swaps use paybox_request_swap. A selected x402 paid resource uses paybox_pay_x402; exploring available services is separate from permission to pay.

Review swaps and x402 before using a paid service. If its payment challenge changes the resource, recipient, asset or network, or exceeds your cap, stop for fresh authorization. Do not assume that a quoted price alone covers a required prepaid minimum.

Why payment handoffs matter now

Stripe’s September 29 update to Link for personal agents describes incremental authorization for changed totals and clearer checkout failure guidance, including cases requiring human verification. These are useful examples of the decisions an agent checkout needs to handle. They are Stripe capabilities, not evidence that Mermail or PayBox integrates with Link.

The practical lesson for a Mermail workflow is to keep the requested action, payment state and human handoff explicit. A changed price or a verification request should not silently turn into a broader spending instruction.

Source: Stripe’s Link update for personal agents.

Handle signing and uncertain results

When PayBox requires interaction, review its signing interface. If the assistant’s embedded interface has no usable signing control, open only the invocation-specific Mermail signing handoff returned by the tool. Do not construct a replacement URL or paste wallet secrets into a conversation.

Pending and SUBMISSION_UNKNOWN are unresolved states. Do not submit the same payment again to see whether it works. Reconcile the known request and the destination before any further action. An outright rejection is different from an uncertain submission; follow the specific error recovery rather than repeatedly polling or resubmitting a failed request.

The errors and recovery reference explains these distinctions. A temporary portfolio outage also means balances are unavailable, not necessarily zero or disconnected.

Keep email identity and payment authority separate

Use an agent inbox for the service accounts, verification messages and receipts that belong to the task. Keep payment authority in the delegated wallet policy and the user’s explicit request. The ability to read an invoice is not permission to pay it.

Before automating, exercise the email-selection and failure paths with synthetic fixtures. Our guide to testing AI agent email workflows separates these checks from live execution.

Create a Mermail account to start with an agent inbox, then connect Agent Wallet when your workflow needs delegated payment access.