Claude Airwallex Developer connectorWhat Claude can do in your Airwallex Developer account.
The Claude Airwallex Developer connector exposes 12 tools. 8 read docs or sandbox data, 4 create or simulate test activity. Below: what Claude does in the sandbox, why it never touches real money, and what Airwallex asks you to check.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your developers
This connector is built for teams integrating Airwallex, not for running finances. Claude reads Airwallex's documentation and API references while it helps you, then creates test transfers, payment links or simulated events in the sandbox, a test copy of an account with no real money.
Answers grounded in current docs. search_public_docs and read_integration_best_practices pull Airwallex's own material into the chat, which Airwallex says reduces outdated or wrong code without removing the need to review it.
Test resources without leaving the chat. create_transfer and create_payment_link set up objects in the sandbox for your code to work against.
Rehearse the awkward cases. simulate_create_deposit funds a test account and simulate_transfer_result plays out a transfer outcome, so you see how your integration behaves before customers do.
What it will not do: touch production. Airwallex is explicit that these tools run in the sandbox only; for reading live balances or creating real beneficiaries it points to a different product. Nothing runs by itself either, and code Claude suggests still has to be reviewed and tested. For event-driven jobs on a live account, an automation tool fits better; the Integrations hub gathers that side.
The vocabulary in one minute
Six words you will meet while plugging Airwallex Developer in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Given once per person, revocable anytime.
- Approval
- The confirmation Claude waits for before it finishes an action that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Airwallex.
- Sandbox
- A test copy of an Airwallex account, with fake money and no real customers, where developers try an integration before going live.
Connect Airwallex Developer to Claude in three steps
- 01
Find Airwallex Developer in Claude
In Claude's settings, open Customize, then Connectors, and look for Airwallex Developer in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Airwallex in the window Airwallex opens itself. If the link breaks later on, use Disconnect and connect again.
- 03
Read the authorization screen
Go through Airwallex's consent screen before approving. It belongs to the service, not to Claude, and it lists what the access covers. You can take that access back later from the Airwallex side.
The 12 Claude Airwallex Developer connector tools, sorted by what they do
Airwallex Developer gives Claude 12 tools: 8 that read your account, 4 that change something in it.
Two groups: what Claude reads, and what it creates or simulates. Everything happens in the sandbox. Names stay exactly as Claude shows them.
- 8 read
- 4 write
What Claude reads (8)
8 toolsEight tools that read Airwallex docs or sandbox data without touching them.
list_transfers
Airwallex classes this one among the sandbox reads its developer connector runs, and stops there: its page never says what this particular tool returns.
list_beneficiaries
Part of the sandbox reads Airwallex mentions as a group. The publisher gives no line of its own for this tool, so this page does not say which objects it reads.
get_fx_quote
Airwallex's documentation files this tool under the reads run against the sandbox, without a sentence on its inputs or its output.
list_global_accounts
One more read on the sandbox account, going by Airwallex's description of the family. Which records it covers is not published, and a tool name is not enough to say.
get_balances
Airwallex lists sandbox reads as a capability of this connector but does not break them down, and this tool is one of them.
list_payment_links
Airwallex's page covers this tool only through the sandbox reads it describes collectively; no text of its own says what it lists or fetches.
search_public_docs
Searches Airwallex's public documentation and API references so Claude answers from the current material rather than from memory. It is part of the documentation tools that also exist in Airwallex's separate docs-only server.
read_integration_best_practices
Pulls Airwallex's written guidance on building an integration into the conversation, one of the documentation tools of this connector.
What Claude changes (4)
4 toolsFour tools that create or simulate activity, in the sandbox only. No specific confirmation is documented for them.
create_transfer
Approval: see the ruleCreates a transfer inside the sandbox, one of the test resources Airwallex says the developer connector can set up.
simulate_transfer_result
Approval: see the ruleSimulates what happens to a transfer in the sandbox, part of the event simulation Airwallex describes for testing.
simulate_create_deposit
Approval: see the ruleSimulates an incoming deposit on the sandbox account, one of the events Airwallex lets you fake while testing.
create_payment_link
Approval: see the ruleSets up a payment link inside the sandbox, one of the test resources the developer connector can create.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the conversation, when it matters.
Airwallex does not describe any confirmation of its own for the four sandbox tools, so the default rule is what covers them. On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time, and they can cap what a connector may do for the whole organization, keeping reads open and closing writes. That setting binds everyone. And Claude works with the sandbox access you granted, nothing more.
Which plans this is available on
None of the 819 sheets in the official directory shows availability per plan. Connector by connector, the answer is published nowhere: a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can sign in. For the current state, the Airwallex Developer sheet in the official directory is the only place that shows it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a payment arrives or a transfer settles.
Only the publisher documents this connector: no Claude help article covers it, and Airwallex describes its tools by family rather than one by one, so six notes above only say that a tool is a sandbox read, nothing more. The tool list is an observed floor, not a promise. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee their behavior. For a connector that works on live records instead, see the Claude airtable connector.
Need help connecting Airwallex Developer to Claude?
A person reads every message.
