Sokin Hooks Licensed Payment Rails to MCP — AI Preps, Humans Confirm

A junior who fills the payment form is useful. A junior who hits send without you is a lawsuit. Sokin just hired the first kind through MCP.

On 14 September 2026 (PR Newswire; company news page), Sokin released a Model Context Protocol connector that plugs its licensed payment infrastructure into customers’ AI tools — ChatGPT, Claude, Gemini, Perplexity and other compatible clients. The agent can pull live balances, FX quotes, and payment status, and it can prepare a beneficiary, a currency exchange, or a payment instruction. Every instruction is presented for customer confirmation. Existing Sokin approval rules still apply before settlement.

The mechanism

MCP is the plug. The product is write-prep on licensed rails, not another read-only “how much is in the wallet” toy.

What an authorized user’s agent can do, per Sokin:

1. Prepare a beneficiary, FX between supported wallets, or a single payment then show the full instruction for confirm.
2. Return wallet balances and transaction activity across corporates the user can access.
3. Fetch a current FX quote between supported Sokin wallets.
4. Find or validate beneficiary details against route requirements.
5. Return payment status and funding details for a wallet.

Pete Daunton (CSO) draws the line the desk cares about: a read-only MCP is a search bar with more personality. Sokin’s connector reaches the tools that create beneficiaries, quote FX, and prepare payments. Settlement still waits on a human (and on whatever dual-control the corporate already configured).

Underneath: Sokin says licenses across 36 countries, money movement to 170+ countries in 70+ currencies, own settlement infrastructure. A prepared instruction settles on rails Sokin owns and is licensed to operate — fiat/cross-border AP context, not a new L1. In testing they claim 10 multi-currency invoices and treasury moves in under 10 minutes; that is a vendor demo number, not a production SLA.

What the numbers mean

Ten invoices in ten minutes is a stopwatch on a pilot, not proof your AP team is done. Thirty-six licences and 170 corridors are the real so-what: the agent is not inventing a crypto bridge; it is queuing work on regulated rails that already exist. Compare custody patterns:

• Hedera hosted MCP — agent drafts ledger bytes; wallet presses send (crypto propose-vs-spend).
• Coinbase / Binance agent products — trade inside a ring-fenced sub-account; external withdraw cut.
• Sokin MCP — agent drafts payment/FX/beneficiary on licensed fiat rails; human + approval matrix still settle.

Same shape, different asset. That is why it belongs on an AIcrypto desk even without a token: the control pattern is the story the operators are copying.

The operator lesson

If your finance team already lives in Claude or ChatGPT, ask whether the connector is read-only or prepare-and-confirm before you celebrate “AI treasury.” Wire Sokin (or anything like it) with the same paranoia you use for a new AP clerk: least privilege on which corporates the agent can see, dual control left on, no skipping beneficiary checks because the model sounded confident.

Do not confuse this with a crypto wallet MCP that signs locally with no confirm UI. Sokin’s published flow keeps confirmation and existing approval rules in the path. That is the feature. Lose it and you have automation theater with a licence number on the letterhead.

Sources

• Sokin news, “Sokin launches MCP connector…,” (company page; body dateline Aug 14 / PR dated Sep 14) https://sokin.com/news/sokin-launches-mcp-connector-customers-ai-can-now-line-up-payments-in-minutes
• PR Newswire, same title, 14 September 2026 — https://www.prnewswire.com/news-releases/sokin-launches-mcp-connector-customers-ai-can-now-line-up-payments-in-minutes-302877439.html
• Sokin MCP — https://sokin.com/mcp
• Related CW: Hedera MCP wallet-sign; Coinbase for Agents; Binance Agent OS