---
title: "NexPay MCP server — Cross-border tuition payments for AI agents"
description: "Connect Claude, ChatGPT, and any MCP-aware AI assistant to NexPay. Search students, draft cross-border tuition payments, check FX, and track settlements — in natural language, with human authorisation."
lastModified: "2026-06-02"
lang: "en"
url: https://nexpay.com.au/mcp
---
## Site navigation

- For businesses
  - [For ed. agents](/for-education-agents.md)
  - [For schools & colleges](/for-schools.md)
  - [For universities](/for-universities.md)
  - [For accommodation](/for-accommodation.md)
  - [Why NexPay?](/about.md)
  - [Pricing](/pricing.md)
  - [AI automation](/payments-ai-automation.md)
- [For students & parents](/for-students-and-parents.md)
- Help & resources
  - [Training](/training.md)
  - [Blog](/blog.md)
  - [Events](/events.md)
  - [Zapier integration](/zapier.md)
  - [Claude & ChatGPT](/mcp.md) — Claude & ChatGPT integration
- [Contact](/contact-us.md)
- [Login](https://portal.nexpay.com.au/login)

# NexPay MCP server — Cross-border tuition payments for AI agents

> Your team can ask their AI assistant — in plain English — to search students, quote FX, draft tuition payments, and track settlements. The assistant prepares the work; a human still confirms before any payment runs.

**Connect Claude or ChatGPT to your payments.**

_Featured assistants:_ Claude + ChatGPT

- [Request alpha access](/contact-us.md)
- [Read the MCP spec](https://modelcontextprotocol.io)

**Example conversation — Your AI assistant of choice · NexPay tools loaded.** _Illustrative; names, amounts and transactions are fictional._

**You:** Pay the deposit for Camila Soares — University of Sydney, AUD 14,500, due Friday.

**Assistant:** Found her. **Camila Soares** · payer is her mother Mariana in São Paulo. Today's BRL→AUD lands the all-in at **BRL 50,182**.

_Tools the assistant called:_
  - `nexpay.student_search` — matched 1 student
  - `nexpay.fx_rate_get` — BRL → AUD · indicative 0.2889

**Assistant:** Quote locked and payment drafted — **AUD 14,500 → University of Sydney**, unconfirmed. Reply **confirm** to release it into NexPay's processing pipeline, or open the dashboard to review first.

_Tools the assistant called:_
  - `nexpay.quote_create` — quote valid 30m
  - `nexpay.payment_create` — payment created, unconfirmed

_Anthropic and OpenAI do not endorse, sponsor, or partner with NexPay. All trademarks belong to their respective owners._

## Connect Claude or ChatGPT in a couple of minutes.

Point your assistant at the NexPay MCP endpoint, sign in with a scoped API key, and your team can start asking it to look up students, quote FX, and draft payments today.

### Claude — Anthropic

Works with Claude Desktop, Claude in the browser, Claude Code, and anything built on Anthropic's MCP support. Anthropic authored the protocol — the experience is first-class.

- [Learn more about Claude](https://claude.com/blog/claude-code-remote-mcp)

### ChatGPT — OpenAI

Works with the ChatGPT desktop and web apps, custom GPTs, and the OpenAI Agents SDK — all of which gained MCP client support through 2025.

- [Learn more about ChatGPT](https://platform.openai.com/docs/mcp)

### And any other MCP-compliant client
- [Cursor](https://www.cursor.com)
- [Windsurf](https://windsurf.com)
- [Zed](https://zed.dev)
- Block's Goose
- Continue.dev
- Custom agents (TS · Python · Kotlin · Swift SDKs)

_MCP is an open protocol; client names are nominative use only. NexPay does not endorse, partner with, or co-market any of the clients listed above. Brand names and marks belong to their respective owners. If your assistant speaks MCP, it can speak to NexPay._

## Conversation instead of clicks.

Your team asks in plain language instead of clicking through the dashboard. The assistant blends NexPay with everything else it has access to — your CRM, email, calendar, codebase — plus the model's own reasoning, all in one answer. The cards below are illustrative examples.

### Prompt — Education agent

> Show me every payment on hold right now and what each one is waiting for.

_Tools the assistant reaches for:_
- `payment_list(status: "on_hold")`
- `payment_get(id: ...)`

_What the assistant returns:_
**2 payments on hold**
- **Camila Soares → University of Sydney** — AUD 14,500 · created 2 days ago · _Awaiting passport_
- **Mateo Rodríguez → Trinity College Dublin** — EUR 12,200 · created 4 days ago · _KYC review_

### Prompt — Education agent

> Which of my students haven't paid yet for the next intake?

_Tools the assistant reaches for:_
- `student_list(limit: 100)`
- `payment_list(status: "pending")`

_What the assistant returns:_
**3 students with tuition outstanding · Sep 2026**
- **Sofía Hernández — RMIT University** — AUD 16,800 outstanding · _No payment yet_
- **Lucas Pereira — University of Auckland** — NZD 22,400 outstanding · _No payment yet_
- **Daniel Vega — University College Dublin** — EUR 13,500 outstanding · _Partial · EUR 4,000 paid_

### Prompt — Finance

> How much did we process last month, broken down by destination country?

_Tools the assistant reaches for:_
- `payment_list(status: "settled", from: "...", to: "...")`
- `payment_get(id: ...)`

_What the assistant returns:_
**Settled · last 30 days**
- **AUD 2.42M** — Australia · 124 payments
- **AUD 689k** — Ireland · 38 payments
- **AUD 318k** — New Zealand · 19 payments

### Prompt — Education agent

> Quote AUD 18,500 for Joaquín to University of Auckland — what's the all-in in COP today?

_Tools the assistant reaches for:_
- `student_search(query: "Joaquín")`
- `fx_rate_get(from: "COP", to: "AUD", amount: 18500)`
- `quote_create(from: "COP", to: "AUD", ...)`

_What the assistant returns:_
**COP → AUD · all-in**
- AUD 18,500 → COP 51,294,300
- rate 2,772.66 · valid 30 minutes

### Prompt — Education agent

> Pull up Camila's payment history.

_Tools the assistant reaches for:_
- `student_search(query: "Camila")`
- `payment_list(student: ..., limit: 20)`

_What the assistant returns:_
**Camila Soares · 3 payments**
- **University of Sydney · Tuition deposit** — AUD 14,500 · 2 days ago · _On hold_
- **University of Sydney · Tuition balance** — AUD 12,800 · Mar 2026 · _Settled_
- **Sydney Student Accommodation** — AUD 4,200 · Feb 2026 · _Settled_

### Prompt — Operations

> Cancel the unconfirmed payment I created for Mateo earlier today — wrong school.

_Tools the assistant reaches for:_
- `student_search(query: "Mateo")`
- `payment_list(student: ..., status: "unconfirmed")`
- `payment_cancel(id: ...)`

_What the assistant returns:_ Cancelled. Payment pi_3kQ9x2mB will not be processed. Funds were never debited.

## AI does the typing. Humans still authorise.

Money moving in cross-border education is regulated work. NexPay's MCP server is designed so an assistant can do the heavy lifting — searches, quotes, drafts — while every write tool is clearly marked and prompts for human approval before it runs.

- **01 · Two-step writes.** — Neither MCP write moves funds. payment_create produces an unconfirmed payment; payment_confirm changes its state so it can enter NexPay's processing pipeline. NexPay's compliance, treasury, and settlement controls run on the platform side before any money actually moves. Most MCP clients prompt for human approval before invoking either call, and you can require confirmation only via the dashboard by scoping the key.
- **02 · Scoped API keys.** — Each MCP connection authenticates with a NexPay API key you mint and can revoke. Keys can be scoped read-only, scoped to a sub-account, or limited to specific tools — so you can disable writes entirely if your agent does not need them.
- **03 · Audit trail by default.** — Every tool call is logged with the agent identity, the prompt that triggered it, the tool name, and the arguments. The regulated record of every transaction stays with NexPay regardless of how the action was initiated.
- **04 · Compliance does not delegate to LLMs.** — Sanctions screening, AML, beneficiary review, KYC — all run on the NexPay side, unchanged. An agent cannot route around them; it can only request actions that NexPay then evaluates.
- **05 · No card or full bank data through the model.** — Card numbers are never stored by NexPay and therefore never reach the MCP server. Bank account fields are only exposed in payee tools the API key explicitly authorises.

_Held by NexPay Pty Ltd · AFSL 560782 (ASIC) · AUSTRAC remittance registered · Group entities also licensed by the FCA (UK) and registered with FINTRAC (CA)._

## The licences behind the audit trail.

AFSL 560782 (ASIC), AUSTRAC remittance registration, FCA Authorised Payment Institution in the UK, FINTRAC MSB in Canada. Every credential is independently verifiable on its public register.

- [Verify us, by jurisdiction](/trust.md)

## MCP for your questions Qualy for your automations.

MCP is great for letting your assistant search, quote, draft, and inspect payments. For the deeper workflow — reconciliation, commission splits, escalation, partner payouts — **Qualy**, our automation partner, is purpose-built for international education.

- **100%** — auto-reconciled
- **90s** — avg. payment
- **20x** — faster collection
- **0** — commission disputes

- [See how it works](/payments-ai-automation.md)

## Frequently asked questions

What the NexPay MCP server is, what it does today, and where it sits alongside our REST API and Zapier integration.

### What is MCP and why does NexPay support it?

MCP — the Model Context Protocol — is an open standard published by Anthropic in November 2024 for connecting AI assistants to external tools and data. By implementing an MCP server, NexPay lets any MCP-aware assistant (Claude, ChatGPT, Cursor, Windsurf, Zed, Goose, custom agents) interact with the payment platform through typed tool calls — without anyone writing a bespoke integration. NexPay supports it because cross-border tuition is high-friction back-office work and assistants are well suited to handling it under human authorisation.

### Is the NexPay MCP server available today?

It is in private alpha. The tool manifest, the auth model, and the safety design described on this page are implemented — but we are only enabling access for a small number of design partners while we observe how real agents use it. Request alpha access through the form on this page and tell us which assistant you would point at it.

### Which AI assistants can use it?

Any MCP-compliant client. That includes Claude (Anthropic), ChatGPT (OpenAI), Cursor, Windsurf, Zed, Block's Goose, Continue.dev, and any custom agent built with the official MCP SDKs (TypeScript, Python, Kotlin, Swift). The same NexPay endpoint and the same API-key auth flow — only the host changes.

### Can an AI agent move money on its own?

No. Neither MCP write tool moves money. payment_create produces an unconfirmed payment and payment_confirm changes its state so the regulated payment engine can pick it up — but the actual movement of funds is controlled by NexPay's compliance, treasury, and settlement layer, which runs on the platform side regardless of how the payment was created. Most MCP clients also prompt for explicit user approval before invoking any write tool, and you can scope your API key to read-only to disable writes entirely.

### How is this different from the NexPay REST API?

Both run on the same NexPay endpoints. The REST API is for engineering teams who want to ship a payment flow inside their own product. The MCP server is for teams whose interface is already an AI assistant — they want their agent to read and write into NexPay without writing or maintaining glue code. Many design partners use both: the REST API where the product owns the flow, MCP where the assistant does.

### How is this different from the NexPay Zapier integration?

Zapier is point-and-click no-code automation between NexPay and 7,000+ apps — event-driven, polling-based, deterministic. MCP is conversational tool-use by an AI assistant — natural language in, structured tool calls out, with the model deciding which tools to invoke in what order. Zapier is the right tool for a fixed workflow you can describe in advance; MCP is the right tool for the long tail of one-off questions and instructions a human gives an assistant.

### How are API keys, auth, and scopes handled?

Each MCP connection presents a NexPay API key you mint and can revoke at any time. Keys can be scoped read-only, scoped to a sub-account, or restricted to specific tool names. The MCP server validates the scope on every tool call before invoking the underlying NexPay API. There is no separate auth system — it reuses the same authenticated API surface as the dashboard.

### What about sanctions, AML, KYC, and beneficiary screening?

Unchanged. Every guardrail that runs on the NexPay side today runs in front of every MCP tool call. An agent cannot route around them — it can only request actions that NexPay then evaluates. NexPay Pty Ltd holds Australian Financial Services Licence 560782 and is registered with AUSTRAC as a remittance service provider; group entities are also licensed by the FCA (UK) and registered with FINTRAC (CA).

### Does the MCP server cost anything extra?

No additional NexPay fee. The MCP server is included with any NexPay account, just like the REST API and Zapier integration. The cost of the AI assistant itself sits with whoever provides it — Anthropic, OpenAI, or your own model deployment.

### How do I get on the alpha?

Use the Request alpha access button on this page. Tell us which assistant you want to point at it, what role on your team will use it most, and any specific workflows you are trying to support. We are deliberately keeping the cohort small so we can pair-debug with each design partner.

- [Talk to our team](/contact-us.md)

## Prefer the REST API? Our engineers ship it with you.

If your team owns the product surface and you want full control over the payment flow, the NexPay REST API is the right path — and a NexPay engineer pairs with you from first call to production. Average time to production: two weeks.

- [Visit the developer hub](/api.md)

## Want point-and-click automation instead? Zapier connects NexPay to 7,000+ apps.

For fixed, deterministic workflows — close a HubSpot deal → draft a NexPay payment, settle a payment → append a row in Google Sheets — Zapier is the simplest tool for the job. No assistant, no glue code, no engineer.

- [See Zapier integration](/zapier.md)

## AI

**Audience:** education agents, school operations teams, and developers building AI assistants that need to read and write into the NexPay payment platform — among the first MCP servers from a regulated cross-border payments provider focused on international education.

### Intents

- nexpay mcp server
- claude payment integration
- chatgpt payment integration
- openai mcp server payments
- anthropic mcp server payments
- international education ai agent
- tuition payments ai assistant
- mcp server for payments
- mcp server for fintech
- agent native payments platform
- llm tool use payments
- nexpay model context protocol
- claude tools cross-border payments
- openai function calling payments
- cursor mcp payments
- windsurf mcp payments
- zed mcp payments
- automate tuition payments with ai
- ai agent payment tracking latam

## More on NexPay

**Platform**

- [For students & parents](/for-students-and-parents.md)
- [For ed. agents](/for-education-agents.md)
- [For universities](/for-universities.md)
- [For schools](/for-schools.md)
- [For accommodation](/for-accommodation.md)
- [AI automation](/payments-ai-automation.md)
- [Pricing](/pricing.md)

**Help & resources**

- [Training](/training.md)
- [Contact](/contact-us.md)
- [Developers](/api.md)
- [Zapier integration](/zapier.md)
- [Claude & ChatGPT](/mcp.md) — Claude & ChatGPT integration

**Company**

- [About](/about.md) — About NexPay
- [Jobs](/about.md#jobs)
- [Blog](/blog.md)
- [Media](/media.md)
- [Events](/events.md)

**Trust & locations**

- [Trust & Regulatory](/trust.md)
- [Our offices](/locations.md)

**Legal**

- [Terms and Conditions](/terms-and-conditions/)
- [Privacy policy](/privacy-policy/)
- [Cookie Policy](/cookie-policy/)
- [Complaints Policy](/complaints-policy/)
- [Financial Services Guide](/financial-services-guide/)
- [Product Disclosure Statement](/product-disclosure-statement/)
- [AML Policy](/aml-policy/)
- [Target Market Determination](/target-market-determination/)
- [Group Regulatory Disclosure](/group-regulatory-disclosure/)
- [Fees & FX Schedule](/fees-and-fx/)
- [Developer & API Terms](/developer-terms/)

## NexPay

NexPay Pty Ltd (ABN 56 153 910 984) holds Australian Financial Services Licence No. 560782 and is authorised to provide non-cash payment services to retail and wholesale clients in Australia.

- **Address:** Level 12, 64 York St, Sydney NSW 2000, Australia
- **Support:** [support@nexpay.com.au](mailto:support@nexpay.com.au)
- **Status:** [https://nexpay1.statuspage.io/](https://nexpay1.statuspage.io/)

**Follow NexPay**

- [LinkedIn](https://au.linkedin.com/company/nexpay)
- [Instagram](https://www.instagram.com/nexpayau/)
- [Facebook](https://www.facebook.com/NexPayAU)

© NexPay Pty Ltd