Afterpay MCP. Handle BNPL payments and refunds via chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Afterpay MCP Server handles Buy Now, Pay Later (BNPL) payments. Connect your Afterpay merchant account to your AI agent to manage checkouts, monitor payments, and process refunds through natural conversation.
Your agent executes financial transactions, from creating secure checkout tokens to initiating partial refunds, without you needing to open the merchant dashboard.
It’s complete BNPL orchestration.
What your AI agents can do
Create checkout
Initiates a secure Afterpay BNPL payment session token for a customer transaction amount.
Get afterpay config
Retrieves the minimum and maximum order transaction limits set on your Afterpay merchant account.
Get payment details
Gets detailed financial status, settlement info, and logs for a specific Afterpay order ID.
Use create_checkout to start a secure BNPL payment session and get a redirect token for a customer.
Call get_afterpay_config to check your merchant account's minimum and maximum order limits.
Run get_payment_details to pull detailed financial status, settlement info, and logs for a specific order ID.
Use list_payments to retrieve a secure list of historical BNPL transactions and authorizations.
Run refund_payment to send a full or partial refund to a customer's account against a captured order.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Afterpay MCP Server: 5 Tools for Payments & Refunds
These tools let your AI agent manage the entire payment lifecycle: creating checkouts, checking status, listing history, and processing refunds.
019d7549create checkout
Initiates a secure Afterpay BNPL payment session token for a customer transaction amount.
019d7549get afterpay config
Retrieves the minimum and maximum order transaction limits set on your Afterpay merchant account.
019d7549get payment details
Gets detailed financial status, settlement info, and logs for a specific Afterpay order ID.
019d7549list payments
Retrieves a secure list of historical BNPL transactions and authorizations from your Afterpay account.
019d7549refund payment
Initiates a full or partial refund to credit a consumer against a previously captured Afterpay order.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Afterpay, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Your AI agent talks straight to your Afterpay merchant account, handling every part of Buy Now, Pay Later (BNPL) payments. You won't gotta open that merchant dashboard to manage checkouts, monitor payments, or process refunds—your agent does all that for ya. You'll get full BNPL orchestration right through natural conversation.
Manage Checkout Sessions
To start a secure BNPL payment session for a customer, you'll use create_checkout, which spits out a redirect token for the transaction amount. Audit Order Limits
You can call get_afterpay_config to check the minimum and maximum order limits set on your Afterpay merchant account. Check Payment Status
Run get_payment_details to pull detailed financial status, settlement info, and logs for a specific Afterpay order ID. List Transaction History
Use list_payments to get a secure list of historical BNPL transactions and authorizations from your Afterpay account. Process Refunds
Run refund_payment to send a full or partial refund to a customer's account against a captured Afterpay order.
How Afterpay MCP Works
- 1 Subscribe to the server and input your Afterpay Merchant ID and Secret Key credentials.
- 2 Your AI client sends a natural language prompt (e.g., 'Refund $50 for order 123').
- 3 The agent executes the necessary tool (
refund_payment) and returns the status and confirmation details.
The bottom line is you manage the entire BNPL payment flow through conversation, using the agent to call the necessary APIs.
Who Is Afterpay MCP For?
This is for Finance Operations teams who need to process refunds and audit transaction logs without logging into a dashboard. It's for E-commerce Managers who need to verify order limits on the fly. Customer Support agents need a way to quickly look up payment statuses and order history to resolve billing questions without escalating to a specialized team.
Automates refund processing and audits transaction logs by calling refund_payment or list_payments via chat.
Checks order limit configurations using get_afterpay_config and monitors checkout health by running create_checkout.
Looks up payment statuses and order history for customers by querying get_payment_details or list_payments.
What Changes When You Connect
- Process refunds instantly. Use
refund_paymentto issue full or partial credits to a customer directly from your chat interface, skipping the refund screen in the dashboard. - Monitor checkout health. Quickly generate new payment sessions using
create_checkoutand retrieve the necessary redirect tokens, testing the payment flow instantly. - Audit financial limits. Run
get_afterpay_configto verify your minimum and maximum order limits. This is essential before processing high-value transactions. - Deep payment visibility. Instead of manual exports, use
list_paymentsto get a complete, secure history of all historical BNPL transactions and authorizations. - Check specific order status. Use
get_payment_detailsto pull detailed settlement info and logs for any specific order ID, solving complex billing questions fast.
Real-World Use Cases
Billing Inquiry: Customer needs to know why a payment failed.
A customer calls support about a failed payment. Instead of asking the customer to provide an ID, the support agent asks their agent to run get_payment_details for the provided order ID. The agent returns the exact payment status and capture time, allowing the agent to resolve the issue without manual dashboard investigation.
End-of-Day Reconciliation: Need to verify all transactions.
The finance ops team needs to reconcile all payments processed today. They ask their agent to run list_payments. The agent compiles the full list of historical BNPL transactions, confirming authorizations and captures, which they can then use to build a report.
Operational Change: Need to test a new product checkout.
An e-commerce manager needs to test a checkout flow for a new product. They instruct their agent to run create_checkout for the specific amount. The agent generates the secure redirect token and URL, allowing the manager to test the full payment flow before going live.
Emergency Correction: A customer was overcharged by $25.
A manager spots an overcharge and needs to correct it immediately. They prompt their agent to run refund_payment for the specific order ID and amount. The agent confirms the refund status and provides the necessary transaction reference.
The Tradeoffs
Assuming data is always available.
A developer writes code that calls list_payments and then assumes the resulting list has all the necessary metadata, causing the payment logic to fail when key fields are missing or null.
→
Don't just list payments. Use get_payment_details on the specific Order ID after running list_payments. This forces the agent to retrieve detailed settlement info, ensuring you have all the required metadata for reliable logic.
Trying to manage state manually.
A client calls create_checkout and then tries to manually wait for a webhook, assuming the subsequent state changes can be queried using general methods, leading to race conditions.
→
The agent manages the state. If you need to check the status later, use get_payment_details with the initial Order ID. This queries the authoritative status, bypassing manual state tracking.
Ignoring transaction limits.
Attempting to process a checkout for a high amount without knowing the account restrictions, resulting in the payment failing mid-transaction.
→
Always check the limits first. Run get_afterpay_config before initiating any large checkout flow. This verifies the minimum and maximum order limits against your account settings.
When It Fits, When It Doesn't
Use this server if your workflow requires managing the entire BNPL lifecycle—from initial checkout token generation (create_checkout) to final payment status checks (get_payment_details) and necessary reversals (refund_payment). This is for operations and support teams who need to handle payments conversationally.
Don't use this if you only need to view a static report. If you only need to pull a simple, historical list of transaction IDs, list_payments is fine. But if you need the full settlement data or want to execute a payment action, you need the full suite of tools. If you only care about the limits, get_afterpay_config is enough. You need the full stack to make money moves.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Afterpay. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 5 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually checking payment status is a time sink.
Today, checking a customer's payment status means logging into the Afterpay dashboard, searching for the order ID, and clicking through several tabs: 'Payments,' then 'Details,' and finally 'Status.' If you need to check ten orders, that's ten different logins and twenty clicks.
With the Afterpay MCP Server, you just tell your agent to check the status. It runs `get_payment_details` and returns the status, capture time, and settlement info immediately. You get the answer without leaving your chat window.
Afterpay MCP Server: Complete Payment & Refund Ops
You no longer need to switch between creating checkout tokens and then opening a separate tool to process refunds. The agent manages the sequence: you tell it to refund, and it automatically uses `refund_payment` against the correct order ID and amount.
The difference is the control layer. You stop thinking about the sequence of API calls and start thinking only about the business outcome—'refund this,' or 'check this out.' It just works.
Common Questions About Afterpay MCP
How do I create an Afterpay checkout session using the `create_checkout` tool? +
You prompt your agent to initiate the checkout session for the required amount. The agent runs create_checkout and returns the secure checkout token and the redirect URL needed for the customer.
Can I list all payments using the `list_payments` tool? +
Yes. The agent runs list_payments and securely retrieves a full, historical list of BNPL transactions and authorizations from your Afterpay account.
What information does `get_payment_details` provide? +
get_payment_details pulls deep financial data for a specific order ID. It includes the payment status, settlement information, and technical logs, far beyond a simple status check.
How do I process a partial refund with `refund_payment`? +
You ask the agent to refund a specific amount against an order ID. The agent runs refund_payment and credits the consumer, confirming the partial refund amount and transaction reference.
How do I check the system limits with the `get_afterpay_config` tool? +
The get_afterpay_config tool returns your merchant's minimum and maximum order limits. This data is vital for ensuring any transaction you try to create via create_checkout adheres to your account's rules.
What happens if a payment fails, and how do I check the status using `get_payment_details`? +
The get_payment_details tool gives you the full financial status, including failure reasons and settlement info. You can use this to diagnose why a payment didn't capture.
Do I need special permissions to run `refund_payment`? +
Yes, you must verify the remaining balance before refunding. The refund_payment tool requires confirmation that the consumer still has a balance to be credited against the captured order.
How do I audit historical records using the `list_payments` tool? +
The list_payments tool retrieves all historical BNPL transactions and authorizations securely. This allows you to build a complete audit trail of your account activity.
How do I find my Afterpay Merchant credentials? +
Log in to your Afterpay Merchant Portal, go to Settings > API. You can generate and retrieve your Merchant ID and Secret Key there. Make sure to choose the correct region (US, AU, UK).
Can I process a partial refund via the agent? +
Yes! Use the refund_payment tool and provide the orderId and the specific amount. Your agent will submit the partial refund request to Afterpay for processing.
What is the difference between Capture and Auth? +
'Capture' finalizes the payment immediately. 'Auth' (Authorization) holds the funds on the customer's account, and you must call the capture tool later (usually when shipping) to finalize the transaction.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
BCB Juros — Selic, CDI e Expectativas Focus
Brazilian interest rates: Selic target rate (COPOM decisions), daily effective Selic rate, CDI (interbank deposit certificate rate), and Focus Survey market expectations for future Selic rates from Brazil's Central Bank.
Monzo Banking
Universal Monzo intelligence — check balances, accounts, and transactions via AI.
Braintree
Process and manage payments via Braintree GraphQL API — search transactions, manage customers, and issue refunds directly from any AI agent.
You might also like
Uber Eats
AI restaurant management: manage orders, menus, deliveries, and store operations via agents.
Highlight (Session Replay & UX)
Streamline observability by ingesting raw logs, OTLP logs, and OTLP traces directly into Highlight for session replay and UX monitoring.
HeyGen
Automate AI video generation via HeyGen — manage avatars, videos, and templates directly from any AI agent.