On October 29, 2026, PayBox added Whop to PayBox Markets, opening the storefront network to purchases by connected AI agents. The operator says users can enable Whop now, search its products, place orders and pay, with the buyer controlling purchase approvals.
The launch adds merchants to PayBox’s existing noncustodial wallet and payment product. PayBox describes Markets as MoonPay’s aggregator layer for storefront networks. A market connects once, and its inventory becomes accessible to agents using PayBox. Whop brings products, subscriptions and services sold by businesses on its platform.
The announcement describes both Always Ask and Autonomous modes. The technical documentation sets a narrower rule for purchases through plugins: money tools always pause for the user’s approval, including under an autonomous grant. Enabling Whop does not give an agent permission to make unattended purchases.
From a conversation to an order
PayBox connects to Claude, ChatGPT and Grok through a custom connector. The agent can prepare a transaction within the conversation; the buyer determines when and how money moves. Users can enable Whop on the PayBox app’s Plugins page at app.paybox.sh/plugins, according to the announcement.
The published purchase flow starts with a person asking their agent for an item. PayBox searches Whop for real products with live prices, then prepares an order for the buyer’s selection. Before payment, the buyer reviews the item, total, payment method and recipient. Approval follows that review.
Existing Whop merchants can keep their stores as they are. The announcement says, “For Whop business operators, existing stores become reachable by agents without any changes to their setup.” Agents shop at those existing storefronts; merchants do not have to rebuild them for the launch.
PayBox’s credential model separates an agent integration from the credentials it can use. Each integration runs under its own client key. That key can be rotated or revoked without changing the underlying credentials. Grants specify which credentials the client may use and the approval mode attached to each one.
Approval survives an autonomous grant
In the announcement, Always Ask requires a passkey approval for every transaction. Autonomous permits actions within limits chosen in advance, and users can revoke access. The MCP tools reference qualifies that description: “plugin money tools always pause for the user’s approval, even under an autonomous grant.” The documented purchase rule limits the autonomy described in the launch announcement.
The general request lifecycle explains when an operation needs a person to act. If the grant requires human approval, or the operation crosses a threshold, PayBox returns pending_approval together with an approval_url. The user opens the link and approves with a passkey in the app. Until then, the agent has a pending request, not a completed payment.
Approvals bind to a specific operation and expire after approximately 10 minutes, according to the request documentation. Changing a parameter creates a new request. An approval for one set of purchase details cannot be replayed against a different amount, merchant or payload.
Wallet operations require a separate signing step. A cleared wallet sign or swap enters pending_signature, and the host opens an interactive signing window inside the chat. The window signs client-side through MoonX MPC and posts the signed artifact back to PayBox. According to the documentation, signing happens outside agent code, and the private key never reaches PayBox, the agent or the model.
The announcement describes the key protection as threshold cryptography and secure enclaves. It says no single party, including MoonPay or the AI, holds a full key or can sign alone. This is the operator’s description of its custody architecture, not an independent security assessment of the implementation.
Completion needs a result, not another request
The request lifecycle tells integrators to submit once, then poll get_request using the returned request_id. Repeating the original write call starts another operation and can create a second charge or signature. Integrators finish the approval flow by waiting for the existing request, avoiding a duplicate operation.
PayBox’s general card tooling separates payment authorization from checkout. Its request_payment tool authorizes a merchant-scoped, one-time virtual card. Issuing the card alone neither submits the merchant checkout nor completes the purchase. For human-approved payments, the polled result redacts the card. The agent retrieves usable details through a separate credential-claim call.
The agent must use those details at the merchant’s checkout or API and wait for the merchant to confirm payment before reporting completion. This describes the general card interface, not a verified Whop-specific payment route. For on-chain operations, the reference requires confirmation on-chain before reporting success. Broadcasting a transaction is not enough.
The documentation also describes an audit trail in the app. Requests, approvals, denials, completions and revocations are recorded against the user, client and request for review. Account access depends on preserving passkeys: the approvals page warns that removing the last passkey can lock an account when passkeys are its only protection. Email alone cannot restore a removed passkey.
Eligibility and responsibility remain with the buyer
The announcement names Launchpad Limited, an unregulated MoonPay group entity, as PayBox’s provider. PayBox lacks the same regulatory protections as MoonPay’s regulated services. Access is limited to eligible users, with sanctions screening, a minimum age requirement and jurisdictional restrictions. The features described in the announcement may vary by location.
MoonPay and PayBox do not supply the AI agent. Users remain responsible for their instructions, spending limits and actions taken on their behalf, including under Autonomous mode. Launchpad Limited says it never holds user funds. The disclosure warns that AI-initiated on-chain payments can settle irreversibly.
The launch announcement does not specify the minimum eligible age or list the jurisdictions where Whop purchases are available.
