Skip to content

t1k:business:airwallex

FieldValue
Modulebase
Version0.12.1
Effortlow
Tools—

Keywords: account balance, airwallex, balance, banking, beneficiaries, beneficiary, card, cashflow, client payment, company card, contract to billing, conversion, foreign exchange, fx, global account, hk entity bank, invoice, issue card, money out, multi-currency, payables, payee, payment received, payout, receivables, reconcile, statement, transactions, transfer

/t1k:business:airwallex
balance | transactions [account] | receivables | payables | beneficiaries | cards | fx-rates | reconcile <amount/client> | invoice-from <contract.md> | <natural-language finance query>

Read and operate the Airwallex business account from Claude Code through the official Airwallex AgentOS MCP server. Airwallex is a common HK-entity business bank — this skill is the bridge between contracts/finance work and the live account: pull real balances, reconcile incoming client payments against invoices, review cashflow, and manage beneficiaries and cards. Pairs with [[t1k:business:pandadoc-esign]] (signing) and t1k:business:finance (modeling/reporting over the numbers this skill pulls).

invoice issued → client pays → airwallex: read transactions → reconcile → finance report
contract (.md) → airwallex: contract-to-billing → invoice + billing terms

Verified surface (observed against a live production account)

Section titled “Verified surface (observed against a live production account)”
  • ~60 tools surface as mcp__airwallex__* once connected. Reads: get_account_balances, list_balance_history, list_global_accounts, list_global_account_transactions, list_transfers, list_fx_conversions, get_fx_rate, list_beneficiaries, list_cards / list_cardholders, list_spend_bills / list_spend_vendors, list_payment_intents / list_refunds, billing list_*. Non-money-out writes: beneficiaries, cards, payment links, billing/invoices. (Names are discovered per session — see the tool-names gotcha — treat this list as a map, not a contract.)
  • Money-out was refused server-side in production — the server itself rejected transfers, payment capture, FX conversion execution, and refunds/payouts, not merely “disabled by default”. Do not rely on that as the only guard: the HARD GATE below still binds, and re-verify on your own account before assuming the door is locked.
  • Keep the mapping of your wallet currencies and global accounts to your accounting files in your own repo docs, not in this skill.

⚠️ This is LIVE PRODUCTION financial data

Section titled “⚠️ This is LIVE PRODUCTION financial data”

The AgentOS MCP authenticates by OAuth against the production Airwallex account. Everything it reads is real money and real counterparties. Two consequences:

  1. Never quote raw account numbers, full card PANs, or beneficiary bank details in chat beyond what the user asked for — treat output like the secrets they are (see rules/security.md).
  2. Money-out is gated (see HARD GATE below). Reading is safe; moving money is not.

Only the AgentOS MCP (row 1) is registered for live account operations. The other two are documented here so you know what you’re not talking to.

ConnectorEndpointScopeUse for live ops?
AgentOS MCP ⭐https://mcp.airwallex.com/mcpProduction: read account + non-money-out writes✅
Developer MCPhttps://mcp-demo.airwallex.com/developerSandbox + docs (coding help only)❌
Docs MCP(docs-only, no auth)Documentation lookup❌
  1. Register the airwallex MCP server in your project .mcp.json (https://mcp.airwallex.com/mcp, HTTP transport).
  2. Authenticate once: run /mcp, select airwallex, complete the browser OAuth login with your production Airwallex account. Status must read connected before any operation below.
  3. Tools surface as mcp__airwallex__* and are deferred — load them first with ToolSearch(query="airwallex"). The exact tool names appear only after step 2; this skill documents operations by capability, then you bind to whatever tools the server actually exposes.

Grouped by safety tier. Read first; write second; move-money last (and gated).

OperationWhat it does
BalancesQuery multi-currency balances across cash / yield / credit account types.
TransactionsList/inspect account transactions for an account + date range.
Receivables / payablesUnderstand cashflow — what’s owed to you vs what you owe.
StatementsPull statement data for a period (reconciliation, finance reports).
FX rates / conversion optionsGet current FX options to prep a payrun (read-only quote, not execution).
BeneficiariesList existing payees and their details.
CardsList company cards and their state.

Write — non-money-out (allowed, but confirm first)

Section titled “Write — non-money-out (allowed, but confirm first)”
OperationWhat it does
Create beneficiaryAdd a new payee. Enables a future payout but does not move money.
Issue / provision cardCreate a company card for business spend.
Contract-to-billingTurn a signed contract into billing terms + a customer invoice.

These don’t move money, but they create real records on the production account. Show the user what you’re about to create and get a yes before writing.

Flow (all non-money-out writes):

create_billing_product → create_billing_customer → create_billing_invoice (DRAFT) → add_billing_invoice_line_items → STOP, show the user the draft → finalize_billing_invoice.

  • finalize is IRREVERSIBLE — once finalized the invoice is issued; it can only be voided, never edited. Never finalize without explicit per-invoice user approval; always build and show the DRAFT first.
  • Default collection_method: OUT_OF_BAND when clients pay by bank transfer into your global accounts: the Airwallex invoice is then just the billing document, and you mark_billing_invoice_as_paid once the deposit shows in the balance ledger. Use CHARGE_ON_CHECKOUT only when you deliberately want the client to pay through Airwallex’s hosted page (a new payment rail, may incur fees).
  • Pick one invoicing channel per invoice. If invoices of record are issued elsewhere (e-sign tool, document system), an Airwallex Billing invoice is a DIFFERENT document — do not double-invoice a client across both.
  • create_billing_customer: never fabricate an email or phone number — omit them unless the user provides them.

Money-out (HARD GATE — disabled by default)

Section titled “Money-out (HARD GATE — disabled by default)”
⛔ **NEVER initiate a money-out action without the user's explicit, per-action approval.** Money-out = **transfers, FX conversions, payouts, bill payments** — anything that debits the account. Airwallex itself ships these **disabled by default** in AgentOS; do not attempt to enable or route around that. Before any such action you MUST: (1) state the exact amount, currency, source account, and destination beneficiary; (2) get an explicit "yes, send " — no standing approval, no "they said pay earlier", no inferred intent; (3) if anything is ambiguous, STOP and ask via `AskUserQuestion`. When in doubt, leave it un-sent and report. This mirrors the per-send discipline already enforced for PandaDoc.

✅ No automated interceptor enforces this gate. Unlike the PandaDoc per-send discipline, the money-out rule below is carried by this skill body alone: it binds whoever is reading this file, and nothing else. There is no PreToolUse hook matching mcp__airwallex__* in this kit or in core — an earlier revision of this section claimed one named airwallex-payout-gate, which was never shipped (theonekit-business#33), and a reader who trusted it could have taken a risk believing a mechanical guard would stop the call. Airwallex’s own default-off on money-out actions is the only backstop that exists. Treat every money-out call as unguarded.

Only the read/reconcile half of this skill is cheap-tier work; every money-moving operation stays behind the HARD GATE above (routing SSOT: rules/orchestration-rules.md § “Task-Type → Agent Routing”):

StepAgent
Pull balances, transaction lists, receivables/payables or statements for a stated account + date range and report the figurest1k-fact-fetcher
Reconcile an incoming client payment — match the incoming credit to the invoice, confirm received, update the client tracker — against a stated invoicet1k-data-verifier
Any money-out operation (transfer, FX conversion, payout, bill payment)never delegated — stays gated behind the HARD GATE above; per-action explicit human approval required in every case
Non-money-out writes (create beneficiary, issue card, contract-to-billing)stay on a reasoning tier — they create real production records and need user confirmation

Cheap-tier delegation ends at “this payment is reconciled against this invoice.” Sending, converting, or paying money is a human decision and is never delegated.

  • Reconcile a client payment — invoice issued → read transactions → match incoming credit to the invoice → confirm received → update the client tracker / deal status. Pairs with t1k:business:finance.
  • Cashflow snapshot — balances + receivables + payables → hand the numbers to t1k:business:finance for runway/burn or an investor update.
  • Beneficiary setup before a payout — create beneficiary (non-money-out) now; the actual payout stays gated until you explicitly approve it later.
  • OAuth, not API keys. No Airwallex credentials should live in the repo. Auth is the interactive /mcp browser flow; nothing to gitignore.

Account data is live financial data. Do not echo full account/card/beneficiary identifiers into chat beyond the user’s request; never write them into synced data-room files. Per rules/security.md and the skill-security boilerplate.