Integrations

Afterpay

Connect Afterpay to find orders, capture and refund payments, make checkouts, and answer disputes. Setup guide for Claude, ChatGPT and other MCP clients.

API credentialsApproval, Afterpay publishes no turnaroundFinance & BillingAfterpay API docsAfterpay MCP server overview

You paste your Merchant ID and Secret Key from the Afterpay Business Hub. PopMCP works out whether they are live or sandbox by trying them.

Seller/marketplace approval before this connector works

You need an approved Afterpay merchant account. Afterpay reviews a business before opening one, and a merchant building its own integration gets production credentials after Afterpay's certification.

Typical wait
Afterpay publishes no turnaround.
Cost
No fee for API access. Afterpay's own fees apply to payments, under your agreement with Afterpay.
Blocked until approved
The whole connection, since the Merchant ID and Secret Key come from an approved account.
Works meanwhile
Nothing on your own. Sandbox credentials come from your Afterpay account manager.

Where to apply: Apply through Afterpay's site for your region, or through Clearpay in the UK. If you already take Afterpay, a Hub Admin can see the credentials in the Business Hub under Settings.

  • Only a Hub Admin can see the Secret Key. Other Business Hub users see just the Merchant ID.
  • Each region has its own Merchant ID and Secret Key, so a second region is a second connection.
  • On file payments need separate approval from Afterpay, and are available only in Australia, New Zealand and the United States.
Setup time
3 min
Auth
API credentials
API base URL
Live: https://global-api.afterpay.com. Sandbox: https://global-api-sandbox.afterpay.com. Both serve every region, including Clearpay. PopMCP picks the right one.
Rate limits
Afterpay publishes no number. Over a limit it answers HTTP 429. Afterpay says a capture, refund or void can take up to 70 seconds to answer, and PopMCP waits for it.

Before you begin

  • An approved Afterpay merchant account, or Clearpay in the UK.
  • A Business Hub login with the Hub Admin role. Other roles can see the Merchant ID but not the Secret Key.

Get your credentials

Open Settings in the Business Hub

Sign in to the Business Hub as a Hub Admin and open the Settings tab. The direct link is hub.us.afterpay.com/settings. UK merchants use hub.clearpay.co.uk/settings. If you are not a Hub Admin, you will see the Merchant ID but not the Secret Key, so ask one for help.

Open this screen →

hub.us.afterpay.com/settings
Acme Store
Settings

Settings

A Hub Admin can see the merchant credentials here.

Copy your Merchant ID and Secret Key

Copy both values. Each region has its own pair, so if you sell in two regions, connect each one on its own. Keep the Secret Key private: it reaches everything your merchant account can do.

Open this screen →

hub.us.afterpay.com/settings
Acme Store
Settings

Settings

Merchant ID
600032000
Secret Key
••••••••••••
Anyone with these two values can act on your merchant account.

Paste them into PopMCP

Open Afterpay in PopMCP, paste your Merchant ID and Secret Key, and connect. There is nothing else to fill in: PopMCP tries the pair on Afterpay's live system and then on its sandbox, and reads your limits and currency, which changes nothing.

Allow writes only if you want them

New connections start read-only, so the AI can find orders and read disputes but cannot change anything. Allow writes on the connection if you want it to capture, refund, void or answer disputes. On live details those move real money, so ask it to confirm first.

To use the sandbox

Most people skip this. Sandbox credentials come from your Afterpay account manager, who can also give you access to the sandbox Business Hub at portal.sandbox.afterpay.com/merchant/. Connect them in the same way. PopMCP recognises them as sandbox, and no money moves.

Connect in PopMCP

Open your workspace, choose Afterpay in the marketplace, and fill in the connect dialog:

FieldWhat to enter
Merchant IDtextFrom the Settings tab of your Afterpay Business Hub. Each region has its own.
Secret KeysecretFrom the Settings tab of your Afterpay Business Hub, next to the Merchant ID. Stored encrypted, used server-side only.Encrypted with AES-256-GCM on save and never shown again.

PopMCP verifies the credential against Afterpay immediately. On success the connection flips to Verified and its MCP tools are provisioned.

Verify it worked

PopMCP shows Afterpay as Verified, named with your Merchant ID, your region, and live or sandbox. Ask for an overview: afterpay_account_overview answers with the system, your order limits, your latest orders and the disputes waiting on you.

Troubleshooting

"Afterpay did not accept this Merchant ID and Secret Key"

Why: One of the values was copied incompletely, or they belong to a different region.

Fix: Copy both again from Settings in the Business Hub, as a Hub Admin, and check they are for the region you mean.

"Afterpay knows this Merchant ID but refused it"

Why: The account may not be active.

Fix: Check the account in the Business Hub, or ask your Afterpay account manager.

I can see the Merchant ID but not the Secret Key

Why: Only a Hub Admin can see the Secret Key.

Fix: Ask a Hub Admin on your account to copy it, or to change your role.

On file tools answer feature_not_enabled

Why: On file payments need separate approval from Afterpay.

Fix: Ask your Afterpay account manager. The rest of the connection works without it.

A checkout does not appear as an order

Why: A checkout is only a link. No order exists until the customer confirms and the checkout is finished.

Fix: After the customer returns, finish it with afterpay_capture_full_payment or afterpay_authorize_payment.

Reference

On this page