afterpay_authorize_ paymentApprove an order after the customer confirms, without taking the money yet (deferred capture).
Find any order, capture or refund it, start a checkout, answer a dispute with evidence, and total your sales for a period, all by asking, on live or sandbox.
PopMCPAfterpay
Every operation in the Afterpay Online API is here: checkouts, payments, disputes, on file grants, Cash App Pay grants and configuration, along with the older billing agreements. The everyday tools load by default and the rest are one search away. A few do a whole job at once, such as refunding what is left on an order after checking it first.
37 tools in the full catalog: 16 read and 21 write. 33 load by default, and the rest are found with tool search.
afterpay_authorize_ paymentApprove an order after the customer confirms, without taking the money yet (deferred capture).
afterpay_capture_ full_ paymentFinish a checkout and take the full amount now: this moves real money and starts the customer's payment plan.
afterpay_capture_ paymentCapture part or all of an approved order: this moves real money.
afterpay_create_ refundRefund part or all of a captured order: this returns real money to the customer and cannot be undone.
afterpay_get_ paymentGet one order by its numeric Afterpay order id: status, amounts, customer, items, events and refunds.
afterpay_get_ payment_ by_ tokenGet one order by its checkout token, when you have the token but not the order id.
afterpay_list_ paymentsList or search orders, newest first by default.
afterpay_reverse_ payment_ by_ tokenCancel a just-made order by its checkout token, for when a capture or auth call timed out and you do not know if the order was made.
afterpay_update_ payment_ merchant_ referenceSet your own order number on an Afterpay order.
afterpay_update_ shipping_ courierAdd shipping details to an order: when it shipped, the courier, tracking number and priority.
afterpay_void_ paymentCancel what has not been captured yet on an approved order and refund the customer that part: this cannot be undone.
afterpay_accept_ disputeGive up a dispute: it is closed as lost and the customer keeps the money.
afterpay_account_ overviewStart here: which Afterpay system this connection is on (live or sandbox), the region and currency, the order amounts this merchant can take, the latest orders and the disputes waiting on you.
afterpay_capture_ remaining_ amountCapture everything still open on an approved order: this moves real money.
afterpay_create_ grantCreate the saved payment grant once the customer has approved, from the token of afterpay_create_grant_approval.
afterpay_create_ grant_ approvalStart asking a customer to save Afterpay for later purchases.
afterpay_get_ disputeGet one dispute: reason, status, amount, the customer's note and attachments, and the deadline.
afterpay_get_ dispute_ fileGet a temporary download link for a dispute file, such as a customer's attachment.
afterpay_get_ grantGet one saved Afterpay grant by id: its status and details.
afterpay_list_ disputesList disputes on your orders.
afterpay_open_ disputesDisputes waiting on you, soonest deadline first, each with its deadline, reason, amount and the customer's note, and the order for the first few.
afterpay_payment_ overviewEverything about one order in one call, found by order_id, token or merchant_reference (give one): status, amounts, what can be captured or refunded now and until when, its events and refunds, and any dispute.
afterpay_refund_ remaining_ amountRefund everything captured and not yet refunded on an order: this returns real money to the customer and cannot be undone.
afterpay_respond_ to_ disputeSubmit your evidence to challenge a dispute: there is only ONE chance, it goes in at once and cannot be changed.
afterpay_revoke_ grantCancel a saved Afterpay grant, so it can no longer be charged.
afterpay_sales_ summaryAdd up orders in a period, per status and currency: order count, order value, refunds and what is still uncaptured.
afterpay_upload_ dispute_ fileUpload one evidence file for a dispute and get its id, to pass to afterpay_respond_to_dispute.
afterpay_create_ checkoutStart a checkout and get a token and redirectCheckoutUrl to send the customer to.
afterpay_get_ cash_ app_ pay_ grantGet a saved Cash App Pay grant, by the customer id and grant id.
afterpay_get_ checkoutRead a checkout that has not been completed yet.
afterpay_get_ configurationGet the order amounts this merchant can take: minimumAmount and maximumAmount.
afterpay_revoke_ cash_ app_ pay_ grantCancel a saved Cash App Pay grant, so it can no longer be charged, by the customer id and grant id.
afterpay_create_ order_ from_ grantStart an order using a customer's saved Afterpay or Cash App Pay grant.
afterpay_create_ grant_ aliasMake a short lived alias of a grant token, used to load the payment schedule widget.
afterpay_start_ grant_ linkStart the link flow with no Afterpay page: sends an one-time code to the customer's email or phone, which contacts a real customer.
afterpay_get_ configuration_ mappingsGet this merchant's Cash App Pay brand id, needed to set up Cash App Pay on file.
afterpay_pingCheck Afterpay's API is up.
Credentials off one Afterpay screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
Sign in to your Afterpay Business Hub as a Hub Admin and open Settings, where your Merchant ID and Secret Key are. Open Afterpay in PopMCP, paste both and connect. PopMCP works out whether they are live or sandbox, and reads your region from your account, so there is nothing else to fill in. UK merchants use the Clearpay Business Hub.
your-afterpay-value••••••••••••3f7aCaptures, refunds, voids, reversals and dispute answers take effect the moment the AI calls them, and on live details they move real money, so ask it to confirm first. New connections start read-only until an owner or admin allows writes in PopMCP, because Afterpay's credentials have no read-only setting of their own. Card details are refused before anything is sent, and a dispute answer that would be empty is refused too, since Afterpay allows only one.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Afterpay credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
What can still be captured or refunded on order 12345678?
afterpay_get_paymentok
Then just ask for the work
“What can still be captured or refunded on order 12345678?”
“Refund 25.00 on this order and tell me what is left to refund”
“Find the order with my reference ORD-1042 and show its status and customer”
“Which disputes are waiting on me, and when are they due?”
“Answer this dispute with the attached proof of delivery”
“Make a checkout for 80.00 and give me the link to send my customer”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting Afterpay behind an AI client.
No. Your Merchant ID and Secret Key are in the Settings tab of the Afterpay Business Hub. Only a Hub Admin can see the Secret Key, so ask one if you cannot.
Yes. Afterpay reviews a business before opening a merchant account, and the credentials come from that account. Sandbox credentials come from your Afterpay account manager.
The credentials decide. PopMCP tries them on Afterpay's live system and then on its sandbox, where no money moves, and the connection profile always says which one the AI is using.
Yes. Clearpay is Afterpay's name in the UK, and it uses the same API. Get your Merchant ID and Secret Key from the Clearpay Business Hub, in Settings. Australia, New Zealand, Canada and the United States work the same way, and each region has its own pair.
Only if you allow it. New connections start read-only. Once writes are on, captures and refunds are real, so ask it to confirm first. Each one carries a request id, so a retry does not act twice.
A checkout is only a link for the customer. The order exists once the customer confirms and the checkout is finished with a capture or an approval, which the AI can do.
No. Afterpay publishes no API for settlement files, so those stay in the Business Hub. The AI can total your orders for a period, which is not the same as what reached your bank.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect Afterpay in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Afterpay on the consent screen. The Afterpay tools are then available in that session, and no Afterpay credential is stored on your machine.
Loading 37 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 33-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 37 here. A trigger is something PopMCP watches for you: 3 Afterpay events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Afterpay.
Launch a hosted MCP endpoint for Afterpay, keep tool access under control, and start testing real workflow prompts right away.