Sokin MCP - Technical Docs - Sokin Embedded API

The Sokin MCP server exposes the Sokin B2B API to AI agents over the Model
Context Protocol. This page is the reference catalogue: every tool, its
parameters, and the exact shape of what it returns.

It is not an install guide. For connecting a specific client, signing in, and
reaching a first successful call, see the companion page, Sokin MCP —
Setup and Usage Guide.

Server

Field	Value
Endpoint	`https://mcp.sokin.com/mcp`
Transport	Streamable HTTP
Protocol	JSON-RPC 2.0 (MCP)
Authentication	OAuth 2.1 + PKCE; the client identifies itself with a Client ID Metadata Document (CIMD)
Tools	26
Session model	Stateless HTTP: no session ID, and any request can reach any replica. One thing is remembered per user and client: whether it declared interactive-card support at `initialize` (kept 24 hours, refreshed by each `initialize`)

The endpoint serves live data from real corporate accounts, and some tools
move real money. The tool catalogue below is read directly from the tools
registered on this server.

Three transport details that surprise people:

Send initialize first. A tools/call with no prior initialize is
answered, and most tools behave the same either way. But initialize is
the only place your client can declare interactive-card support (MCP Apps,
the io.modelcontextprotocol/ui extension under capabilities.extensions),
and the server keeps that declaration for 24 hours per user and client,
refreshed by every initialize. With no declaration on record,
create_fx_quote and settle_fx_quote refuse every call, get_fx_quote
returns its no-quote fallback, and the payment tools use their plain-text
wording. A host that renders MCP Apps may still draw the cards, because
each card is attached to its tool rather than to a response branch; the FX
card's Get Quote is then refused (see get_fx_quote).

Responses arrive as SSE. Even a single, non-streaming call comes back
as a text/event-stream with the result in a data: event, not as a
plain JSON body.

Your Accept header must include both content types. Send
Accept: application/json, text/event-stream. Leave out the second value
and the server answers 406 Not Acceptable ("Client must accept both
application/json and text/event-stream").

Authentication

The server is an OAuth protected resource, not an authorization server: it
signs nobody in. The client signs the user in with Sokin's authorization
server and receives an access token issued for this server, which it sends
as a bearer token on every request. The server verifies that token, then
exchanges it on the user's behalf for the Sokin API token the tools need.
That API token never leaves the server, so a client never needs (and cannot
obtain) a Sokin API token of its own.

Discovery starts at this server and follows the standard well-known paths:

Endpoint	Purpose
`https://mcp.sokin.com/.well-known/oauth-protected-resource/mcp`	Protected-resource metadata (RFC 9728): the resource identifier, `https://mcp.sokin.com/mcp`, and the authorization server that issues its tokens, `https://auth.sokin.com/`
`https://auth.sokin.com/.well-known/oauth-authorization-server`	The authorization server's metadata: its `authorize` and `token` endpoints, and `client_id_metadata_document_supported: true`

An unauthenticated request to /mcp is answered 401 with a
WWW-Authenticate header whose resource_metadata points at the first
document. This server serves no authorization-server metadata of its own, and
no /authorize, /token or /register.

Client registration is by Client ID Metadata Document (CIMD). The
client's client_id is an HTTPS URL at which it publishes its own metadata
(name, redirect URIs). Sokin accepts the documents of the clients it
supports; Claude, Claude Code and ChatGPT are among them.

Dynamic Client Registration is not available. A client cannot register
itself on the fly, and a client whose CIMD Sokin has not registered cannot
sign in; to connect one, talk to your Sokin contact. The authorization
server's metadata still lists a registration_endpoint, but registration
there is switched off.

Use PKCE (S256).

Send the resource parameter (RFC 8707) as https://mcp.sokin.com/mcp.
The access token's aud includes that URL (it may be an array), and the
server rejects a token whose audience does not, including a Sokin API
token.

No scopes are required. Request offline_access to receive a refresh
token.

Access tokens last 15 minutes. Refresh tokens rotate on every use and
expire after 30 days, or after 15 days unused; the user then signs in again.

The first sign-in from each client shows a consent screen naming that
client. It is asked once per client, not once per session.

You cannot request a Sokin API token yourself, and you do not need one.
The server exchanges your token for one, on the user's behalf, whenever a
tool needs the API.

Requests to /mcp are additionally gated by Host and Origin checks (DNS
rebinding protection). They run after the token check, so a request with a
valid token but addressed to a host other than the advertised public one is
rejected with 421, and one carrying a disallowed Origin with 403. If
you see a 421, check the Host header before looking at your token.

Anatomy of a result

Every tool call returns a CallToolResult with three parts:

Part	Type	What it carries
`content`	array of text blocks	The model-facing rendering: a sentence or a markdown table. Always present, and always compact in every mode.
`structuredContent`	object, or absent	The machine-readable payload. This is the half the full-response opt-in widens. See the caveats below; it is not present on every result.
`isError`	boolean	Whether the call failed.

On a successful call both channels arrive together, and that duplication is
deliberate: content is what a model reads cheaply, structuredContent is
what your own code parses.

structuredContent is absent in two cases, and code that parses results
must handle both:

Every error result. A failure carries content and isError: true and
nothing else. Check isError before reaching into structuredContent, or
the first upstream failure your integration meets becomes a KeyError
rather than a handled error.

play_cheetah_dash, which returns a bare string and never goes
through the compact/full machinery at all.

Every other tool returns structuredContent on success.

An empty upstream field is left out, not sent as null. The Sokin API
drops unset fields from its responses, so a field this page documents as
"or null" that comes from the API is usually absent when it has no value.
Treat a missing key and null the same way. The explicit nulls are the
ones this server builds itself (for example idempotencyKey when a draft
failed validation).

A stray `message` field

Upstream envelopes also carry a message field, filled by the B2B API's own
response helpers with message or "Success.". It is almost always that
literal string, describes the HTTP exchange rather than your result, and is
never worth reading.

Some tools strip it before building structuredContent; some pass it
through unchanged. Tolerate it rather than assume a fixed key set:

Behaviour	Tools
Stripped	`list_corporates`, `list_beneficiaries`, `get_beneficiary`, `get_beneficiary_schema`, `validate_beneficiary`, `create_beneficiary`, `update_beneficiary`, `list_financial_institution_branches`, `validate_payment_instruction`
Passed through	`list_accounts`, `get_account`, `get_account_ledger`, `list_instructions`, `get_instruction`, `get_instruction_request`, `list_financial_institutions`
Not applicable, no upstream envelope	`get_fx_quote`, `create_fx_quote`, `create_payment_instruction`, `create_fx_payment_instruction`, `get_documentation_links`, `visualize`, `play_cheetah_dash`
Both, depending on the branch taken	`submit_payment_instruction`, `submit_fx_payment_instruction`, `settle_fx_quote`: stripped on a fresh submission, passed through on a replay that reports an existing payment's state

Where a tool strips it, opting into the full response brings it back. That
is noted per tool below wherever it is the only difference the opt-in makes.

Response modes: compact and full

By default structuredContent is compact: trimmed to the fields a
caller can actually act on, with internal bookkeeping removed. A client can
opt into the full raw B2B API payload instead.

Two independent triggers, combined with OR semantics. Use whichever your
framework lets you reach.

Trigger 1: the MCP _meta side channel.

{
  "jsonrpc": "2.0", "id": 1, "method": "tools/call",
  "params": {
    "name": "list_corporates",
    "arguments": {},
    "_meta": { "sokin.com/full-response": true }
  }
}

The check is a strict identity comparison against boolean true. A
stringified "true" is ignored. This fails closed on purpose, so a proxy
that coerces JSON types cannot silently opt you into the wider payload.

Trigger 2: an HTTP header.

Case-insensitive and whitespace-trimmed, but the value must be exactly
true; any other non-empty value is ignored. This path exists because
several agent frameworks (LangChain/LangGraph, CrewAI, Semantic Kernel) let
application code set custom HTTP headers on a request, but expose no way to
set _meta on an individual call, even though the MCP SDK beneath them
already supports it.

Neither trigger is a tool parameter, so the calling model can never opt
itself in; only your client code can.

Here is the same list_corporates call's structuredContent, compact by
default and widened when a client opts in (real values from this server's
own test suite):

Compact (default):

{
  "data": {
    "items": [
      {
        "corporateReference": "CORP-1",
        "corporateName": "Acme Ltd",
        "assignmentType": "direct"
      }
    ]
  }
}

Full (opted in via either trigger above):

{
  "data": {
    "items": [
      {
        "corporateReference": "CORP-1",
        "corporateName": "Acme Ltd",
        "assignmentType": "direct",
        "activeFrom": "2026-01-01T00:00:00Z",
        "features": { "paymentAcceptance": true }
      }
    ]
  }
}

content is identical either way: only structuredContent widens.

One more limit worth knowing: whether structuredContent itself reaches the
model at all is a host decision, not this server's. Some hosts (OpenAI's
Apps SDK among them) do surface it to the model. A client that opts in on
such a host is choosing to put the full payload into model context.

Errors

Every failure comes back with isError: true and no structuredContent
at all: only content and the flag. Branch on isError before parsing. Never string-match the
message text.

Class	Message shape	Cause
Reference not available (403/404)	`That reference is not available on this account. Check it against the value the corresponding list tool returned, and retry. If the reference is correct, this account may not have access to it.`	The reference does not exist, is malformed, belongs to another corporate, or this account lacks permission for it. All four render identically and carry no status code, deliberately: telling them apart would answer "does this reference exist elsewhere in Sokin". The middle sentence names the tool's own reference arguments and the list tool that produces each. Only `list_corporates` and `list_financial_institutions`, which take no reference, show the generic middle sentence. Exception: on a `404`, `validate_beneficiary`, `create_beneficiary` and `update_beneficiary` name what is missing instead (`Corporate not found` or a missing payee id; see their entries), while a `403` still gets this neutral text.
B2B API error (any other status)	`API error (400): <message from the API>`	The upstream Sokin API rejected the call for a stated, non-reference reason. The status and message are passed through as is — except that a message carrying the identity-provider tenant name, an internal principal id or a permission string is replaced with `no further detail available`.
Token exchange failed	`API error (503): Could not obtain an API token for this session, please try again`	Not the B2B API: the server could not exchange the client's token for a Sokin API token, because the authorization server was unreachable or refused. Retryable. The client's own token is never forwarded in its place.
Unexpected failure	`Something went wrong while processing that request. Please try again, and contact support if it keeps happening.`	Anything unanticipated: a malformed upstream response, a bug. Internal detail is deliberately not leaked.
Schema validation	Rejection from the MCP layer, before the tool body ever runs	A wrongly typed argument, or a value outside a closed `Literal` enum.
Tool-local validation	Usually `Error: <specific problem>`, but not reliably; see below	Per-tool argument checks: blank references, unsupported pagination parameters, malformed amounts. Listed per tool below.

Most tool-local validation messages start with Error: , but two do not:
visualize returns markdown must not be empty. and
list_financial_institution_branches returns

Unknown financial institution
id: '999'. Call list_financial_institutions to see valid ids.

That
inconsistency is exactly why the rule above is to branch on isError: no
prefix, and no substring, is a dependable signal across every tool.

A message starting with Error: is not on its own proof that isError is
true. create_fx_payment_instruction can return content that begins with
the literal word Error: (its quote-problem message) while isError stays
false: that is a reported finding from the validation dry run, not a tool
failure. No draft is registered on that branch (idempotencyKey is null),
but the quote it minted is real. Branching on the prefix instead of the flag
gets exactly this case backwards.

An upstream response that is structurally unusable is reported as a
synthesized 502 through the same channel rather than rendered as a false
success. validate_payment_instruction does this when a 200 arrives with
no verdict field; submit_payment_instruction,
submit_fx_payment_instruction and settle_fx_quote do it when a 202
arrives with no externalReference.

Pagination

Cursor-based, never page/offset. A paginated response carries:

{
  "data": [ "..." ],
  "pagination": {
    "nextToken": "eyJrIjoi...",
    "previousToken": null,
    "totalItems": 128,
    "hasMore": true
  }
}

When hasMore is true, pass nextToken back as the next_token argument.
The casing difference is not a typo and the two are not interchangeable:
nextToken is the field the API returns, and next_token is the parameter
this server's tools declare, so the value crosses from one convention to the
other. Every response field on this page is camelCase and every tool parameter
is snake_case, with one exception: the draft object the two create_*
payment tools return is the tool's own argument set, so its keys are
snake_case.

No tool here exposes a previous_token parameter, so previousToken is
informational only.

Tool	Pagination
`get_account_ledger`	Cursor: `limit`, `next_token`
`list_instructions`	Cursor: `limit`, `next_token`
`list_beneficiaries`	Cursor: `limit`, `next_token`
`list_financial_institution_branches`	Cursor: `limit`, `next_token`
`list_accounts`	Envelope present but inert: the upstream route hardcodes `hasMore: false` and accepts no pagination parameter at all, so this always returns everything in one call
`list_corporates`	None
`list_financial_institutions`	None; the upstream endpoint accepts no parameters at all

Tools

18 of the 26 tools are read-only (readOnlyHint: true) and move no money.
Eight are writes, and they are not equivalent — only three of the eight move
money:

Tool	Annotations	What it does
`create_fx_quote`	`readOnlyHint: false`, `destructiveHint: false`, `idempotentHint: false`	Mints a real, short-lived FX quote. Additive: it only ever creates, never mutates or removes, and it moves no money on its own
`create_fx_payment_instruction`	`readOnlyHint: false`, `destructiveHint: false`, `idempotentHint: false`	Prepares an FX payment for review. Mints a real quote on every preparing call (the same write as `create_fx_quote`); submits nothing and moves no money
`settle_fx_quote`	`readOnlyHint: false`, `destructiveHint: true`, `idempotentHint: true`	Executes a real FX conversion between two of the corporate's own currency accounts
`submit_payment_instruction`	`readOnlyHint: false`, `destructiveHint: true`, `idempotentHint: true`	Submits a prepared payment to a beneficiary
`submit_fx_payment_instruction`	`readOnlyHint: false`, `destructiveHint: true`, `idempotentHint: true`	Submits a prepared FX payment: converts and pays a beneficiary in one motion against a live quote
`validate_beneficiary`	`readOnlyHint: false`, `destructiveHint: false`, `idempotentHint: true`	Verifies payee details; its existing-payee mode persists refreshed validation statuses (convergent)
`create_beneficiary`	`readOnlyHint: false`, `destructiveHint: false`, `idempotentHint: false`	Creates a payee behind an emailed one-time code; a repeat call creates a second payee (no upstream dedupe)
`update_beneficiary`	`readOnlyHint: false`, `destructiveHint: true`, `idempotentHint: true`	Overwrites a payee's destination/identity details behind the same emailed code

Hosts prompt before running any destructive tool. Of the payment prepare
side, validate_payment_instruction and create_payment_instruction stay on
the read-only default: the first is a pure dry run, and the second prepares a
draft for a human to look at without touching any write endpoint (its draft
record is gate bookkeeping). create_fx_payment_instruction is a write
because it mints a real quote before preparing the draft; it still never
touches the fx-payment endpoint. The beneficiary writes use a different human-in-the-loop
than the payment pair: an emailed one-time code the model cannot forge (see
create_beneficiary).

That split describes today's tool set, not a permanent property of this
server. A tool added later can change it; each tool's own annotation line
below is the authority.

None of these money-moving flows is a single call. Each is a pair (or, for
FX quoting, a triple) joined by a server-side draft gate, and the shape is
worth understanding before integrating against any of them.

Card support and where the human control sits

The two payment pairs (create_payment_instruction/submit_payment_instruction
and create_fx_payment_instruction/submit_fx_payment_instruction) work
whether or not the session declared MCP Apps (SEP-1865) support at
initialize. The human control for a payment is not the review card but
approval in the Sokin portal: every corporate has an approval rule that holds
each instruction this server creates until someone approves it there (see
"What the gate does not guarantee" under settle_fx_quote for its limits,
which apply identically here). A plain-chat
create -> confirm in chat -> submit flow is therefore a supported path,
not a workaround.

Only create_fx_quote and settle_fx_quote refuse a session without
declared card support. That refusal is defence in depth behind portal
approval: it stops a session minting real quotes with no card to show them,
and keeps own-account settlement behind the card's review surface (see
settle_fx_quote's entry below).

The two create_* tools read the session's declared capability only to
choose which of two response texts to show, never to refuse; the submit_*
tools do not read it at all:

MCP UI declared: the create_* tool renders its review card and its
text says so ("awaiting the user's confirmation in the review widget").
The card's Approve click is meant to invoke the paired submit_* tool,
though the model holds the key too (see submit_payment_instruction).

Not declared, or unknown (the common case for a plain-chat client):
there is no card. The create_* tool's own content text spells the
idempotencyKey out in plain words -- structuredContent is not reliably
surfaced to the calling model, so the key has to travel where the model
can actually see it -- and instructs the calling model to read the draft
and fees back to the user, get their explicit approval in chat, and only
then call the paired submit_* tool itself with that key and
byte-identical arguments.

structuredContent does not change between these two branches: idempotencyKey
is present in both once validation passes. Only the content wording
changes, and both submit_* tools accept a direct call under either
branch -- there is no "widget-only" enforcement on the submit side.

Payments prepare in the conversation and commit from a review card (or, for
a non-UI client, from an explicit chat confirmation):

validate_payment_instruction and create_payment_instruction both persist
nothing upstream and move no money; the first is a dry run, the second
prepares a draft for a human to look at. Only submit_payment_instruction
commits, and it will only ever send a byte-identical copy of the draft that
was prepared, under a key the server minted itself. See its own entry for
what that gate does and does not guarantee.

create_fx_payment_instruction and submit_fx_payment_instruction follow a
similar prepare/review/approve/submit shape, with the same draft-gate
guarantees. create_fx_payment_instruction takes raw pricing inputs
(buy_currency, sell_currency, amount, fixed_side,
corporate_reference) and mints its own quote, via the same FX quote
adapter create_fx_quote uses, so no separate quote call comes first. The
minted quote's id travels inside the registered draft, which is why
submit_fx_payment_instruction takes quote_id: it has to match that same
draft. See both entries below.

FX quoting runs its whole lifecycle inside one card instead, because a
quote expires too quickly to survive a round trip through a conversation:

Both create_fx_quote and settle_fx_quote exist only to back that card's
own buttons, and both are refused outright for a client that has not
declared MCP UI support. See settle_fx_quote's entry for why, and for what
its gate does and does not guarantee.

`list_corporates`

List Corporates · read-only · touches an external system

Lists the corporates the authenticated user can access. This is the entry
point for most sessions: nearly every other tool needs a
corporateReference, and this is where one comes from. Takes no arguments.

Parameters: none.

content, one sentence: see the Example below.

structuredContent, envelope {"data": {"items": [...]}}, each item:

Field	Type	Description
`corporateReference`	string	The reference to pass to every other tool
`corporateName`	string	Display name
`assignmentType`	string	`direct` or `inherited`

Full response adds: activeFrom (an ISO-8601 timestamp nothing in this
server consumes) and features (an opaque corporate feature-flag object
passed through without being read). It also restores the envelope's
message field, which the compact response strips.

Example

Request

{"name": "list_corporates", "arguments": {}}

Reply

2 corporates: CORP-8842 — Northwind Trading Ltd (direct assignment); CORP-9110 — Northwind Logistics BV (inherited access).

Reply as data

{
  "data": {
    "items": [
      {"corporateReference": "CORP-8842", "corporateName": "Northwind Trading Ltd", "assignmentType": "direct"},
      {"corporateReference": "CORP-9110", "corporateName": "Northwind Logistics BV", "assignmentType": "inherited"}
    ]
  }
}

`list_accounts`

List Accounts · read-only · touches an external system

Lists all Corporate Currency Accounts (CCAs) for a corporate, with balances.

Parameter	Type	Required	Description
`corporate_reference`	string	yes	The `corporateReference` from `list_corporates`

content, one sentence: see the Example below.

availableBalance is nullable upstream: it is balance minus the
amount reserved by outstanding instructions, and it cannot be computed when
the caller lacks Instruction Read permission. The summary states that in
words rather than rendering an empty value.

Neither balance nor availableBalance includes Boost (Easy Access Boost
or Fixed Term Boost) deposits -- a Boost deposit moves money out of this
account's own ledger into a separate Boost product this server does not
expose at all. balance includes held funds, availableBalance excludes
them. The Sokin portal's "Total Funds" figure adds the corporate's Boost
total on top of balance; it is a portal figure, not part of this API, so
don't derive a Boost total from it. get_account_ledger shows the movement
itself: a Boost deposit is a boost_deposit entry with counterparty
Sokin Boost; money coming back from Boost -- an Easy Access withdrawal,
or a Fixed Term Boost reaching or leaving its term -- is a
boost_maturity_payout entry, which carries neither a counterparty nor a
description, so recognise it by the type alone.

structuredContent, envelope {"message": "Success.", "data": [...], "pagination": {...}}.
The pagination object is always present here but inert: nextToken and
previousToken are always null and hasMore is always false; the upstream
route accepts no pagination parameter at all. Each item:

Field	Type	Description
`corporateReference`	string	The corporate that owns this account
`corporateCurrencyAccountReference`	string	The account reference used by other tools
`currencyCode`	string	ISO 4217
`balance`	decimal	Current balance
`availableBalance`	decimal, or null	Balance minus outstanding instruction reservations; null when not computable

Full response adds: nothing. Compact is the identity of raw here; every
field is caller-actionable, so nothing is trimmed.

Example

Request

{"name": "list_accounts", "arguments": {"corporate_reference": "CORP-8842"}}

Reply

2 accounts for CORP-8842: CCA-1001 (GBP) — balance 48200.00, of which 47150.00 available; CCA-1002 (USD) — balance 12000.00, available balance not computable.

Reply as data

{
  "message": "Success.",
  "data": [
    {
      "corporateReference": "CORP-8842",
      "corporateCurrencyAccountReference": "CCA-1001",
      "currencyCode": "GBP",
      "balance": "48200.00",
      "availableBalance": "47150.00"
    },
    {
      "corporateReference": "CORP-8842",
      "corporateCurrencyAccountReference": "CCA-1002",
      "currencyCode": "USD",
      "balance": "12000.00",
      "availableBalance": null
    }
  ],
  "pagination": {"nextToken": null, "previousToken": null, "totalItems": 2, "hasMore": false}
}

`get_account`

Get Account · read-only · touches an external system

Full detail for one Corporate Currency Account, including the pay-in
details someone would use to fund it.

Parameter	Type	Required	Description
`account_reference`	string	yes	The corporate currency account reference

content, a sentence per funding route: see the Example below.

structuredContent, envelope {"message": "Success.", "data": {...}}:

Field	Type	Description
`externalReference`	string	The account reference
`currency`	string	ISO 4217
`currentBalance`	decimal	Current balance
`availableBalance`	decimal, or null	A computed value: `currentBalance` minus outstanding instruction reservations, null when not computable. The value it is computed from, `outstandingInstructionBalance`, is never itself serialized on the wire
`localAccountStatus`	string	Locality status, see the enums appendix
`internationalAccountStatus`	string	Locality status, see the enums appendix
`localPaymentDetails`	object, or null	Pay-in details for the local route
`internationalPaymentDetails`	array	Pay-in details for international routes; defaults to an empty list, may hold several options

Neither currentBalance nor availableBalance includes Boost (Easy
Access Boost or Fixed Term Boost) deposits -- a Boost deposit moves money
out of this account's own ledger into a separate Boost product this
server does not expose at all. currentBalance includes held funds,
availableBalance excludes them. The Sokin portal's "Total Funds" figure
adds the corporate's Boost total on top of currentBalance; it is a portal
figure, not part of this API, so don't derive a Boost total from it.
get_account_ledger shows the movement itself: a Boost deposit is a
boost_deposit entry with counterparty Sokin Boost; money coming back
from Boost -- an Easy Access withdrawal, or a Fixed Term Boost reaching or
leaving its term -- is a boost_maturity_payout entry, which carries
neither a counterparty nor a description, so recognise it by the type
alone.

Each payment-details object carries accountName, accountNumber,
accountType, iban, routingCodeType, routingCode, bicCode, email,
corporateReference, bankName, bankCountry, bankAddress,
bankBranch.

Full response adds: version only, an optimistic-concurrency counter
with no user-facing meaning.

Validation errors: account_reference must not be blank. This is
enforced locally rather than left to the upstream API because a blank path
segment collapses the request down to the account collection route; it
would return a list of accounts instead of erroring.

Example

Request

{"name": "get_account", "arguments": {"account_reference": "CCA-1001"}}

Reply

Account CCA-1001 (GBP): balance 48200.00, of which 47150.00 available. Local funding: active — ready to receive payments — pay into Northwind Trading Ltd, account 12345678, SortCode 04-00-75, at Modulr FS Limited (London branch), GB. International funding: not yet set up.

Reply as data

{
  "message": "Success.",
  "data": {
    "externalReference": "CCA-1001",
    "currency": "GBP",
    "currentBalance": "48200.00",
    "availableBalance": "47150.00",
    "localAccountStatus": "ACTIVE",
    "internationalAccountStatus": "NOT_PROVISIONED",
    "localPaymentDetails": {
      "accountName": "Northwind Trading Ltd",
      "accountNumber": "12345678",
      "routingCodeType": "SortCode",
      "routingCode": "04-00-75",
      "bankName": "Modulr FS Limited",
      "bankBranch": "London",
      "bankCountry": "GB"
    },
    "internationalPaymentDetails": []
  }
}

`get_account_ledger`

Get Account Ledger · read-only · touches an external system

Transaction history for one account. Cursor-paginated (this is a genuinely
paginated endpoint, unlike list_accounts).

Parameter	Type	Required	Description
`account_reference`	string	yes	The corporate currency account reference
`from_date`	string	no	Filter from this date (`YYYY-MM-DD`)
`to_date`	string	no	Filter to this date (`YYYY-MM-DD`)
`limit`	integer	no	Items per page (default 25, max 100)
`next_token`	string	no	Cursor from the previous page's `pagination.nextToken`

content, a markdown table, amounts signed for readability:

3 ledger entries for CCA-1001 (amounts shown as +credit/-debit):

Date	Type	Amount	Counterparty	Description
2026-08-14	deposit	+5000.00	Contoso Ltd	Invoice 4471
2026-08-15	withdrawal	-1250.00	Fabrikam GmbH	Supplier payment
2026-08-16	FX Trade	-800.00		GBP to EUR conversion

The counterparty column reads sourceReference for credit rows and
beneficiary for debit rows; the two are mutually exclusive upstream,
gated by direction.

structuredContent, envelope {"message": "Success.", "data": [...], "pagination": {...}},
each entry (8 fields, the complete set on this model, nothing trimmed):

Field	Type	Description
`amount`	decimal	Unsigned amount. The sign shown in `content` is derived from `direction`
`direction`	string	`credit` or `debit` in practice (see the enums appendix); typed as a plain string upstream, not an enforced enum
`type`	string	Entry type. Only FX and forward legs get a friendly label; every other kind appears under its own raw `snake_case` value. See the enums appendix for the full set
`effectiveDate`	date	Date the entry takes effect
`sourceReference`	string, or null	Counterparty on credit entries
`beneficiary`	string, or null	Counterparty on debit entries
`description`	string, or null	Free text
`transactionReference`	string, or null	Logical reference tying together every leg of one transaction

Full response adds: nothing; this is already the complete raw model.
transactionReference is kept in the compact response deliberately despite
looking like an internal correlation id: it is the reference that makes
reconciliation possible.

Validation errors: account_reference must not be blank.

Example

Request

{
  "name": "get_account_ledger",
  "arguments": {"account_reference": "CCA-1001", "from_date": "2026-08-01", "limit": 25}
}

Reply

3 ledger entries for CCA-1001 (amounts shown as +credit/-debit):

Date	Type	Amount	Counterparty	Description
2026-08-14	deposit	+5000.00	Contoso Ltd	Invoice 4471
2026-08-15	withdrawal	-1250.00	Fabrikam GmbH	Supplier payment
2026-08-16	FX Trade	-800.00		GBP to EUR conversion

More results available -- pass next_token='eyJrIjoi...' to see more.

Reply as data

{
  "message": "Success.",
  "data": [
    {
      "amount": "5000.00",
      "direction": "credit",
      "type": "deposit",
      "effectiveDate": "2026-08-14",
      "sourceReference": "Contoso Ltd",
      "beneficiary": null,
      "description": "Invoice 4471",
      "transactionReference": "TXN-77120"
    },
    {
      "amount": "1250.00",
      "direction": "debit",
      "type": "withdrawal",
      "effectiveDate": "2026-08-15",
      "sourceReference": null,
      "beneficiary": "Fabrikam GmbH",
      "description": "Supplier payment",
      "transactionReference": "TXN-77121"
    },
    {
      "amount": "800.00",
      "direction": "debit",
      "type": "FX Trade",
      "effectiveDate": "2026-08-16",
      "sourceReference": null,
      "beneficiary": null,
      "description": "GBP to EUR conversion",
      "transactionReference": "TXN-77122"
    }
  ],
  "pagination": {"nextToken": "eyJrIjoi...", "previousToken": null, "totalItems": 3, "hasMore": true}
}

`list_instructions`

List Instructions · read-only · touches an external system

Lists payment instructions for a corporate or for a single account.
Cursor-paginated.

Parameter	Type	Required	Description
`corporate_reference`	string	one of	The corporate to list for
`cca_reference`	string	one of	The account to list for
`completed`	boolean	no	Deprecated on the backend itself -- `true` for terminal (Processed or Failed), `false` for everything still in progress. Mutually exclusive with `exclude_display_status`, which should be preferred -- see below
`exclude_display_status`	enum, repeatable	no	Exclude rows whose `displayStatus` is in this list. Only `Processed` and `Failed` are accepted, the backend's only terminal statuses; any other value is rejected by schema validation, not sent. Mutually exclusive with `completed`
`limit`	integer	no	Max instructions (default 20, max 100)
`next_token`	string	no	Cursor from the previous page
`sort_order`	enum	no	`"desc"` (default, newest first) or `"asc"` (oldest first), by instruction id

Exactly one of corporate_reference or cca_reference is required.

completed cannot express "outstanding including failures".
completed=true includes Failed as well as Processed, so asking
completed=false for what is still outstanding silently excludes every
failed instruction, even though the portal's own Transaction Queue shows
them as unresolved work. exclude_display_status=["Processed"] is what's
actually outstanding / needs attention -- still-in-progress rows and
Failed ones together, distinguishable by each row's own displayStatus
field (already present on every row, not an extra lookup). By contrast,
exclude_display_status=["Processed", "Failed"] is narrower: still in
progress, nothing terminal at all -- that drops failures rather than
surfacing them, so it is not the "outstanding" answer. "Failed only" is
not expressible as a filter here -- exclude Processed and read each
row's own displayStatus instead. This list also shows approval
rejections as Failed (only get_instruction relabels them Rejected),
so excluding Failed drops those too, and Rejected is not an accepted
value for this parameter. The backend's own route (GET /instructions)
also marks completed deprecated in favour of excludeDisplayStatus, so
exclude_display_status is the parameter to build on, not just the more
precise one.

content, a markdown table: see the Example below.

structuredContent, envelope {"message": "Success.", "data": [...], "pagination": {...}},
each item:

Field	Type	Description
`instructionReference`	string	The instruction's external reference
`corporateReference`	string	Owning corporate
`ccaReference`	string	Source account. A corporate can hold several accounts in one currency, so currency alone does not identify it
`instructionType`	string	See the enums appendix
`amount`	decimal	Instruction amount
`currency`	string	ISO 4217
`displayStatus`	string	User-facing status, see the enums appendix
`createdAt`	datetime	Creation timestamp
`updatedAt`	datetime	Last update timestamp

This list summary is a lighter model than get_instruction's full detail
response below; it does not carry fees, beneficiary, or currency-conversion
fields at all.

Full response adds: status, the internal instruction status. The
API's own field description calls it internal, and displayStatus already
carries the user-facing equivalent.

Validation errors:

Error: You must provide either corporate_reference or cca_reference.

Error: Provide only one of corporate_reference or cca_reference, not both.

Error: Provide only one of completed or exclude_display_status, not both.

An exclude_display_status value other than Processed or Failed fails MCP argument-schema validation before the tool body runs, the same as an invalid payment_purpose elsewhere in this reference.

A sort_order value other than asc or desc fails the same schema validation.

Example

Request

{"name": "list_instructions", "arguments": {"corporate_reference": "CORP-8842", "limit": 20}}

Reply

2 instructions for CORP-8842:

Reference	Account	Type	Amount	Currency	Status	Created
INS-5512	CCA-1001	Payment	1250.00	GBP	Processed	2026-08-15T09:12:44Z
INS-5513	CCA-1002	FXPayment	800.00	USD	Pending Settlement	2026-08-16T11:03:02Z

Reply as data

{
  "message": "Success.",
  "data": [
    {
      "instructionReference": "INS-5512",
      "corporateReference": "CORP-8842",
      "ccaReference": "CCA-1001",
      "instructionType": "Payment",
      "amount": "1250.00",
      "currency": "GBP",
      "displayStatus": "Processed",
      "createdAt": "2026-08-15T09:12:44Z",
      "updatedAt": "2026-08-15T09:14:02Z"
    },
    {
      "instructionReference": "INS-5513",
      "corporateReference": "CORP-8842",
      "ccaReference": "CCA-1002",
      "instructionType": "FXPayment",
      "amount": "800.00",
      "currency": "USD",
      "displayStatus": "Pending Settlement",
      "createdAt": "2026-08-16T11:03:02Z",
      "updatedAt": "2026-08-16T11:04:18Z"
    }
  ],
  "pagination": {"nextToken": null, "previousToken": null, "totalItems": 2, "hasMore": false}
}

`get_instruction`

Get Instruction · read-only · touches an external system

Full detail for one instruction: status, currencies, fees, beneficiary.

Parameter	Type	Required	Description
`instruction_reference`	string	yes	The instruction reference to look up

content, a sentence, with optional clauses appearing only when the
underlying field is populated: see the Example below.

structuredContent, envelope {"message": "Success.", "data": {...}}.
The full upstream model has 25 fields; the compact response drops 3 of them
(version, status, quoteId), leaving 22, plus 2 more synthesized ones
described below (rejectedBy, rejectionComment) present only when a
rejection is detected and the approval lookup succeeds:

Field	Type	Description
`externalReference`	string	The instruction reference
`createdAt`	datetime	Creation timestamp
`updatedAt`	datetime	Last update timestamp
`failureReason`	string, or null	Why it failed, when it did
`displayStatus`	string	User-facing status, see the enums appendix. Can be the synthesized value `Rejected`, described below -- not a raw backend value
`rejectedBy`	string, or absent	Present only when `displayStatus` is the synthesized `Rejected` AND the approval lookup succeeded. The rejecting user's raw id (IdP scheme, tenant and principal id, e.g. `waad\|<tenant>\|<principal-id>`); this server has no name-resolution for it, which is also why it's left out of this tool's `content` text and only present here
`rejectionComment`	string, or absent	Present under the same condition as `rejectedBy`. The rejecting approver's own comment (mandatory on their end)
`instructionType`	string	See the enums appendix
`corporateReference`	string	Owning corporate
`corporateCurrencyAccount`	string	Source account
`amount`	decimal	Source amount
`destinationAmount`	decimal, or null	Destination amount; set only when a conversion happens
`sourceCurrency`	string	ISO 4217
`destinationCurrency`	string	ISO 4217
`beneficiaryReference`	string, or null	The payee
`senderReference`	string, or null	Text shown to the recipient
`paymentPurpose`	string, or null	Purpose code
`paymentReference`	string, or null	Payment reference
`sokinFxFee`	decimal	FX fee
`sokinTransactionFee`	decimal	Transaction fee
`resellerTransactionFee`	decimal	Reseller fee
`destinationCorporateReference`	string, or null	Destination corporate, when distinct from the source
`destinationCorporateCurrencyAccount`	string, or null	Destination account, when applicable
`instructionRequestReference`	string, or null	The request this instruction came from. Pass it to `get_instruction_request`

Full response adds: version (an optimistic-concurrency counter),
status (the internal status; the API's own field description calls it
internal, and even that description is known to be incomplete versus the
real enum, so prefer displayStatus), and quoteId (an internal
correlation id no tool here reads). It is not a strict superset of the
compact response for a rejected instruction: displayStatus: "Rejected"
and rejectedBy/rejectionComment are this server's own inference, never
present in the backend's own payload, so the full response's
structuredContent shows the raw displayStatus: "Failed" with neither
extra field, even while content (built from the compact view regardless
of which response mode was requested) still says "Rejected". Use the
compact response (the default) when this distinction matters; the full
response trades it away for an exact, unmodified copy of what the backend
actually sent.

A rejection during approval vs. a real failure: the B2B API itself has
no distinct status for an instruction being declined during approval --
both that and a genuine processing failure come back as
displayStatus: "Failed". This server detects a rejection from an exact
"Approval rejected: " prefix on failureReason and relabels
displayStatus to Rejected before returning it -- a value the backend
itself never sends, present only in this tool's response. This is usually
a human declining the instruction in the approval portal, but not always:
a bulk-file import failure or a customer cancellation resolve an
instruction's approval as a rejection the same way, with the identical
prefix and no portal decision involved -- always read failureReason for
the real reason rather than assuming a portal decline. When the rejection
did come from an actual approval decision, this server also calls a
second, independent endpoint (

GET /approval-evaluations/by-instruction/
{reference}

) to find the rejecting decision and adds
rejectedBy/rejectionComment. That second call can fail on its own
(404 when no approval evaluation exists, a transient error), and finds
nothing for a rejection with no underlying approval decision (the
bulk-file and cancellation cases above); either way, displayStatus is
still Rejected but the two extra fields are simply absent. This
Rejected is unrelated to get_instruction_request's own Rejected (see
its statuses below) -- that one means the request never became an
instruction at all.

Example

Request

{"name": "get_instruction", "arguments": {"instruction_reference": "INS-5513"}}

Reply

Instruction INS-5513 (FXPayment) for corporate CORP-8842, account CCA-1002: 800.00 USD -> 742.10 EUR, status Pending Settlement. Beneficiary: BEN-3301. Sender reference (shown to the recipient): INV-4471. Purpose: SUPPLIER_PAYMENT. Fees: 4.20 FX, 1.50 transaction, 0.00 reseller. Created 2026-08-16T11:03:02Z, updated 2026-08-16T11:04:18Z.

Reply as data

{
  "message": "Success.",
  "data": {
    "externalReference": "INS-5513",
    "displayStatus": "Pending Settlement",
    "instructionType": "FXPayment",
    "corporateReference": "CORP-8842",
    "corporateCurrencyAccount": "CCA-1002",
    "amount": "800.00",
    "destinationAmount": "742.10",
    "sourceCurrency": "USD",
    "destinationCurrency": "EUR",
    "beneficiaryReference": "BEN-3301",
    "senderReference": "INV-4471",
    "paymentPurpose": "SUPPLIER_PAYMENT",
    "sokinFxFee": "4.20",
    "sokinTransactionFee": "1.50",
    "resellerTransactionFee": "0.00",
    "failureReason": null,
    "instructionRequestReference": "IR-Payment-5513",
    "createdAt": "2026-08-16T11:03:02Z",
    "updatedAt": "2026-08-16T11:04:18Z"
  }
}

`get_instruction_request`

Get Instruction Request · read-only · touches an external system

Reads the outcome of a submitted payment. A submitted payment becomes an
instruction request first and is processed asynchronously: acceptance at
submission does not mean the payment was created. This is the way to get
from a submission to the instruction it produced.

Parameter	Type	Required	Description
`instruction_request_reference`	string	yes	The instruction request reference exactly as the API returned it (currently `IR-`-prefixed, e.g. `IR-Payment-...`, though treat the prefix as convention, not contract). Not an instruction reference; those belong to `get_instruction`. If you only have an instruction, its `instructionRequestReference` field is this value.

Read status carefully: the names run counter to their meaning.
Created is the initial, still-processing state, not a success. Accepted
is terminal success. Rejected is terminal failure. These are the only
three values this field takes.

content, one sentence, branching on status:

Instruction request IR-Payment-1 is still being processed -- no outcome yet. Check again shortly.

Instruction request IR-Payment-1 was accepted: instruction INS-42 was created. Use get_instruction for its full detail.

Instruction request IR-Payment-1 was rejected: Insufficient balance (category: amount). No instruction was created.

createdInstructionReference is nullable on the contract even when the
status is Accepted; in that case the sentence ends "accepted; the created
instruction's reference is not available yet" rather than rendering a
literal None. A status outside the three above is echoed verbatim (

...
has status <value>.

) rather than reinterpreted.

structuredContent, envelope {"message": "Success.", "data": {...}},
5 fields:

Field	Type	Description
`externalReference`	string	The instruction request reference
`status`	string	`Created`, `Accepted`, or `Rejected`; see the enums appendix
`createdInstructionReference`	string, or null	The instruction produced on acceptance. Feed it to `get_instruction`. Nullable even when `Accepted`
`failureReason`	string, or null	Why the request was rejected
`errorCategory`	string, or null	The field or category that caused the rejection. See the enums appendix

Full response adds: version, an optimistic-concurrency counter.

Tool-specific errors: a blank reference is rejected locally before any
call. A response whose payload is missing externalReference or status
is rejected as an unexpected shape rather than reported as a confident
success. A not-found is usually final: the reference is wrong (commonly an
instruction reference passed here by mistake), or the request belongs to a
different login. The one transient case is a request submitted moments ago,
which can briefly read as not-found while still being persisted; retry
once, then stop.

Example

Request

{"name": "get_instruction_request", "arguments": {"instruction_request_reference": "IR-Payment-77"}}

Reply

Instruction request IR-Payment-77 was accepted: instruction INS-9 was created. Use get_instruction for its full detail.

Reply as data

{
  "message": "Success.",
  "data": {
    "externalReference": "IR-Payment-77",
    "status": "Accepted",
    "createdInstructionReference": "INS-9",
    "failureReason": null,
    "errorCategory": null
  }
}

`validate_payment_instruction`

Validate Payment Instruction · read-only · touches an external system

Dry-runs a payment: the same checks real creation performs (account,
beneficiary, balance, fee resolution) run synchronously with nothing
persisted and no money moved.

Same currency only. This tool never converts currencies -- the payment
goes out in the source account's own currency. A beneficiary that exists
but has no destination in that currency fails with

errorCategory:
"beneficiary_currency"

and a reason naming the currency, instead of a false
"beneficiary does not exist" (see the enums appendix for why that
distinction needs an MCP-server-side check at all) -- but this is
best-effort, not a guarantee. It depends on the account's currency
resolving, the corporate reference parsing out of the account reference,
and a beneficiary lookup all succeeding; when any of those fails, the
backend's own answer (which does conflate the two cases) passes through
unchanged. A caller should check list_beneficiaries before assuming
"does not exist" means a payee needs creating. For a cross-currency
payment to that same beneficiary, use create_fx_payment_instruction
instead.

It is marked read-only despite issuing a POST upstream, and that is not a
convenience label. The validate handler is wired with no repositories at
all (unlike the create handler beside it), and the engine it runs performs
no writes. The path holds nothing capable of persisting; the wire verb is
an artifact of sending a request body.

Parameter	Type	Required	Description
`corporate_currency_account`	string	yes	Source account reference from `list_accounts`. Currency and corporate are derived from it
`beneficiary_reference`	string	yes	The payee, from `list_beneficiaries`. Must already exist
`amount`	string	yes	Plain decimal, max 2 places, greater than zero (e.g. `"125.50"`)
`reseller_fee`	string	no	Same format as `amount`, zero or greater
`sender_reference`	string	no	Shown to the recipient, max 18 characters
`payment_purpose`	enum	no	One of 22 declared purpose codes (e.g. `ACCOUNTS_PAYABLE`); see the enums appendix. An unrecognized value is rejected by schema validation, not sent
`amount_is_fees_inclusive`	boolean	no	`true` takes fees out of `amount`; default `false` adds them on top

content, a verdict sentence: see the Example below.

Validation failed: insufficient available balance on the source account (category: amount). The engine still computed amounts: total debit 1256.70 (5.20 Sokin fee, 1.50 reseller fee). Nothing was created and no money moved.

structuredContent, envelope {"data": {...}}:

Field	Type	Description
`success`	boolean	Whether the dry run passed every check
`failureReason`	string, or null	Why it failed
`errorCategory`	string, or null	Machine-readable failure category. Not a closed set on the wire; see the enums appendix
`feeBreakdown`	object, or null	Amounts, when the engine got far enough to compute them

feeBreakdown carries amount (total debit including fees, required),
destinationAmount (what the beneficiary receives, nullable), sokinFee
(required), resellerFee (required), and feeRateCardReference (nullable).
It is populated on failures too; an insufficient-balance rejection still
shows how short the account is.

Full response adds: the envelope's message field, the literal string
"Success." on every call regardless of the verdict. It describes the HTTP
exchange, not the validation, and reading it as a result would be a bug.

Validation errors:

Error: corporate_currency_account must not be empty.

Error: beneficiary_reference must not be empty.

Error: amount must be a plain decimal number with at most 2 decimal places (e.g. '125.50'), got '1e3'.

Error: amount must be greater than zero.

Error: reseller_fee must be ... (same format rule, but zero is allowed)

Error: sender_reference must be at most 18 characters, got 24.

The amount rule is deliberately stricter than the upstream API's. Pydantic
would parse "1e3" as 1000 and accept signed forms; for anything
payment-shaped, silent reinterpretation is the worst available failure
mode, so only a plain unsigned decimal passes here.

A malformed upstream response is a hard error. A 200 whose success
verdict is missing or not a boolean is rejected as a synthesized 502:
"API error (502): API returned an unexpected response shape for the
validation -- the result is unknown; do not report the payment as passed or
failed." A missing verdict must never render as a failed validation.

Example

Request

{
  "name": "validate_payment_instruction",
  "arguments": {
    "corporate_currency_account": "CCA-1001",
    "beneficiary_reference": "BEN-3301",
    "amount": "1250.00",
    "reseller_fee": "1.50",
    "sender_reference": "INV-4471"
  }
}

Reply

Validation passed: this payment would clear the creation checks. Total debit 1256.70 (5.20 Sokin fee, 1.50 reseller fee); beneficiary would receive 1250.00. Nothing was created and no money moved.

Reply as data

{
  "data": {
    "success": true,
    "failureReason": null,
    "errorCategory": null,
    "feeBreakdown": {
      "amount": "1256.70",
      "destinationAmount": "1250.00",
      "sokinFee": "5.20",
      "resellerFee": "1.50",
      "feeRateCardReference": "RC-14"
    }
  }
}

`create_payment_instruction`

Create Payment Instruction · read-only · touches an external system

Prepares a payment for a human to review. It submits nothing. Despite
the name, no payment exists after this call and no money has moved.

Same currency only, same reason and same

errorCategory:
"beneficiary_currency"

as validate_payment_instruction above -- this
tool runs the same check before ever calling the backend, so a
cross-currency beneficiary produces the same distinct reason here instead
of an approvable-looking draft.

What it actually does: resolves the source account's currency, its
visible identifier (the IBAN or account number shown in the Sokin
portal), and the beneficiary's display name and country with two
read-only lookups (account and beneficiary), runs the currency-mismatch
check against that same currency, re-runs the validate dry run so the
review can show server-computed fees rather than model-relayed figures,
mints an idempotency key server-side, and registers the normalized draft
against that key. When the calling session has declared MCP UI support it
also renders its own MCP UI embed (ui://sokin-mcp/payment-review), a
review card with Approve and Cancel; only the user's Approve click there
submits, by invoking submit_payment_instruction from inside the widget.

Call validate_payment_instruction first. This tool's own description
instructs the calling model to validate and iterate with the user (fixing
inputs, asking for missing data) until validation passes, and only then
prepare. The dry run this tool re-runs internally is a guard, not the
pre-flight: a draft that fails it produces no approvable draft and no
registered key, costing the user a round trip.

MCP UI support changes only which text this tool shows you, not whether
it will run. The human control for a payment is approval in the Sokin
portal, not this tool's widget -- see "Card support and where the human
control sits" above. The session's declared capability is read only to
choose the wording:

MCP UI declared: the card renders, and the text says "awaiting the
user's confirmation in the review widget." Only the widget's Approve
click should invoke submit_payment_instruction.

Not declared, or unknown: there is no card. The text spells out the
idempotencyKey in plain words -- structuredContent is not reliably
surfaced to the calling model, so the key has to travel where the model
can read it -- and instructs the calling model to read the draft and fees
back to the user, get their explicit approval in chat, and only then call
submit_payment_instruction itself with that key and byte-identical
arguments.

structuredContent does not change between the two branches: idempotencyKey
is present in both once validation passes. Only content changes.

A non-UI host does not "fail safe" just because no card appears: the
prepare half returns the idempotency key in its structuredContent, which
is by itself enough for a caller to invoke the submit half directly. What
stands between a model seeing the key and a submission is the
explicit-approval instruction in the non-UI text above, the host's own
confirmation prompt on submit_payment_instruction's destructive
annotation, and portal approval after it. Treat that prompt as
load-bearing, not decorative, if you are embedding this server in your own
agent -- see submit_payment_instruction's own entry for the full
reasoning.

It is marked read-only for the same reason validate_payment_instruction
is: its only upstream call is the side-effect-free dry run. It does write
one piece of server-side state (the draft record the paired submit tool
checks against), which is gate bookkeeping, not a business write.

Parameter	Type	Required	Description
`corporate_currency_account`	string	yes	Source account reference from `list_accounts`. Currency and corporate are derived from it
`beneficiary_reference`	string	yes	The payee, from `list_beneficiaries`. Must already exist — if it doesn't, create it first with `create_beneficiary` (needs a one-time emailed code)
`amount`	string	yes	Plain decimal, max 2 places, greater than zero (e.g. `"125.50"`)
`reseller_fee`	string	no	Same format as `amount`, zero or greater
`sender_reference`	string	no	Shown to the recipient, max 18 characters
`payment_purpose`	enum	no	One of 22 declared purpose codes (e.g. `ACCOUNTS_PAYABLE`); see the enums appendix. An unrecognized value is rejected by schema validation, not sent
`amount_is_fees_inclusive`	boolean	no	`true` takes fees out of `amount`; default `false` adds them on top
`status_check_key`	string	no	Leave unset. Only the review widget passes it, with the idempotency key it was given, to ask whether that draft was already submitted. With it the tool prepares nothing and makes one read-only call, for the account; see "Status check" below

content, when MCP UI is declared -- a not-submitted notice worded so a
model relaying it cannot truthfully claim the payment was made: see the Example below.

content, when MCP UI is not declared (or unknown) -- the idempotency
key spelled out, and explicit chat-confirmation instructions:

Payment prepared and validated -- nothing has been submitted yet. idempotency key: 3fae1c9e-... . Read the draft and fees back to the user and get their explicit approval; only after they approve, call submit_payment_instruction yourself with this idempotency_key and the exact same arguments. Never submit without that approval, and never tell the user the payment was made until submit_payment_instruction succeeds -- it will still need approval in the Sokin portal afterward.

When the dry run fails, there is no approvable draft and no registered key
(this text is the same in both branches), and the text says what to do
instead:

The payment could not be validated: insufficient available balance on the source account. Fix the inputs (validate_payment_instruction is the pre-flight) and prepare again. Nothing has been submitted.

structuredContent: this tool builds its own payload, so there is no
{"data": ...} envelope:

Field	Type	Description
`draft`	object	The normalized payment exactly as it would be submitted
`currency`	string, or null	The source account's currency, for display. Null if the lookup failed (display sugar that never blocks a valid draft). Absent entirely on the validation-failure branch
`accountIdentifier`	string, or null	The account's visible identifier (`"IBAN ..."` or `"account ..."`), the same one shown in the Sokin portal. Null if the lookup failed
`beneficiaryDisplayName`	string, or null	The payee's human-readable name, for display instead of the raw reference. Null if the lookup failed
`beneficiaryCountryCode`	string, or null	The payee's country, alongside the display name. Null if the lookup failed
`validation`	object	The dry-run verdict, same shape as `validate_payment_instruction`'s `data`, including `feeBreakdown`
`idempotencyKey`	string, or null	Server-minted, registered to this exact draft. Null when validation failed, because no approvable draft exists
`duplicateWarning`	object	Present only when an identical draft was submitted within the duplicate window: `instructionRequestReference` and `submittedAt` of that earlier payment

All four display fields (currency, accountIdentifier,
beneficiaryDisplayName, beneficiaryCountryCode) come from two
read-only lookups this tool makes itself, synchronously, before the card
ever renders -- never from the widget making its own round trip after the
fact. Each fails soft to null independently; a lookup failure never
blocks an otherwise-valid draft, and the caller falls back to the raw
reference rather than a bare "unavailable" message.

draft uses the tool's own snake_case parameter names, not the API's
camelCase: corporate_currency_account, beneficiary_reference, amount,
reseller_fee, sender_reference, payment_purpose,
amount_is_fees_inclusive. It sits next to camelCase siblings like
idempotencyKey in the same object because it is the tool's argument set,
not an upstream payload. Normalization strips every string and uppercases
payment_purpose; a whitespace-only optional becomes null, except
reseller_fee, which becomes "" and is then refused as not a plain
decimal.

duplicateWarning is not an error. It means this exact payment has
already been submitted. When a widget is present it renders an
already-submitted card with no Approve button, then follows that payment's
current status from its instructionRequestReference (waiting for
approval, completed, rejected or failed), since submitted is not the same as
paid; either way submit_payment_instruction refuses the draft. The block
lasts 12 hours from the earlier submission, and counts a submission that
was later rejected; after it, the same content can be approved again. A
deliberate second identical payment inside the window is prepared with a distinguishing
sender_reference, which makes it a different draft. There is no
acknowledgement flag to override this by design: any flag a caller could
set would be one a model could set too.

Full response adds: nothing. This tool assembles its own payload, so
the compact and full responses are the same object.

Validation errors: the same set validate_payment_instruction lists,
over the same normalized draft. A draft that renders as reviewable is one
submit would also accept.

Draft lifetime. The key and the reviewed draft live in the server's
session store. Pending drafts expire after 24 hours; an expired key is
refused and the payment is simply prepared again. Submitted records are
kept for 7 days, answering a same-key replay with the original payment;
after that the key is refused as unknown and nothing is sent (the
backend's own dedupe on the key is permanent). Hosts may
re-execute a read-only tool freely (on session restore, for instance); each
execution mints a fresh key and registers a fresh draft, which is why
unapproved drafts expire rather than accumulate.

Status check (status_check_key). Hosts replay this tool's stored
result to the review card whenever it remounts, for instance when a
conversation is reopened, and do not call the tool again. That replayed
result predates any approval, so on every mount the card asks this tool
again, passing its own draft and its own idempotency key as
status_check_key. With it, the tool answers from the server's session
store and returns before anything else: no dry run, no beneficiary lookup
and no new key. It makes exactly one call to the Sokin API: it reads
corporate_currency_account with the caller's own token, and answers only
if that succeeds. The one exception is an empty account, which answers
expired with no call at all, since no prepared draft can have one. The session store is shared by every user, so without
that read anyone signed in could ask about another corporate's payment. A
refused read comes back as the usual error, identical whether or not the
payment exists, and the card shows it as "couldn't check". The card keeps
its original key, so an Approve after a reload is a replay of that key
rather than a new submission.

Field	Type	Description
`idempotencyKey`	string	The key that was asked about, echoed back
`submissionState`	string	`submitted`, `in_flight` (an identical submission is running now, or its outcome is unknown after a 5xx or timeout, so the payment may already exist; nothing is approvable), `pending` (not submitted, still approvable under this key) or `expired` (the pending draft expired, or the key was not registered for these arguments, and no submission is on record; the text says so rather than claiming nothing went out, since a lost record would look the same)
`duplicateWarning`	object	Present only when `submitted`: `instructionRequestReference`, `submittedAt` (null if the server did not record the time) and `submittedUnderThisKey` (true when this key's own draft was submitted, false when an identical draft was submitted under another key). Submitted means Sokin accepted the request, not that the payment completed; the card follows the rest from `instructionRequestReference`

For a pending draft the content reads:

Status check only -- nothing was prepared and nothing was submitted by this call. This payment draft has not been submitted; it is still awaiting the user's decision in the review widget. status_check_key is for the review widget only; omit it to prepare a payment.

If a reply carries no submissionState, the card treats it as "couldn't
check" and never offers Approve on the key it returns. A store failure is an error result, never a pending
answer, and so is a draft record in a state the server does not recognise. The
card also refuses a submitted answer that carries no
instructionRequestReference, showing "couldn't check" instead. If no
reply arrives within 15 seconds (a host that never answers a widget's
tools/call), the card shows "couldn't check" too; a reply that arrives
later still renders.

While it waits, the card already shows the payment's details from the
replayed result, since none of them depend on the answer. Only what it
offers waits: the header reads "Checking status", a spinner takes the place
of Approve and Cancel, the FX card starts no quote countdown, and nothing is
sent to the model. "Couldn't check", in flight and expired keep the details
on screen and put their message where the buttons would be.

Example

Request

{
  "name": "create_payment_instruction",
  "arguments": {
    "corporate_currency_account": "CCA-1001",
    "beneficiary_reference": "BEN-3301",
    "amount": "1250.00",
    "reseller_fee": "1.50",
    "sender_reference": "INV-4471"
  }
}

Reply

Payment prepared and validated -- awaiting the user's confirmation in the review widget. Nothing has been submitted; do not report this payment as made, and do not call submit_payment_instruction yourself.

Reply as data

{
  "draft": {
    "corporate_currency_account": "CCA-1001",
    "beneficiary_reference": "BEN-3301",
    "amount": "1250.00",
    "reseller_fee": "1.50",
    "sender_reference": "INV-4471",
    "payment_purpose": null,
    "amount_is_fees_inclusive": false
  },
  "currency": "GBP",
  "validation": {
    "success": true,
    "failureReason": null,
    "errorCategory": null,
    "feeBreakdown": {
      "amount": "1256.70",
      "destinationAmount": "1250.00",
      "sokinFee": "5.20",
      "resellerFee": "1.50",
      "feeRateCardReference": "RC-14"
    }
  },
  "idempotencyKey": "a5f1c8e0-7d3b-4f2a-9c61-0b8e4d2f1a77"
}

`submit_payment_instruction`

Submit Payment Instruction · destructive, idempotent · touches an
external system

The payment commit, and one of the three tools on this server that move
real money (with submit_fx_payment_instruction and settle_fx_quote). This
call itself cannot be cancelled once submitted, but it does not
complete a payment on its own: approval in the Sokin portal is the real
control -- see "Card support and where the human control sits" above.

When the calling session declared MCP UI support, this tool is invoked by
the payment review widget after the user clicks Approve, and is not meant
to be called directly in that case. When it did not, create_payment_instruction's
own text hands back the idempotency key and instructs the calling model to
get the user's explicit approval in chat first -- calling this tool
directly at that point is the intended path, not a bypass; there is no
separate capability check here that would refuse it. Either way it accepts
only an idempotency key that create_payment_instruction minted, and only
with arguments that match the reviewed draft exactly. It declares
readOnlyHint: false, destructiveHint: true and idempotentHint: true,
and carries no MCP UI embed of its own: when a widget invoked it, its
result renders in that same widget.

Parameter	Type	Required	Description
`idempotency_key`	string	yes	The key `create_payment_instruction` minted for this exact draft, from its `idempotencyKey` field
`corporate_currency_account`	string	yes	Must match the reviewed draft
`beneficiary_reference`	string	yes	Must match the reviewed draft
`amount`	string	yes	Must match the reviewed draft
`reseller_fee`	string	no	Must match the reviewed draft
`sender_reference`	string	no	Must match the reviewed draft
`payment_purpose`	enum	no	Must match the reviewed draft
`amount_is_fees_inclusive`	boolean	no	Must match the reviewed draft

content, a 202 receipt. Acceptance is not completion:

Payment submitted: instruction request IR-Payment-77 for 125.50 from CCA-1 to BEN-1. This is an instruction-request reference, not a completed payment -- it now needs human approval in the Sokin portal before it is processed. Check the outcome via get_instruction_request.

structuredContent, envelope {"data": {...}} with a single field on a
fresh submission:

Field	Type	Description
`externalReference`	string	The instruction request's reference. Pass it to `get_instruction_request` for the outcome

That is the whole upstream create response model. Everything about the
payment's actual business outcome is asynchronous, so nothing else is
available yet.

A malformed upstream response is a hard error. A 202 whose body lacks
externalReference is rejected as a synthesized 502 reading "API error
(502): API returned an unexpected response shape for the payment submission
-- whether it was accepted is unknown; check get_instruction_request before
retrying." After a POST that may have landed, "unknown" is the only honest
verdict, and it is never rendered as a failure.

Full response adds: the envelope's message field on a fresh
submission, which the compact response strips. On the replay branch below,
message is already passed through in compact mode.

What the gate refuses, and when. Every refusal below happens before the
server acquires an access token, so a refusal never depends on
authentication being healthy, and an auth outage cannot mask one behind a
generic client error. None of these reach the B2B API, and none create a
payment:

Situation	Result
Key unknown, fabricated, or expired	`Error: unknown idempotency key -- payments are prepared via create_payment_instruction, which mints the key and renders the review widget. If a prepared draft was lost, prepare it again.`
Arguments differ from the reviewed draft	`Error: these arguments do not match the draft the user reviewed under this idempotency key.` Only the exact reviewed draft can be submitted
Key already used, with different values	`Error: this idempotency key was already used to submit a different draft (IR-...). Nothing was submitted for these arguments.` Answering with the original's state would read as "your new values were handled"
Identical draft already submitted, under another key	`Error: an identical payment was already submitted as IR-... at ... -- this submission was refused, no new payment was created.` Lasts 12 hours. (Under the same key, the original's state is reported instead; see below)
Identical draft being submitted right now	`Error: an identical payment is being submitted right now ... Wait a moment, then check the payment's state with get_instruction_request.` Concurrent approvals are resolved atomically, so exactly one can win

The duplicate block is checked at submit time, not only at prepare time, so
it also catches two identical drafts that were both prepared before either
was approved. It is content-addressed over the normalized draft, so it
survives a fresh key and a restored session, for as long as the duplicate
window runs.

A replay is answered, not re-executed. Re-submitting the same draft
under the same key (a double click, a widget remount, a model retry, or a
non-UI client calling this a second time) sends nothing upstream. Instead
the tool reads the original payment's live state and reports it, which a
blind retry against the backend's own dedupe could not do:

This draft was already submitted -- no new payment was created. Instruction request IR-Payment-77 was accepted: instruction INS-9 was created. Use get_instruction for its full detail.

On that branch structuredContent is get_instruction_request's shape
(externalReference, status, createdInstructionReference,
failureReason, errorCategory), not the one-field submission shape. Code
that parses this tool's result must tolerate both. If the original's state
cannot be read, the tool says so rather than guessing.

What the gate does not guarantee. It constrains what can be submitted:
only the prepared draft, only once, only under a key the server minted. It
does not, and within MCP cannot, prove who approved it. There is no
widget-only channel, so idempotencyKey necessarily reaches the model in
create_payment_instruction's structuredContent regardless of whether a
widget rendered. The human step rests on either the review card plus the
host's confirmation prompt, or -- for a non-UI client -- the explicit
in-chat approval create_payment_instruction's own text asks for, plus that
same host confirmation prompt on this tool's destructive annotation either
way. If you are embedding this server in your own agent, treat that prompt
as load-bearing, not optional, in both cases.

The backend independently dedupes forever on

(idempotencyKey, type,
account)

, so duplicate money on one key is impossible even if the
server's own draft registry were lost entirely. The gate documented here is
an availability and integrity layer on top of that; the backend remains
the correctness layer.

Outcome tracking. When a review widget is present, it polls
get_instruction_request and then get_instruction, rendering the
payment's journey as a timeline and distinguishing created-and-processing,
created-but-awaiting-your-team's-approval (corporate approval rules), and
rejected or failed. "Needs approval" shows as soon as get_instruction
first reports Approval Initiated, and it is not final: portal approval is
human-paced, so the card keeps polling until the payment is Processed or
Failed. On supporting hosts it also pushes a self-contained summary into
the model's context via ui/update-model-context (MCP SEP-1865): once when
the payment first needs approval, and at each terminal state. That way the
assistant knows where the payment stands without re-querying. Hosts without support, and non-UI clients
entirely, get the same information from get_instruction_request directly.

Example

Request

{
  "name": "submit_payment_instruction",
  "arguments": {
    "idempotency_key": "a5f1c8e0-7d3b-4f2a-9c61-0b8e4d2f1a77",
    "corporate_currency_account": "CCA-1001",
    "beneficiary_reference": "BEN-3301",
    "amount": "1250.00",
    "reseller_fee": "1.50",
    "sender_reference": "INV-4471"
  }
}

Reply

Payment submitted: instruction request IR-Payment-77 for 1250.00 from CCA-1001 to BEN-3301. This is an instruction-request reference, not a completed payment -- it now needs human approval in the Sokin portal before it is processed. Check the outcome via get_instruction_request.

Reply as data

{"data": {"externalReference": "IR-Payment-77"}}

`get_fx_quote`

Get FX Quote · read-only · touches an external system

Starts an FX conversion for a buy/sell currency pair. This tool itself never
mints a quote, books a trade or moves money. What it returns depends
on whether your client declared MCP UI support at initialize time. This
is the only tool on this server whose response shape (not merely its text)
branches on that declaration.

This tool ships its own MCP UI embed (ui://sokin-mcp/fx-quote), an
interactive card covering the whole request, quote, and settle flow, with a
live countdown to expiry. Hosts that declared MCP UI support render it in
place of plain text.

Why this branches: a real FX quote is short-lived, and how short is set
by the provider that priced it rather than by anything the caller asks for
(see create_fx_quote). Minting one before a human ever sees a review
card — the straightforward approach — burns part of that window before
anyone can act on it, and on the shortest-lived pairs most of it. So this
tool never mints a quote itself; it only renders the interactive card, and
the card's own buttons call the two tools below at the moment a person
actually clicks:

Client declared MCP UI support: this call mints no quote and never
touches the rate endpoint; when corporate_currency_account is passed it
makes one read of that settlement account, to label the card. It renders
an empty, unpriced card echoing the requested pair and amount. The
card's "Get Quote" button calls create_fx_quote; its "Settle" button
calls settle_fx_quote. Do not tell the user a rate exists from this
call alone.

Client did not declare MCP UI support, or the declaration is unknown:
makes no upstream call at all, creates no quote and shows no rate: every
B2B rate endpoint persists a real quote, and there is no non-persisting
one. It returns the validated request plus a link to the Sokin portal,
where the user sees the live rate and executes the trade. That link is
configured on the server; where it is not configured the sentence still
tells the user to execute the trade in the Sokin portal, just with no
URL. A session in this state can never reach create_fx_quote or
settle_fx_quote; see settle_fx_quote's hard refusal below. (This is
the one pair on this server that refuses a non-UI session -- unlike the
payment pairs, see "Card support and where the human control sits.")

Parameter	Type	Required	Description
`buy_currency`	string	yes	ISO 4217 code being bought (e.g. `"USD"`)
`sell_currency`	string	yes	ISO 4217 code being sold (e.g. `"GBP"`)
`amount`	string	yes	The amount of whichever side `fixed_side` names
`fixed_side`	`"BUY"` or `"SELL"`	no	Which side `amount` refers to. Default `"SELL"`
`corporate_reference`	string	yes	The corporate to quote for. Always pass it: the upstream API only fills it in when the token itself names one corporate, and then it ignores what you pass, so passing it is never wrong. Call `list_corporates` first if the user hasn't named one
`corporate_currency_account`	string	no	The account to eventually settle from. Used by the card's later Settle step; when passed, the card-rendering branch also reads this account once to label it (the raw reference is never sent anywhere else by this call)
`card_id`	string	no	Leave unset. Only the FX quote card passes it, with the `cardId` from this tool's own earlier result, to ask what already happened on that card. With it the call is a status check, not a card; see "Card status check" below

When MCP UI is supported:

content is a one-sentence acknowledgement, not a quote: see the Example below.

structuredContent is a flat echo of the request, not upstream data:

Field	Type	Description
`buyCurrency`	string	Echoed request
`sellCurrency`	string	Echoed request
`amount`	string	Echoed request
`fixedSide`	string	Echoed request
`corporateReference`	string, or null	Echoed request
`corporateCurrencyAccount`	string, or null	Echoed request
`cardId`	string	A fresh id for this card (a uuid4). Minting it writes nothing. It is the card's only handle for asking, after a reopen, what already happened on it
`corporateCurrencyAccountDisplay`	string	The resolved label, e.g. `GBP account 12345678` or `GBP IBAN GB33...`, from a read of the settlement account. When that lookup fails or yields no identifier it is `<sellCurrency> account (number unavailable)` and the card data is still returned, never an error. Present only when `corporate_currency_account` was passed (non-blank); omitted otherwise, and then no upstream call is made at all. The card's requested state shows this label, never the internal reference

No full-response delta in this branch: the only upstream call is the
account read for the label, so there is nothing to widen.

Card status check (card_id). Hosts replay this tool's stored result
to the card whenever it remounts, for instance when a conversation is
reopened, and do not call the tool again. The card's own buttons call
create_fx_quote and settle_fx_quote, and those replies are not stored
in the conversation's transcript, so a reopen has nothing of them to replay.
(This is about replay, not secrecy: the server still assumes the model may
see them; see "What the gate does not guarantee" under settle_fx_quote.)
So the replayed result alone
cannot say whether the card was quoted or settled. On every mount the card
therefore calls this tool again with the same arguments plus card_id. create_fx_quote(card_id=)
records the card's latest quote, and settle_fx_quote records its
settlement (found from the key: the settle tool takes no card id).

With card_id, the tool answers from the server's session store only. It
runs ahead of the capability check and the rate call, makes no call to the
Sokin API, acquires no client and mints nothing. The card's records are
keyed by the caller's user and the card id together, so another user's card
id gets the same answer as an unknown one. That is also why no account read
is needed here, unlike the payment status checks. A card_id the server
could not have minted (not a uuid) is an error.

Each record also carries the request the card was made for: the currencies,
amount, fixed side, corporate and the account as the card passed it. A
record made for a different request than the status check's arguments is
an error, never an answer: it means a quote was made under this card's id
for something else (a model passing another card's id to
create_fx_quote), and neither unquoted nor that quote's own state is
safe to show on this card. The card shows it as "couldn't check", and its
own Get Quote is refused too, so a model that quotes under another card's id
can leave that card unusable (for 24 hours, or for 30 days if it settles). That
is the fail-closed trade: the other card is never shown a quote it did not
make. The user asks for a new card with get_fx_quote.

In the quoted state the reply carries every argument settle_fx_quote
needs, key included, to any caller of this tool, not only the card. The card
needs the original key to offer Settle on a reopen, and the server cannot
tell the card from the model, so the key does enter the transcript. That
is accepted because an MCP-originated FX settlement is held for portal
approval; see "What the gate does not guarantee" under settle_fx_quote
for that defence and its limits. settle_fx_quote also refuses a session
without MCP UI support.

Field	Type	Description
`cardId`	string	The card that was asked about, echoed back
`cardState`	string	`unquoted` (no quote from this card is on record: never quoted, its record expired, or not this user's card), `quoted` (the latest quote has no settlement on record and is inside its `expiresAt`; the card shows it live with Settle), `expired` (the latest quote has no settlement on record and is past its `expiresAt`; the card offers Get Quote again), `settling` (a settlement of it is running, or was attempted and its outcome never became known, so the conversion may exist; nothing is offered) or `settled` (a settlement from this card was submitted to Sokin as an instruction request; that is where the conversion starts, not proof it completed: the card resumes tracking it, through any wait for approval in the Sokin portal, until it is processed or fails)
`quote`	object	Present for every state but `unquoted`: the quote as `create_fx_quote` returned it. It carries `idempotencyKey` only when `quoted`, the one state that offers Settle, and it is null when `settled` was recorded without the card's quote
`instructionRequestReference`	string	Present only when `settled`: the `IR-` reference to follow with `get_instruction_request`

Precedence is settled > settling > quoted/expired > unquoted. A reopened
settled card offers neither Get Quote nor Settle. A second view of the same
card that was mounted earlier still shows Get Quote, so create_fx_quote
itself allows a new quote only on a card with no quote on record or whose
last quote expired with no settlement on record (see its card_id below). A press anywhere
else is refused, and that view re-checks the card and shows what is really
there. Only two presses on an unquoted card at the same moment can still
race. A card record with no settlement expires after 24 hours, the same as
the settlement draft; a card that ever had a settlement attempted keeps a
record of the attempt for 30 days (see below). A settled one is kept for 30 days. After that the
card has no history and offers Get Quote again. For a settled card
the content reads:

Status check only -- nothing was quoted or settled by this call. A conversion from this card was already settled as instruction request IR-FX-6b2f90. Do not quote or settle it again; check get_instruction_request for its outcome. card_id is for the FX quote card only; omit it to show a card.

An outcome nobody learned stays settling for 30 days. A settlement that
ends with a 5xx, a timeout, or a request cut off mid-POST (a cancelled task,
a process killed) may have gone through. settle_fx_quote keeps its claim
for 10 minutes, so a retry is possible after that (and safe: B2B looks an
instruction request up by idempotency key, type and account, and returns
the original instead of creating a second). The claim alone would not be
enough: a quote can live longer than it, since its window is provider-set
and uncapped, so without the attempt record the card could read as quoted
with a live Settle, or once the quote expired as expired with Get Quote, a
new key the dedupe cannot catch.

So before the request goes out, settle_fx_quote records the attempt on
the card, kept for 30 days, and removes it only when the request is
definitely rejected (a 4xx). An attempt whose outcome never became known
keeps the card reading settling for those 30 days, even after the
card's 24-hour quote record has expired, and it also lets the status check
find a settlement through the submitted record (kept 7 days) after that. A same-key
retry that turns out to have settled then reads settled. To start
another conversion, call get_fx_quote for a new card.

quoted and expired mean "no settlement on record", not "nothing was
settled", and expired never says nothing was settled: a store that lost a
write looks the same. Its text points at the account's recent instruction
requests.

If a reply carries no cardState, the card treats it as "couldn't check",
never as unquoted. A store failure is an error result, which the card
shows as "couldn't check" with Try again.

When MCP UI is not supported (or unknown):

No upstream call is made and no quote is created. content tells the model
so, names the trade, and points at the portal: see the Example below.

Where the portal link is not configured, the sentence reads "The Sokin
portal link is not configured for this deployment; direct the user to
the Sokin portal" in place of Open <url>.

A host that renders MCP Apps resources may still draw the card for this
reply: the resource is attached to the tool itself, not to the branch. The
card then shows the echoed request, unpriced, with a Get Quote button that
create_fx_quote refuses for the same reason. So a rendered card is not
proof the session declared support; declare it at initialize.

structuredContent, flat with no data envelope, unlike every other tool
here:

Field	Type	Description
`buyCurrency`	string	Echoed request, uppercased
`sellCurrency`	string	Echoed request, uppercased
`amount`	string	Echoed request
`fixedSide`	string	Echoed request
`corporateReference`	string	Echoed request
`indicative`	boolean	Always `true`
`quoteCreated`	boolean	Always `false`
`dashboardUrl`	string, or null	The configured portal link, null when not configured

No quoteId, rate, fee or expiry appears anywhere in this response, and
there is no full-response delta: nothing upstream was called.

Validation errors (all branches): checked in this order, before any
upstream call or capability lookup, returning the first failure as an
isError result. create_fx_quote and create_fx_payment_instruction
run the same checks.

Failure	Message
`buy_currency` / `sell_currency` is not 3-4 uppercase letters (checked first, buy then sell)	`Error: buy_currency must be a currency code such as 'USD', got 'usd1'.`
`buy_currency` / `sell_currency` is well-formed but not a supported currency	`Error: buy_currency 'ZZZ' is not a currency Sokin supports (e.g. 'USD', 'EUR', 'GBP').`
Same currency on both sides	`Error: buy_currency and sell_currency must differ (both are 'USD').`
`amount` is not a plain decimal (negative, `1e12`, three decimals, non-ASCII digits)	`Error: amount must be a plain decimal number with at most 2 decimal places (e.g. '125.50'), got '-5'.`
`amount` is zero	`Error: amount must be greater than zero.`
`amount` is above the quote limit	`Error: amount must not exceed 9999999999 (the FX quote limit), got '10000000000'.`

The supported set is Sokin's own list of 62 currency codes (including the
four-letter stablecoins USDT and USDC), not all of ISO 4217. It is a copy
of the Sokin currency list kept in this server, so a currency the API adds
is refused here until that copy is updated; upstream remains the final
authority.

Example

Request

{
  "name": "get_fx_quote",
  "arguments": {
    "buy_currency": "USD",
    "sell_currency": "GBP",
    "amount": "1000.00",
    "fixed_side": "SELL",
    "corporate_reference": "CORP-8842",
    "corporate_currency_account": "CCA-1001"
  }
}

Reply, with cards — an acknowledgement, not a rate:

Ready to quote GBP -> USD, 1000.00 on the sell side. No quote has been created yet -- the card's Get Quote button mints one.

The corporateCurrencyAccountDisplay field below is the account's resolved
label, shown on the card's requested state. It only appears when
corporate_currency_account is passed; if the account read fails it
becomes GBP account (number unavailable) and the card still renders.

Reply as data

{
  "buyCurrency": "USD",
  "sellCurrency": "GBP",
  "amount": "1000.00",
  "fixedSide": "SELL",
  "corporateReference": "CORP-8842",
  "corporateCurrencyAccount": "CCA-1001",
  "cardId": "0f8fad5b-d9cb-469f-a165-70867728950e",
  "corporateCurrencyAccountDisplay": "GBP account 12345678"
}

cardId is the card's own id. It is what lets the card remember its quote.

Reply, without cards — no quote, no rate, just the portal link:

This client cannot show the FX quote card, so no quote was created and no rate is shown. Open https://portal.sokin.com/v2/transfer/currency-exchange to see the live rate and execute GBP -> USD for 1000.00 (SELL side) for corporate CORP-8842. Do not try to quote or settle this through the assistant.

Reply as data

{
  "buyCurrency": "USD",
  "sellCurrency": "GBP",
  "amount": "1000.00",
  "fixedSide": "SELL",
  "corporateReference": "CORP-8842",
  "indicative": true,
  "quoteCreated": false,
  "dashboardUrl": "https://portal.sokin.com/v2/transfer/currency-exchange"
}

`create_fx_quote`

Create FX Quote · not read-only, not destructive · touches an external
system

Mints a real, short-lived FX quote and reserves a settlement draft for it.
Called by the FX quote card's own "Get Quote" button after get_fx_quote
has rendered the empty card; do not call this directly, call get_fx_quote
first.

Unlike get_fx_quote's display step, this is a genuine write: every call
persists a real quote and calls a live external rate provider.

How long a quote lasts is decided by the provider that priced it, and
it can vary by roughly a factor of five between currency pairs. The window
this server requests (MIN_2, the longest option the API's own
FXValidityPeriod enum offers) is only a fallback that applies when a
provider declares no expiry of its own; a provider that returns its own
valid_until overrides it in either direction. In practice the two live
providers sit at opposite ends: one pins its quotes to exactly the
requested MIN_2 window, the other returns its own valid_until
(observed around ten minutes). Which provider prices a given pair is
resolved upstream and is not exposed in the response.

So the quote's own expiresAt is the only figure to trust, never the
requested window, and never a hardcoded assumption about how long a quote
lasts. Never call this speculatively or more than once for the same
request.

How the quote prices.

The FX fee (fxFees) is already inside sellAmount: the provider is
quoted on the amount net of the fee, so it is not charged on top of the
sell amount and not deducted again from the buy amount.

fxFees is denominated in the sell currency, whichever side is fixed.

fxRate is the all-in customer rate, buyAmount / sellAmount by
construction. Sell amount x fxRate approximates buyAmount with the
fee absorbed, but the rate is truncated to 6 decimals and that error
grows with the amount, so never recompute buyAmount from the rate.

buyAmount is the quote's locked buy leg and is the amount that settles.
The total debited is not stated by the quote: a conversion carries no
Sokin fee, but a reseller_fee, if one is given, is added on top.

The card shows the fee as
FX <fee> <sell currency>, included in the <sell amount> <sell currency> you sell,
in a Fees row that sits outside the live
quote panel so a reopened settled or settling card shows it too, and the text
result carries the same statement when fxFees is present and positive. The other shapes fxFees
can take are stated too, never silently dropped:

a zero fee: the card shows "no FX fee" and the text says
No FX fee applies; <buy amount> <buy currency> is the amount that settles.;

no fee at all (an empty fxFees): the card shows "none" and the text
carries no fee sentence;

a fee that is present but unreadable (not a finite, non-negative number):
the card shows the raw value with "(could not be read; check it before you
settle)", its "You get" hint says "The FX fee could not be read; check the
Fees line before you settle.", and the text says "The FX fee could not be
read from the quote; check the fee shown on the card before settling."
without claiming what settles.

Annotated

readOnlyHint: false, destructiveHint: false, idempotentHint:
false

: a genuine third state, distinct from a typical write. Additive (it
only ever creates a new quote and draft pair, never mutates or removes
anything) but not idempotent (each call mints a fresh quote and a fresh
idempotency key, even for identical arguments).

Hard-refused for any session that has not declared MCP UI support --
there is no card for such a session to show a quote in, so minting one
would be a real cost (a live provider call, a persisted record) with no
legitimate use:

Error: this session has not declared MCP UI support, so creating a real FX quote is refused here -- there is no card to display it in. Direct the user to the Sokin portal to get a live rate and execute a trade instead.

Parameter	Type	Required	Description
`buy_currency`	string	yes	ISO 4217 code being bought
`sell_currency`	string	yes	ISO 4217 code being sold
`amount`	string	yes	The amount of whichever side `fixed_side` names
`fixed_side`	`"BUY"` or `"SELL"`	no	Default `"SELL"`
`corporate_reference`	string	yes	Same resolution rule as `get_fx_quote`, mandatory for the same reason
`corporate_currency_account`	string	no	The account settlement would debit. Never sent to the quote-creation endpoint itself, only carried into the reserved draft for the later Settle call. When omitted, the corporate's own account in the sell currency is resolved automatically if there is exactly one match; with zero or several candidates, no account is reserved and the card renders with no Settle option
`reseller_fee`	string	no	Carried into the reserved draft only, never sent to the quote-creation endpoint
`beneficiary_external_reference`	string	no	Only needed if quote creation itself asks for one; some rate providers require it even though this quote never pays a beneficiary
`card_id`	string	no	Leave unset. Only the FX quote card passes it, so that a reopened card can still show this quote and whether it was settled (see `get_fx_quote`'s card status check). With it, the card is looked up first, from the store alone, and only a card with no quote on record or whose last quote expired with no settlement on record gets a new one. A card holding a live quote, already settled, possibly settling, or whose record was made for a different request gets no new quote and nothing is sent upstream (the error reads "no new quote was created from this card"), and a failure of that lookup is an error with nothing minted. The card's quote is then recorded with the settlement draft, and a failure there is reported like a failed draft registration ("could not be tracked"): a key that can be settled must be findable from its card. A `card_id` that is not a uuid is ignored, and the quote is simply not remembered

content, a sentence naming the quote and its real expiry, followed (when the quote carries an FX fee) by a sentence saying the fee is inside the sell amount and which amount settles:

Quote QT-88213 created: 1000.00 GBP -> 1187.40 USD at rate 1.18740. Expires at 2026-08-27T14:34:00+00:00 -- settle it before then, or ask for a fresh quote once it expires. The 2.50 GBP FX fee is included in the 1000.00 GBP sold; 1187.40 USD is the amount that settles.

structuredContent, flat, no data envelope:

Field	Type	Description
`quoteId`	string	Quote identifier, required by `settle_fx_quote`
`idempotencyKey`	string	Minted here, not an upstream field — the exact key `settle_fx_quote` requires
`currencyPair`	string	Sell/buy with a separator, e.g. `GBP/USD` — the V2 quote domain's format
`fxRate`	string	The quoted rate
`fixedSide`	string	Which side the amount was fixed on
`buyAmount`	string	Amount bought
`buyCurrency`	string	ISO 4217
`sellAmount`	string	Amount sold
`sellCurrency`	string	ISO 4217
`fxFees`	string	FX fee
`createdAt`	string	Normalized to UTC ISO-8601 with an explicit offset
`expiresAt`	string	The real expiry, normalized the same way. The only expiry to trust; provider-set, so it may be far longer or shorter than the requested window (see above)
`corporateCurrencyAccount`	string, or null	The resolved (or supplied) settlement account, or null if none could be resolved
`corporateCurrencyAccountDisplay`	string, or null	Currency + account number or IBAN the portal shows (e.g. `USD account 12345678`, `GBP IBAN GB33...`); falls back to `<currency> account (number unavailable)` when the account lookup fails or yields no identifier. Null when no settlement account resolved. This is what the card's "Settle from" row renders; the raw reference never appears there
`resellerFee`	string, or null	Echoed from the request, or null

Full response adds the upstream envelope's message field and the
quote's status (Pending, Created, Booked or Expired). The reverse direction matters too: idempotencyKey,
corporateCurrencyAccount, corporateCurrencyAccountDisplay and resellerFee are synthesized by this tool,
not upstream fields. They are absent from the full/raw payload and only
ever appear in the compact response.

Errors: a B2B API rejection (e.g. an invalid currency pair) surfaces as
a standard B2B API error. If the quote is minted upstream but the
server-side draft registration fails afterward (a store blip), this is
reported explicitly rather than as a bare failure:

Error: quote QT-88213 was created but could not be tracked -- it cannot be settled through this assistant. Do not report a usable quote to the user; ask for a fresh one via get_fx_quote.

With card_id, a card that already holds a live quote, is settled or
settling, or whose record was made for a different request is refused
before anything is sent upstream (the card then re-checks and shows its
real state):

Error: no new quote was created from this card -- it already holds a live quote, a conversion from it is already settled, a settlement of it may still be in progress, or it was made for a different request. Do not quote from this card again; the card shows its current state. For another conversion, call get_fx_quote to show a new card.

No other tool-local input validation beyond the standard schema checks, the
blank corporate_reference check and the capability refusal above.

Example

Request

{
  "name": "create_fx_quote",
  "arguments": {
    "buy_currency": "USD",
    "sell_currency": "GBP",
    "amount": "1000.00",
    "fixed_side": "SELL",
    "corporate_reference": "CORP-8842",
    "corporate_currency_account": "CCA-1001"
  }
}

Reply

Quote QT-88213 created: 1000.00 GBP -> 1187.40 USD at rate 1.18740. Expires at 2026-08-27T14:34:00+00:00 -- settle it before then, or ask for a fresh quote once it expires. The 2.50 GBP FX fee is included in the 1000.00 GBP sold; 1187.40 USD is the amount that settles. Settling from GBP account 12345678.

Reply as data

{
  "quoteId": "QT-88213",
  "idempotencyKey": "7c2e9b41-5a08-4d6f-b3c2-91ef0a4d8b52",
  "currencyPair": "GBP/USD",
  "fxRate": "1.18740",
  "fixedSide": "SELL",
  "buyAmount": "1187.40",
  "buyCurrency": "USD",
  "sellAmount": "1000.00",
  "sellCurrency": "GBP",
  "fxFees": "2.50",
  "createdAt": "2026-08-27T14:32:00+00:00",
  "expiresAt": "2026-08-27T14:34:00+00:00",
  "corporateCurrencyAccount": "CCA-1001",
  "corporateCurrencyAccountDisplay": "GBP account 12345678",
  "resellerFee": null
}

`settle_fx_quote`

Settle FX Quote · destructive, idempotent · touches an external system

Executes a previously created FX quote: moves real money between two of
the corporate's own currency accounts. Called by the FX quote card's own
Settle button after the user's explicit click; do not call this directly,
and never fabricate or reuse an idempotency key for a different quote. A
reused key returns the original conversion's outcome and ignores changed
arguments.

Hard-refused for any session that has not positively declared MCP UI
support. tools/list hides this tool from a client known to lack support
(it sent initialize without declaring it), but shows it when support is
unknown, for example to a client that never sent initialize or whose
24-hour record has lapsed. That listing is hygiene only. The real
enforcement is this check, which runs first, before any upstream call:

Error: this session has not declared MCP UI support, so real-money FX settlement is refused here. Direct the user to the Sokin portal to execute this trade instead.

Unlike the two payment pairs, this refusal applies here and to
create_fx_quote, and nowhere else. It backs up portal approval (see "What
the gate does not guarantee" below) rather than standing alone, and it keeps
any session from minting real quotes with no card to show them.

Parameter	Type	Required	Description
`idempotency_key`	string	yes	The key minted by `create_fx_quote` for this exact quote, its `idempotencyKey` field
`corporate_currency_account`	string	yes	Must match the quote the user reviewed
`quote_id`	string	yes	Must match the quote the user reviewed
`reseller_fee`	string	no	Must match the quote the user reviewed

Arguments are checked against the draft create_fx_quote reserved under
idempotency_key. Any mismatch is refused, never silently corrected.

Draft lifetime. The draft create_fx_quote registers is held for 24
hours, then the key is refused as unknown and a fresh quote is needed. That
window is deliberately much longer than a quote actually lives, for two
reasons worth knowing as an integrator:

Quote expiry is not enforced by that TTL. How long a quote stays
valid is decided by the provider that priced it (see create_fx_quote),
so no local timer could get it right. Settling a quote whose window has
passed reaches a real synchronous pre-check and comes back as

Error:
this quote could not be settled: <reason>

, the true reason, rather than
a misleading unknown-key refusal. Read the quote's own expiresAt, and
expect the expiry answer to come from the settle call.

A replay stays answerable. A settled key returns the original
conversion's outcome for 7 days after the settlement (the settled record
is kept that long), so a retry after a lost response is reported rather
than mistaken for a new settlement. After that the key is refused as
unknown and nothing is sent.

The card's memory. After a successful settlement this tool also
records, for 30 days, that the card the quote was made on was settled. It
finds the card from the key, so it takes no card id of its
own, and reads no user key: the card's user and request were stored with
the draft. The write is best-effort and never turns a settlement into an
error, and it is retried. A lost write is covered anyway: the card's attempt
record (below) names this key for 30 days, so the status check still
finds the settlement through the submitted record for the 7 days that
record is kept, and reads settling after that, and create_fx_quote
keeps refusing a new quote on the card meanwhile.

Before the request is sent (after the validate pre-check passes) this
tool records the attempt on the card, for 30 days, and removes it only on
a definite rejection (a 4xx). So after any ambiguous end -- a 5xx, a
timeout, any other failure, or the request being cut off mid-POST -- the
card keeps reading settling instead of offering the conversion again (see
get_fx_quote's card status check). If the attempt cannot be recorded,
nothing is sent: the claim is released and the answer is

Error: this quote
could not be settled: the attempt could not be recorded, so nothing was
sent. Try again in a moment.

The record does not block a same-key retry:
B2B returns the original instruction request for a repeated key.

While a settlement is in flight, the key is claimed for up to 10 minutes: a
second call on the same key during that time is refused as in-flight
rather than executed, and a definite rejection releases the claim
immediately so a corrected retry does not have to wait it out. Submitted
records themselves are kept for 7 days; the backend's own dedupe on the
key is permanent.

For an outcome check, prefer get_instruction_request over a repeat
settle_fx_quote call. It is a read, and it answers regardless of how
long ago the settlement happened.

Upstream deduplication. idempotencyKey is also sent on the wire, and
the transaction core dedupes on

(idempotencyKey, instructionType,
corporateCurrencyAccount)

. A replayed key returns the first request and
silently ignores changed values. That is the correctness layer; the gate
described here is an availability layer in front of it, which turns a
replay into an explicit, readable answer instead of a blind repeat.

What the gate does not guarantee. It constrains what can be submitted,
not who approved it. The model can hold a settleable key, so it can call
this tool directly rather than through the card's Settle button:

in create_fx_quote's reply, if the model calls that tool itself (MCP
has no widget-only channel through which the card could hold a secret);

in get_fx_quote(card_id=)'s quoted reply. That call returns the live
key, the quote id and the account in a normal, stored tool result, and the
server cannot tell the card asking from the model asking. So the Settle
click is not the only path to a settlement.

What stands between a model-initiated call and a conversion:

the arguments must byte-match the quote the card registered;

the session must have positively declared MCP UI support (the hard
refusal above);

the host's own confirmation prompt for destructive tools, which is
load-bearing, not decorative;

the real human control: portal approval. Every corporate has an
approval rule covering every instruction type this server can create
(payments, FX payments and FX conversions alike), matching instructions
that arrive through the MCP channel and needing one approval. So an
MCP-originated settlement is created but waits for approval in the Sokin
portal instead of executing; the card shows "Needs approval". Any of the
corporate's approvers can clear it, the submitting user included: it
guarantees the authorising step happens in a Sokin surface, not that a
second person checks it. The rule is per corporate, and anyone there who
can edit approval rules can deactivate it; the corporate's other rules then
apply.

This tool creates and submits an instruction request; it never approves or
completes one.

content on success:

FX conversion submitted: instruction request IR-FX-9911 for account CCA-1002. This is a submission receipt, not confirmation the conversion completed -- check get_instruction_request for its actual outcome.

structuredContent, a data envelope, the same shape the upstream
create-instruction-request call returns:

Field	Type	Description
`data.externalReference`	string	The instruction request reference. Pass to `get_instruction_request` for its actual outcome

Full response adds the upstream envelope's message field back.

Tool-specific errors:

Condition	Message
Session not MCP-UI-capable	`Error: this session has not declared MCP UI support, so real-money FX settlement is refused here. Direct the user to the Sokin portal to execute this trade instead.`
Empty `idempotency_key`	`Error: idempotency_key must not be empty.`
Unknown key (never registered, or expired)	`Error: unknown idempotency key -- quotes are prepared via create_fx_quote, which mints the key and renders the review card. If a quote was lost, ask for a fresh one via get_fx_quote.`
Arguments do not match the reserved draft	`Error: these arguments do not match the quote the user reviewed under this idempotency key. Only the exact reviewed quote can be settled -- for a different conversion, get a fresh quote.`
Another settlement for the same key is already in flight	`Error: another settlement attempt for this exact quote is already being processed -- its outcome is not yet known. Do not retry immediately; check get_instruction_request shortly, or wait a moment before trying again.`
Same key already settled	Not an error: returns the original `get_instruction_request` result again, prefixed "This quote was already submitted, no new conversion was created."
Quote fails a synchronous pre-check (e.g. expired)	`Error: this quote could not be settled: <reason>.` Adds `Ask for a fresh quote via get_fx_quote.` when the failure category is the quote itself
B2B API rejects with 4xx	Standard B2B API error shape. The reservation is released, so a corrected retry does not have to wait out its TTL
B2B API fails with 5xx, or times out, or the reply to the create call cannot be read	`Error: the settlement submission's outcome is unknown (API error <status>: <message>, or "the response could not be read") -- it may or may not have been accepted. Do not report this conversion as settled or as failed, and do not retry immediately; check the account's recent instruction requests first.` The reservation is deliberately kept, not released, so a blind retry cannot double-submit, and the card's attempt record (written before the request) stays, so the card keeps reading `settling` after the reservation lapses

Example

Request

{
  "name": "settle_fx_quote",
  "arguments": {
    "idempotency_key": "7c2e9b41-5a08-4d6f-b3c2-91ef0a4d8b52",
    "corporate_currency_account": "CCA-1001",
    "quote_id": "QT-88213"
  }
}

Reply

FX conversion submitted: instruction request IR-FX-9911 for account CCA-1001. This is a submission receipt, not confirmation the conversion completed -- check get_instruction_request for its actual outcome.

Reply as data

{"data": {"externalReference": "IR-FX-9911"}}

`create_fx_payment_instruction`

Create FX Payment Instruction · not read-only, not destructive, not idempotent · touches an external system

Prepares an FX payment for a human to review. It submits nothing.
Despite the name, no payment exists after this call and no money has
moved. Converts and pays a beneficiary in one motion against a quote this
tool mints for you, via POST /instruction-requests/fx-payment on submit.
This follows the same prepare/submit-with-draft-gate pattern as
create_payment_instruction, combining the account/beneficiary side of a
payment with the quote side of an FX conversion.

This tool takes no quote_id. It takes the raw pricing inputs
(buy_currency, sell_currency, amount, fixed_side,
corporate_reference) and mints a real, live quote itself, via the same FX
quote adapter create_fx_quote uses (POST /fx/quotes/), with the
beneficiary passed straight through as the quote's
beneficiaryExternalReference. A quote minted by an earlier, separate call
could not reliably reach a non-UI calling model (that depends on
ui/update-model-context), and the B2B API only checks a quote's existence,
expiry, corporate and sell currency at instruction time, so minting it here
is equivalent and needs no second call.

Minting the quote here is a genuine write, exactly like create_fx_quote:
every call to this tool persists a real quote and calls a live external
rate provider. Never call it speculatively or more than once for the same
request. Call it directly, with no get_fx_quote step first, whenever the
user wants to pay an external beneficiary with a conversion, and only once
they are ready to actually prepare the payment; the figures it returns (fees,
the amount the beneficiary receives) are what the user reviews. get_fx_quote
solves a different problem, converting between the corporate's own accounts,
and on a non-UI client it shows no rate at all: it returns the request echo
plus a link to the Sokin portal, which is the path for a non-UI own-account
conversion.

What it actually does, in order: mints the quote as described above; runs
the FX-payment validate dry run (the same instructionType: FXPayment the
real create uses, carrying the account, beneficiary and the freshly-minted
quote) so the review can show server-computed fees and catch an expired
quote, an unusable beneficiary or an insufficient balance in one round
trip; looks up the source account and the beneficiary for display (two
read-only calls); mints an idempotency key server-side; and registers the normalized
draft against that key. When the calling session has declared MCP UI
support it also renders its own MCP UI embed
(ui://sokin-mcp/fx-payment-review), a review card with Approve and
Cancel. Only the user's Approve click there submits, by invoking
submit_fx_payment_instruction from inside the widget. This tool renders
its own interactive card when one is available, so it should not be
followed with the visualize tool.

Annotated as a write. This tool makes four upstream calls: the FX
quote mint (a persisted quote record and a real call to an external rate
provider, upstream of anything a human has approved), the FX-payment
validate dry run, and the account and beneficiary lookups. The last three
are side-effect-free; the mint is not, so the tool carries
readOnlyHint: false, idempotentHint: false, like create_fx_quote, and
hosts ask before running it. Every preparing call mints a new quote, even
one whose dry run then fails and produces no approvable draft, so never call
it speculatively. Its own draft registration remains gate bookkeeping, not a
business write against the corporate's money, same as
create_payment_instruction's.

The dry run declares the same instruction type as the real create, so the
beneficiary is checked before the user is asked to approve: that it
exists, that it is not an internal beneficiary (which this instruction
type does not accept), that it can receive the quote's buy currency, and
that it passes verification of payee. A beneficiary problem is therefore
reported by this tool rather than surfacing after the Approve click.

One thing this tool still cannot guarantee is that the quote survives to
settlement. The backend re-checks quote validity at the moment a human
approves the instruction in the Sokin portal, which is a human-paced wait,
so a quote valid here can still expire before then. The portal then refuses
the approval itself, and the approver either rejects the instruction
(Failed upstream with an Approval rejected: prefix, which this server
relabels Rejected) or refreshes the quote, which fails the original
instruction with failureReason FX quote expired at approval (shown as
Failed, not relabelled). Either way it arrives through the instruction's
status, not as an error from either tool in this pair. The same applies to
an FX conversion submitted by settle_fx_quote, whose quote is usually far
shorter-lived than a human approval.

MCP UI support changes only which text this tool shows you, not whether
it will run -- the identical reasoning create_payment_instruction
documents at length above. In short: no capability check refuses this
tool, the session's declared capability only
selects the wording (widget-flow text vs. an idempotency key spelled out
for chat confirmation), and structuredContent carries idempotencyKey
either way.

Parameter	Type	Required	Description
`corporate_currency_account`	string	yes	Source account reference from `list_accounts`
`beneficiary_reference`	string	yes	The payee, from `list_beneficiaries`. Must already exist — if it doesn't, create it first with `create_beneficiary` (needs a one-time emailed code). Passed to the quote provider (as `beneficiaryExternalReference`) as well as the payment itself
`buy_currency`	string	yes	ISO 4217 code being bought (e.g. `"USD"`)
`sell_currency`	string	yes	ISO 4217 code being sold (e.g. `"GBP"`)
`amount`	string	yes	The amount of whichever side `fixed_side` names
`fixed_side`	`"BUY"` or `"SELL"`	no	Which side `amount` refers to. Default `"SELL"`
`corporate_reference`	string	no	The corporate to quote for. Required in practice; call `list_corporates` first if the user hasn't named one. Omitting it does not auto-resolve for a typical caller -- the upstream API only fills it in when the token itself already identifies one specific corporate (a corporate's own self-service token, or a reseller token delegating as that one corporate), never for a plain reseller token. Used only for minting the quote, never sent to the payment itself
`reseller_fee`	string	no	Plain decimal string, zero or greater
`sender_reference`	string	no	Shown to the recipient, max 18 characters
`payment_purpose`	enum	no	Same 22 declared values as `create_payment_instruction`; see the enums appendix. An unrecognized value is rejected by schema validation, not sent
`status_check_key`	string	no	Leave unset. Only the review widget passes it, with the idempotency key it was given, to ask whether its draft was already submitted. With it the tool mints no quote and makes one read-only call, for the account; see "Status check" below

content, when MCP UI is declared -- a not-submitted notice: see the Example below.

content, when MCP UI is not declared (or unknown) -- unlike
create_payment_instruction, submit's arguments here are NOT the same as
create's (submit needs quote_id, which is not one of create's own
parameters), so the idempotency key, the quote_id, and the real
server-computed fee numbers are all spelled out in the text -- none of it
can rely on structuredContent, which a non-UI client is not guaranteed to
show the model: see the Example below.

When the underlying dry run fails outright (either branch, same text):

The FX payment could not be validated: <reason>. Nothing has been submitted.

When the quote itself has expired or is unknown by the time the dry run
runs, or does not fit the payment (the validate response's errorCategory
is "quote"). Besides a quote that lapsed, this happens when
corporate_reference belongs to a different corporate than the account, or
sell_currency is not the account's currency; preparing again with the same
arguments fails the same way and mints another quote:

Error: the quote minted for this request is no longer valid (<reason>). Call create_fx_payment_instruction again to mint a fresh one. Nothing has been submitted.

Despite the leading word Error:, none of the three texts above set
isError: true -- they are reports from the validation dry run, delivered
through the normal (non-error) result channel, exactly like
create_payment_instruction's own validation-failure text. See the top-level
Errors section's note on this.

structuredContent: this tool builds its own payload, no
{"data": ...} envelope:

Field	Type	Description
`draft`	object	The normalized FX payment exactly as it would be submitted: `corporate_currency_account`, `beneficiary_reference`, `quote_id`, `reseller_fee`, `sender_reference`, `payment_purpose`. No `amount`, `buy_currency`, `sell_currency`, or `fixed_side` field -- the ledger legs derive entirely from the quote, and the pricing inputs exist only to mint that quote, never to submit the payment. `quote_id` here is the id of the quote THIS call minted for you, not one you supplied -- pass it through unchanged to `submit_fx_payment_instruction`
`currency`	string, or null	The source account's currency, for the card's debit and fee rows. Null when the account lookup failed; display only, it never blocks a valid draft
`buyCurrency`	string	The beneficiary's currency (this call's own `buy_currency` parameter, normalized), labelling what the beneficiary actually receives. Always present, unlike `currency` -- there is no lookup that can fail
`quoteExpiresAt`	string, or null	The minted quote's normalized expiry timestamp, straight from the adapter -- drives the card's countdown and disables Approve once it passes. Null only if the upstream response omitted it
`quoteCreatedAt`	string, or null	The minted quote's normalized creation timestamp, paired with `quoteExpiresAt` for the countdown's total span
`validation`	object	The FX-payment validate dry-run verdict (`instructionType: FXPayment`), same envelope shape as `validate_payment_instruction`'s, including a resolved `feeBreakdown`
`idempotencyKey`	string, or null	Server-minted, registered to this exact draft. Null when validation failed
`duplicateWarning`	object	Present only when an identical draft was submitted within the duplicate window: `instructionRequestReference` and `submittedAt`
`quoteRequest`	object	The pricing arguments this draft was prepared from, under the tool's own parameter names: `buy_currency`, `sell_currency`, `amount`, `fixed_side`, `corporate_reference`. Absent on the validation-failure branch. The review card needs these to rebuild this tool's required arguments for its status check

duplicateWarning is not an error, with the same semantics as
create_payment_instruction's: when a widget is present it renders an
already-submitted card with no Approve button either way, the block lasts
for the same duplicate window, and a deliberate second identical payment
inside it needs a distinguishing sender_reference.

Full response adds: nothing. This tool assembles its own payload.

Errors: input validation (blank corporate_currency_account or
beneficiary_reference, a malformed reseller_fee, an over-length
sender_reference) is checked and rejected with isError: true before
the quote is minted, deliberately -- a blank reference or a malformed fee
must never burn a real, provider-priced quote's validity window for
nothing. A B2B API rejection while minting the quote itself (an invalid
currency pair, for instance) surfaces as a standard B2B API error. Unlike
create_fx_quote, a failure registering the draft after the quote has
already been minted (a store blip) is not given its own explicit message
here -- it falls through to the generic unexpected-failure fallback, so a
real, live, unexpired quote can in that rare case be reported to the caller
as an opaque failure with no reference to hold onto.

Draft lifetime: pending drafts expire after 24 hours; submitted records
are kept for 7 days, after which a replayed key is refused as unknown and
nothing is sent (the backend's own dedupe on the key is permanent). This
draft has its own namespace in the server's session store, separate from a
plain payment's draft, so an FX payment and a plain payment can never
collide on the same idempotency key.

Status check (status_check_key). The same mechanism as
create_payment_instruction's, with the same response fields and states.
It is answered before the quote is minted, so reopening a conversation
costs no provider quote on a host that replays the stored result. (A host
that remounts the card without it makes the card fall back to a full
re-prepare, which does mint one.) The card rebuilds this tool's arguments from
the replayed draft (without quote_id) plus quoteRequest, and the
server matches them against the draft's duplicate identity. That identity
leaves out quote_id, because every prepare mints a fresh one and two
prepares of the same payment would otherwise never match.

Example

Request

{
  "name": "create_fx_payment_instruction",
  "arguments": {
    "corporate_currency_account": "CCA-1001",
    "beneficiary_reference": "BEN-3301",
    "buy_currency": "USD",
    "sell_currency": "GBP",
    "amount": "100.00",
    "fixed_side": "SELL",
    "corporate_reference": "CORP-8842",
    "sender_reference": "INV-4471"
  }
}

Reply, on a client with cards — a not-submitted notice:

FX payment prepared and validated -- awaiting the user's confirmation in the review widget. Nothing has been submitted; do not report this payment as made, and do not call submit_fx_payment_instruction yourself.

Reply, on a client without cards — the figures and both references are
spelled out in the text, because there is no card to carry them:

FX payment prepared and validated -- nothing has been submitted yet. Total debit 100.50 (0.50 Sokin fee, 0.00 reseller fee); beneficiary would receive 125.00 (GBP debited, beneficiary receives USD). idempotency key: 9c21ab4f-... . quote_id: FXQ-1a2b3c... . Read these figures back to the user and get their explicit approval. Only after they approve, call submit_fx_payment_instruction with this idempotency_key, this quote_id, and the same corporate_currency_account, beneficiary_reference, reseller_fee, sender_reference, and payment_purpose you used here -- it does not take buy_currency, sell_currency, amount, fixed_side, or corporate_reference; those only mint the quote. Never submit without that approval, and never tell the user the payment was made until submit_fx_payment_instruction succeeds -- it will still need approval in the Sokin portal afterward.

Reply as data

{
  "draft": {
    "corporate_currency_account": "CCA-1001",
    "beneficiary_reference": "BEN-3301",
    "quote_id": "FXQ-1a2b3c",
    "reseller_fee": null,
    "sender_reference": "INV-4471",
    "payment_purpose": null
  },
  "currency": "GBP",
  "buyCurrency": "USD",
  "quoteCreatedAt": "2026-09-16T10:02:00+00:00",
  "quoteExpiresAt": "2026-09-16T10:12:00+00:00",
  "idempotencyKey": "9c21ab4f-7c4e-4a2b-9f31-6d0e2a5b8c14",
  "quoteRequest": {
    "buy_currency": "USD",
    "sell_currency": "GBP",
    "amount": "100.00",
    "fixed_side": "SELL",
    "corporate_reference": "CORP-8842"
  }
}

`submit_fx_payment_instruction`

Submit FX Payment Instruction · destructive, idempotent · touches an
external system

Submits a prepared FX payment. When the calling session declared MCP UI
support, this tool is invoked by the FX payment review widget after the
user's explicit Approve, and is not meant to be called directly in that
case. When it did not, create_fx_payment_instruction's own text hands
back the idempotency key and instructs the calling model to get the user's
explicit approval in chat first -- calling this tool directly at that point
is the intended path, not a bypass; there is no separate capability check
here that would refuse it. Either way, always call
create_fx_payment_instruction first -- it mints the quote and the key
this tool requires, and renders the widget when one is available.

Moves real money: converts and pays a beneficiary in one motion via

POST
/instruction-requests/fx-payment

, and cannot be cancelled once submitted.
Only accepts an idempotency_key minted by create_fx_payment_instruction,
and only with arguments identical to the draft the user reviewed. A reused
key with the same draft returns the original payment's state; a reused key
with different values is refused.

Parameter	Type	Required	Description
`idempotency_key`	string	yes	The key minted by `create_fx_payment_instruction` for this exact draft
`corporate_currency_account`	string	yes	Must match the reviewed draft
`beneficiary_reference`	string	yes	Must match the reviewed draft
`quote_id`	string	yes	Must match the reviewed draft -- this is the id of the quote `create_fx_payment_instruction` minted for you, from its `draft.quote_id` field, not a value you choose
`reseller_fee`	string	no	Must match the reviewed draft
`sender_reference`	string	no	Must match the reviewed draft
`payment_purpose`	enum	no	Must match the reviewed draft

content on success:

FX payment submitted: instruction request IR-FXPayment-77 from CCA-1 to BEN-1. This is an instruction-request reference, not a completed payment -- it now needs human approval in the Sokin portal before it is processed. Check the outcome via get_instruction_request.

The approval clause is stated unconditionally on purpose, even though a
corporate can deactivate the rule (see settle_fx_quote's "What the gate
does not guarantee" section): this text errs toward over-warning rather
than under. The review
card, when one is present, tracks the instruction's actual progress through
that approval step and renders it once the backend reports it; a non-UI
client gets the same information from get_instruction_request.

structuredContent, {"data": {"externalReference": ...}} on a fresh
submission (the same single-field shape submit_payment_instruction
returns, from the create endpoint's own response model, which carries only
externalReference); on a replay of an already-submitted draft, the same
get_instruction_request shape (externalReference, status,
createdInstructionReference, failureReason, errorCategory) instead of
re-posting.

Full response adds: the envelope's message field on a fresh
submission; nothing further on the replay branch, which already passes
message through in compact mode.

A malformed upstream response is a hard error, the same discipline as
submit_payment_instruction: a 202 whose body lacks externalReference
is rejected as a synthesized 502 reading "API returned an unexpected
response shape for the FX payment submission -- whether it was accepted is
unknown; check get_instruction_request before retrying." rather than being
rendered as a false success.

Tool-specific errors: the same draft-gate outcome set
submit_payment_instruction lists (unknown key, submitted-draft mismatch,
pending-draft mismatch, duplicate blocked in both its in-flight and
already-submitted variants), over this pair's own draft namespace, plus the
same pre-POST client-acquisition release guard: a failure acquiring the
upstream client between the gate's reservation and the real POST is a
definite non-submission and releases the reservation, gated on the outcome
having actually been a clear-to-submit verdict so a stray release can never
delete a live duplicate block for a payment that already exists.

Example

Request

{
  "name": "submit_fx_payment_instruction",
  "arguments": {
    "idempotency_key": "9c21ab4f-7c4e-4a2b-9f31-6d0e2a5b8c14",
    "corporate_currency_account": "CCA-1001",
    "beneficiary_reference": "BEN-3301",
    "quote_id": "FXQ-1a2b3c",
    "sender_reference": "INV-4471"
  }
}

Reply

FX payment submitted: instruction request IR-FXPayment-77 from CCA-1001 to BEN-3301. This is an instruction-request reference, not a completed payment -- it now needs human approval in the Sokin portal before it is processed. Check the outcome via get_instruction_request.

Reply as data

{"data": {"externalReference": "IR-FXPayment-77"}}

`list_beneficiaries`

List Beneficiaries · read-only · touches an external system

Searches and browses existing payees. Its primary use is checking whether a
payee already exists before creating one with create_beneficiary — the API
has no duplicate detection on create, and a payee's displayName, entity
type, country, and address are immutable afterwards (only destination and
identity details are updatable via update_beneficiary; there is no delete
tool), so this check is what stands between the user and a duplicate payee.

Parameter	Type	Required	Description
`corporate_reference`	string	no	The corporate to list for. Required in practice
`search`	string	no	Text to match against the display name. Omit to list all
`search_mode`	`"contains"` or `"starts_with"`	no	How `search` matches. Default `"contains"`
`limit`	integer	no	Max per page
`next_token`	string	no	Cursor from the previous page
`page`	integer	no	Not supported; accepted only to reject it clearly
`offset`	integer	no	Not supported; accepted only to reject it clearly

content, a markdown table: see the Example below.

structuredContent, envelope {"data": [...], "pagination": {...}},
each item:

Field	Type	Description
`externalReference`	string	The beneficiary reference
`displayName`	string	Display name
`entityType`	string	`individual` or `company`
`countryCode`	string	ISO country code
`destinations`	array	Each entry `{currencyCode, paymentRail}`
`status`	string	`active` or `deleted`

Each distinct (currency, rail) pair is kept rather than deduped to a bare
currency list. A beneficiary reachable in GBP over both faster_payments
and swift differs in settlement speed and cost, and collapsing that would
lose the distinction.

Full response adds: isInternal, supportedRails, createdAt,
version, the individual / company detail objects, address, and the
complete destination payloads — routing codes, account numbers, financial
institution details, validationStatus, autodepositEnrolled. It also adds
the envelope's message field (the literal "Success."). One field is
withheld even here: the e-Transfer securityAnswer (the answer a recipient
must give to claim a transfer — credential-shaped, so never returned).

Validation errors:

Error: page/offset pagination is not supported here. Use limit and next_token instead.

Example

Request

{
  "name": "list_beneficiaries",
  "arguments": {"corporate_reference": "CORP-8842", "search": "fab", "search_mode": "contains"}
}

Reply

2 beneficiaries:

Reference	Name	Type	Country	Currencies (rails)	Status
BEN-3301	Fabrikam GmbH	company	DE	EUR (sepa/swift)	active
BEN-3302	Jane Okafor	individual	GB	GBP (faster_payments)	active

Reply as data

{
  "data": [
    {
      "externalReference": "BEN-3301",
      "displayName": "Fabrikam GmbH",
      "entityType": "company",
      "countryCode": "DE",
      "destinations": [
        {"currencyCode": "EUR", "paymentRail": "sepa"},
        {"currencyCode": "EUR", "paymentRail": "swift"}
      ],
      "status": "active"
    },
    {
      "externalReference": "BEN-3302",
      "displayName": "Jane Okafor",
      "entityType": "individual",
      "countryCode": "GB",
      "destinations": [{"currencyCode": "GBP", "paymentRail": "faster_payments"}],
      "status": "active"
    }
  ],
  "pagination": {"nextToken": null, "previousToken": null, "totalItems": 2, "hasMore": false}
}

`get_beneficiary`

Get Beneficiary · read-only · touches an external system

One payee's full details by beneficiary id. Where list_beneficiaries
collapses each payee to its (currency, rail) pairs, this returns every
destination's actual account details — account numbers, routing/institution
data, e-Transfer email, crypto wallet address, or target corporate reference —
plus each destination's validationStatus.

Parameter	Type	Required	Description
`beneficiary_id`	string	yes	The payee's `externalReference` from `list_beneficiaries`
`corporate_reference`	string	no	The corporate this payee belongs to. Required in practice

content — a header line, a destinations table, and the creation date:

Acme Ltd -- company, GB, active

Currency	Rail	Validation	Account
GBP	faster_payments	matched	12345678
CAD	e_transfer	not_validated	payee@example.com

Created 2026-01-01T00:00:00Z.

A payee with status deleted gets an explicit trailing line: it cannot
receive payments.

structuredContent — envelope {"data": {...}}:

Field	Type	Description
`externalReference`	string	The beneficiary reference
`displayName`	string	Display name
`entityType`	string	`individual` or `company`
`countryCode`	string	ISO country code
`status`	string	`active` or `deleted`
`isInternal`	boolean	Whether this is a Sokin-to-Sokin payee
`destinations`	array	Full per-method payloads: `currencyCode`, `paymentRail`, `validationStatus`, and the method's own account fields. Bank-account destinations carry their stored snake_case keys (e.g. `account_number`, `institution`); e-Transfer and crypto destinations use camelCase
`individual` / `company`	object	Identity details — only the one matching `entityType`, and only when set
`address`	object	Payee address, when set
`createdAt`	string	Creation timestamp

Two upstream fields never reach the compact response: supportedRails,
because the details endpoint always returns it as [] (rail availability
lives in destinations[].paymentRail instead), and version, an internal
concurrency counter. For an e-Transfer destination without auto-deposit the
security question is returned but the security answer never is — it
is what the recipient must give to claim the transfer.

Full response adds: the envelope's message, supportedRails (always
empty here), version, and the raw destination payloads — minus the
e-Transfer securityAnswer, which is withheld even from the full response
(credential-shaped: it is the answer a recipient must give to claim a
transfer).

Validation errors:

Error: beneficiary_id must not be empty.

That reference is not available on this account. Check BOTH beneficiary_id (the Reference column from list_beneficiaries) and corporate_reference (the value list_corporates returned), and retry. If the reference is correct, this account may not have access to it.

— one rendering for every reference failure: an unknown payee, an unknown corporate, a corporate belonging to someone else, or a permission denial. It names both candidate arguments and never which one upstream rejected. It does not tell an unknown corporate apart from an unknown payee: upstream 404s a corporate reference that does not exist but 403s one that exists and is foreign, so the distinction would answer "does that corporate exist".

Example

Request

{"name": "get_beneficiary", "arguments": {"beneficiary_id": "BEN-3301", "corporate_reference": "CORP-8842"}}

Reply

Fabrikam GmbH -- company, DE, active

Currency	Rail	Validation	Account
EUR	sepa	matched	DE89370400440532013000
EUR	swift	not_validated	DE89370400440532013000

Created 2026-02-11T09:20:00Z.

Reply as data

{
  "data": {
    "externalReference": "BEN-3301",
    "displayName": "Fabrikam GmbH",
    "entityType": "company",
    "countryCode": "DE",
    "status": "active",
    "isInternal": false,
    "destinations": [
      {
        "currencyCode": "EUR",
        "paymentRail": "sepa",
        "validationStatus": "matched",
        "account_number": "DE89370400440532013000",
        "institution": "Commerzbank AG"
      },
      {
        "currencyCode": "EUR",
        "paymentRail": "swift",
        "validationStatus": "not_validated",
        "account_number": "DE89370400440532013000",
        "institution": "Commerzbank AG"
      }
    ],
    "company": {"registeredName": "Fabrikam GmbH"},
    "address": {"city": "Berlin", "countryCode": "DE"},
    "createdAt": "2026-02-11T09:20:00Z"
  }
}

`get_beneficiary_schema`

Get Beneficiary Schema · read-only · touches an external system

The fields a new payee needs for a given payment method, currency, and country
— names, types, requiredness, and allowed values — for collecting details
before creating a payee. Field names are dot-paths into the beneficiary
payload (e.g. address.city, bankAccount.accountNumber).

Payment method here is a different taxonomy from the payment rails
shown in list_beneficiaries destinations. Every rail belongs to exactly one
method: e_transfer → e_transfer, internal → sokin_internal, pix →
virtual_account, the on-chain networks (base, tron, ethereum,
polygon, solana) → crypto, and every other rail (faster_payments,
sepa, swift, ach, eft, …) → bank_account.

Parameter	Type	Required	Description
`payment_method`	`"bank_account"` \| `"e_transfer"` \| `"virtual_account"` \| `"sokin_internal"`	yes	See the rail-to-method mapping above. The taxonomy's fifth method, `crypto`, is deliberately not an accepted value — the upstream endpoint cannot describe crypto payees yet (its currency validation caps `currencyCode` at 3 characters; the only crypto currencies are the 4-character stablecoin codes USDC/USDT), so there is no schema to fetch. Crypto payees skip the schema lookup: `currency_code` USDC/USDT, `payment_rail` = the on-chain network, wallet address in the crypto object's `walletAddress`
`currency_code`	string	unless `sokin_internal`	ISO 4217 currency the payee is paid in
`country_code`	string	unless `sokin_internal`	ISO 3166-1 alpha-2 country of the payee's account
`entity_type`	`"individual"` \| `"company"`	unless `sokin_internal`	Payee entity type
`autodeposit_enrolled`	`"true"` \| `"false"` \| `"unknown"`	no	e-Transfer only: whether the recipient email has Interac auto-deposit. Passing `"false"` or `"unknown"` makes the security question/answer fields required; omitting the parameter behaves like `"true"` (they stay optional), so pass `"unknown"` rather than omitting when enrolment hasn't been checked
`corporate_reference`	string	no	The corporate the payee will be created under. Required in practice

content — a markdown table:

Beneficiary schema for bank_account / GBP / GB / company -- 4 fields:

Field	Type	Required	Notes
displayName	string	yes	length 1-100
bankAccount.accountNumber	string	only for faster_payments
entityType	enum	yes	one of: individual, company
eTransfer.securityQuestion	string	no	conditional on eTransfer.email; fixed value: Confirm the agreed passphrase

A field marked "only for rails" is required just for those payment rails
(whether upstream expressed that via requiredForPaymentRails or via
rail-gating conditions, as with bankAccount.institution.branchCode on
SWIFT-plus-local corridors); a field marked "conditional on X" only applies
once X is answered. On a multi-rail corridor, an enum value noted
"value only with rails" is accepted just for those rails — e.g. on the
three-rail GBP/GB corridor, bankAccount.accountNumberType renders

one of: account_number, iban; account_number only with chaps,
faster_payments, swift; iban only with swift

, so a faster_payments payee
must use account_number. Single-rail corridors carry no conditions and
render without the extra notes.

structuredContent — envelope {"data": {"condition": {...}, "fields": [...]}}.
condition echoes the resolved query context (currencyCode, entityType,
countryCode, paymentMethod). Each field object always carries name,
fieldType (string / integer / boolean / date / enum), and
isRequired (a non-nullable boolean upstream, default true — never absent),
plus — only when set, the upstream route excludes nulls — min, max,
allowedValues, requiredForPaymentRails, conditions, visibility,
conditionalOn, revalidateOn, fixedValue.

Full response adds: the envelope's message, and regional — which the
upstream processor never populates on this endpoint today.

Validation errors:

Error: currency_code, country_code, entity_type required for payment_method 'bank_account' (only sokin_internal can omit them).

— mirrors the API's own rule; for sokin_internal the API defaults the entity type to company.

A payment_method outside the four accepted values (including crypto — see the parameter table) fails MCP argument-schema validation before the tool body runs.

That reference is not available on this account. Check corporate_reference (the value list_corporates returned), and retry. If the reference is correct, this account may not have access to it.

— corporate resolution runs upstream before the schema lookup, and corporate_reference is this tool's only reference argument, so the neutral rendering can name it without disclosing which failure it was.

A combination the corporate has no payment rails for is rejected upstream:
API error (400): No payment rails for GBP+US and bank_account.

Example

Request

{
  "name": "get_beneficiary_schema",
  "arguments": {
    "payment_method": "bank_account",
    "currency_code": "GBP",
    "country_code": "GB",
    "entity_type": "company",
    "corporate_reference": "CORP-8842"
  }
}

Reply

Beneficiary schema for bank_account / GBP / GB / company -- 4 fields:

Field	Type	Required	Notes
displayName	string	yes	length 1-100
bankAccount.accountNumber	string	only for faster_payments
bankAccount.sortCode	string	yes
entityType	enum	yes	one of: individual, company

Reply as data

{
  "data": {
    "condition": {
      "currencyCode": "GBP",
      "entityType": "company",
      "countryCode": "GB",
      "paymentMethod": "bank_account"
    },
    "fields": [
      {"name": "displayName", "fieldType": "string", "isRequired": true, "min": 1, "max": 100},
      {
        "name": "bankAccount.accountNumber",
        "fieldType": "string",
        "isRequired": true,
        "requiredForPaymentRails": ["faster_payments"]
      },
      {"name": "bankAccount.sortCode", "fieldType": "string", "isRequired": true},
      {
        "name": "entityType",
        "fieldType": "enum",
        "isRequired": true,
        "allowedValues": ["individual", "company"]
      }
    ]
  }
}

`validate_beneficiary`

Validate Beneficiary · writes (non-destructive, idempotent) · touches an external system

Verifies payee account details before creating a payee, probes an e-Transfer
email's auto-deposit enrolment, or re-checks an existing payee's
destinations. create_beneficiary's docstring requires the applicable
pre-create mode; the existing-payee mode is also what makes a fresh (or
just-patched) EUR/SEPA payee payable — the API blocks payments to
EUR/SEPA destinations whose stored status is anything other than
matched/close_match/check_not_possible (not_validated, no_match,
and invalid all block). Exactly one verification mode per call:

Mode	Fields	What runs
Existing payee	`beneficiary_id`	Re-validates every destination and persists each refreshed `validationStatus` — the reason this tool is not read-only. Convergent: re-running re-derives the same statuses. Corridor-gated per destination: e-Transfer gets a DDR enrolment probe, internal and non-EUR bank destinations come back `not_validated` ("not applicable"), GBP local rails get CoP where reseller-enabled, EUR gets VoP
e-Transfer probe	`email`	Interac auto-deposit (DDR) check. No persistence
IBAN name check	`iban` + `bic` + `account_name`	Verification of Payee — runs on any format-valid IBAN regardless of country; verdicts are `matched` / `close_match` / `no_match` / `check_not_possible`, never `not_validated` in this mode. A malformed IBAN or BIC comes back `invalid`
UK CoP	`sort_code` + `account_number` + `account_name`	Confirmation of Payee on GBP local rails — only where enabled for the reseller; otherwise `not_validated`

Parameter	Type	Required	Description
`beneficiary_id`	string	mode 1	The payee's `externalReference` from `list_beneficiaries`
`email`	string	mode 2	Recipient email for the auto-deposit check
`iban`	string	mode 3	IBAN (15–34 chars)
`bic`	string	mode 3	BIC/SWIFT, 8 or 11 chars (upstream uppercases)
`account_name`	string	modes 3, 4	The account holder name to verify
`sort_code`	string	mode 4	UK sort code, 6 digits — spaces/hyphens tolerated
`account_number`	string	mode 4	UK account number, 8 digits
`corporate_reference`	string	no	The corporate to validate under. Required in practice

content — a worst-status-first summary line and a results table:

Close match only -- the name on record differs from the name supplied. Show the user both names and get their confirmation before going further.

Currency	Rail	Check	Status	Name on record	Details
		COP	close_match	J Okafor Ltd	Name is a close match

The summary wording is load-bearing: no_match/invalid render as NOT
verified; check_not_possible/not_validated render as NOT a pass (the
check did not run). A multi-check response's headline is prefixed
Worst of N checks: so a mixed payee never reads as "nothing ran". A matched
that includes a DDR result renders All checks passed. with a note that DDR
confirms auto-deposit enrolment, not the account name. Email-mode
responses render the enrolment result instead —
enrolled yes/no/unknown, registered/legal names when enrolled, whether
security Q&A is required, the matching autodeposit_enrolled value to pass to
get_beneficiary_schema, and that enrolment state's e-Transfer field list.

structuredContent — envelope {"data": {...}}:

Field	Type	Description
`isValid`	boolean	False only when some result is `no_match` or `invalid`. True does not mean verified — `check_not_possible` and `not_validated` still yield true
`results`	array	One entry per check: `validationType` (`FORMAT`/`VOP`/`COP`/`DDR`), `status`, and — when set — `currencyCode`, `paymentRail`, `details`, `actualName` (the name on record, on a CoP partial/close match)
`autodepositEnrolled`	boolean	Email mode only; absent when the check was inconclusive
`registrationName` / `legalName`	string	Email mode, only when enrolled
`securityQaRequired`	boolean	Email mode: whether the payee needs a security question/answer
`fields`	array	Email mode: the e-Transfer schema fields for that enrolment state (same shape as `get_beneficiary_schema`)

Full response adds: the envelope's message field only.

Validation errors:

Error: supply fields for exactly one verification mode: beneficiary_id (existing payee); email (e-Transfer auto-deposit); iban + bic + account_name (IBAN name check); or sort_code + account_number + account_name (UK Confirmation of Payee).

Error: the IBAN name check needs all of iban, bic and account_name.

Error: the UK Confirmation of Payee check needs all of sort_code, account_number and account_name.

No payee with id 'ben_missing' exists under this corporate -- check BOTH beneficiary_id ... and corporate_reference ... — unlike get_beneficiary, this tool distinguishes a missing corporate from a missing payee id; its corporate branch renders a fixed Corporate not found string rather than quoting the upstream message.

A 200 whose payload lacks results/isValid is reported as
API error (502) — "the result is unknown; do not report the details as
valid or invalid" — rather than letting a gateway artifact read as a verdict.

Example

Request

{
  "name": "validate_beneficiary",
  "arguments": {
    "sort_code": "04-00-75",
    "account_number": "12345678",
    "account_name": "Jane Okafor",
    "corporate_reference": "CORP-8842"
  }
}

Reply

Account name verified.

Currency	Rail	Check	Status	Name on record	Details
GBP	faster_payments	COP	matched	Jane Okafor	Name matches the account holder

Reply as data

{
  "data": {
    "isValid": true,
    "results": [
      {
        "validationType": "COP",
        "status": "matched",
        "actualName": "Jane Okafor",
        "details": "Name matches the account holder",
        "currencyCode": "GBP",
        "paymentRail": "faster_payments"
      }
    ]
  }
}

`create_beneficiary`

Create Beneficiary · writes (additive, NOT idempotent) · touches an external system

Creates a new payee, protected by an emailed one-time confirmation code
(OTP): one tool, called twice. The first call (no otp_code) dry-runs
the draft against POST /beneficiaries/batch-validation — an invalid draft
costs nothing, no email is sent — then attempts the create; if the corporate
requires OTP, the API emails the user a 6-character code and the tool
returns status otp_required. The second call repeats the same arguments
plus otp_code. For a corporate without the OTP requirement, the first call
creates immediately. Calling again without otp_code while any code is
outstanding for this user and action type — a resend of the same draft OR a
corrected draft after a typo'd one — returns status otp_resent instead:
upstream keeps ONE live code per user and action type and overwrites it on
every issue, so the text says any earlier code is void and to use the MOST
RECENT email.

There is no upstream duplicate detection on create: a repeated call
creates a second payee. Check list_beneficiaries first; the tool
deliberately adds no duplicate blocking of its own, only a 10-minute
in-flight claim so the same draft can't be POSTed twice concurrently.

The docstring requires a validate_beneficiary name check before
creating wherever the destination has one (IBAN → VoP, UK sort code → CoP,
e-Transfer → the email/auto-deposit probe; destinations with none: internal,
pix, crypto, and bank accounts with neither an IBAN nor UK sort-code details
— e.g. US ACH, CAD EFT), with a hard stop on
no_match/invalid/close_match until the user has seen both names. This
is an instruction to the calling model, not server-side enforcement: the
checks live in validate_beneficiary, and nothing stops a payee being
created without one. It
also instructs the model to run the beneficiary_id mode after creating
an EUR/SEPA payee: a new payee starts not_validated, and the API blocks
payments to EUR/SEPA destinations until a validation refreshes the stored
status.

The two-call state is held server-side, keyed by user and draft
fingerprint: the redeem call must be byte-identical
to the trigger call (including corporate_reference), or it is refused
before any network call. That byte-match is protection the API itself lacks —
upstream codes are scoped per user+action, not per payload. The gate also
tracks the newest trigger per (user, action type), mirroring upstream's
one-live-code rule: triggering a second draft of the same type supersedes
the first, whose redeem is then refused with an instruction to re-trigger —
without this, an older draft could silently spend the newer draft's code.

OTP mechanics (upstream): codes are 6 characters, single-use (consumed even
when the create then fails for another reason), expire after 10 minutes, max
5 emails per 15 minutes, and 5 wrong attempts temporarily blocks the
user's account including their Sokin portal login — the tool's error
wording forbids the model from guessing or retrying codes. Upstream keeps
one live code per user per action type (internal Sokin-to-Sokin payees
are tracked separately from all other rails): every new code email replaces
the previous code of the same type, so only the most recent email works —
including across different pending drafts of that type.

Parameter	Type	Required	Description
`display_name`	string	yes	Payee display name (1–255 chars)
`currency_code`	string	yes	ISO 4217; for crypto rails, the stablecoin code (USDC/USDT)
`payment_rail`	string	yes	e.g. `faster_payments`, `sepa`, `swift`, `eft`, `e_transfer`, `internal`, `pix`, `tron`. Corridor legality is checked upstream
`entity_type`	`"individual"` \| `"company"`	unless rail `internal`	Payee entity type
`country_code`	string	unless rail `internal`	ISO 3166-1 alpha-2
`bank_account` / `e_transfer` / `virtual_account` / `sokin_internal` / `crypto`	object	exactly one	The destination object matching the rail's payment method (rail→method mapping as in `get_beneficiary_schema`); inner keys are the camelCase names the schema returns
`individual` / `company`	object	per entity_type	Identity details
`address`	object	bank rails + `e_transfer`	Not required for `internal`, `pix`, or crypto rails
`corporate_reference`	string	no	Corporate to create under. Required in practice; part of the byte-match
`otp_code`	string	2nd call	The 6-character code from the user's email
`confirm_verified_payee_name`	boolean	no	Only after a VoP mismatch the user explicitly confirmed; changes the draft, so the flow restarts and needs a fresh code

content / structuredContent — three shapes:

Draft invalid (informational, isError false): {"status": "draft_invalid", "errors": [{"field", "message"}]} — text lists each field error and says nothing was created and no code email was sent.

Code triggered (informational, isError false): {"status": "otp_required", "expiresInSeconds": 600} — text instructs asking the user for the code and calling again with the same arguments plus otp_code. Any trigger while a code is outstanding for this user and action type (same draft or a different one) returns {"status": "otp_resent", ...} — text says a NEW code was emailed, any earlier code is now void, and to use the most recent email.

Ambiguous upstream failure (isError true): any 5xx/transport error renders

API error (N): <message> -- the request may still have gone through, so whether the payee was created is UNKNOWN. Do NOT retry blindly: check list_beneficiaries for this payee FIRST -- a blind retry can create a DUPLICATE. ...

— the in-flight claim is kept, so an identical call is refused for up to 10 minutes.

Created: envelope {"data": {...}} with externalReference, displayName, status, destinations[] (currencyCode, paymentRail, validationStatus), createdAt:

Payee created: Acme Ltd (reference ben_new, status active).
Destinations: GBP via faster_payments (name verified).

(supportedRails and version are dropped as in get_beneficiary; a
create without OTP appends "No confirmation code was required for this
corporate.")

Full response adds: on the created shape, the envelope's message plus
the full raw record (supportedRails, version, complete destination
payloads — minus the e-Transfer securityAnswer, withheld even here); on
the draft-invalid shape, the raw batch-validation envelope.

Validation errors (each refuses before the create is attempted):

Error: display_name must not be empty. (and the same for currency_code / payment_rail)

Error: payment_rail 'sokin_internal' is a payment METHOD, not a rail. ... — catches the method-vs-rail taxonomy confusion

Error: payment_rail 'faster_payments' takes exactly one destination object: bank_account (you supplied: e_transfer). Call get_beneficiary_schema for that corridor's field list.

Error: entity_type and country_code are required for every payment rail except internal.

Error: otp_code must be the 6-character code from the confirmation email (letters and digits). ...

Error: these arguments don't match the draft that triggered the code (or more than 10 minutes have passed). ... — the byte-match refusal

Error: a newer confirmation code was requested after this draft's -- each new code email replaces the previous one of the same type, so the code for this draft is no longer redeemable. ...

— the superseded-trigger refusal

Error: an identical create for this payee is already in flight. ... — on the trigger path this one can follow the dry-run pre-flight call; everything else above is purely local

One pre-flight nuance: the dry-run validator is corporate-agnostic while the
create itself resolves payment rails per corporate, so a rejection whose
only errors are on paymentRail is treated as non-authoritative and the
tool proceeds to the real create (which decides with the corporate's actual
rail set — e.g. a per-corporate rail pilot).

OTP-state errors (each maps one upstream 401/403/429, discriminated by
the API's exact message strings — an unrecognized status/message combination
falls through to generic API-error rendering rather than gaining fabricated
OTP specifics): invalid code (pending draft kept — the user re-reads the
most recent email), expired code (re-trigger), account blocked (hard stop,
names the portal-login lockout), rate-limited (names the 5-per-15-min
window), stale/no active code (re-trigger), and no-Sokin-user-identity (401
— OTP actions can't complete on this connection). A Verification of Payee
mismatch (422) renders both names verbatim, clears the pending draft (the
code is consumed and that exact draft can only mismatch again), and
instructs the confirm_verified_payee_name restart with a fresh code.

A 201 whose payload lacks the created record is reported as
API error (502) — whether the payee was created is unknown; check
list_beneficiaries before retrying, a blind retry can create a duplicate.

Example

Request

{
  "name": "create_beneficiary",
  "arguments": {
    "display_name": "Contoso Ltd",
    "currency_code": "GBP",
    "payment_rail": "faster_payments",
    "entity_type": "company",
    "country_code": "GB",
    "bank_account": {"accountNumber": "12345678", "sortCode": "040075"},
    "company": {"registeredName": "Contoso Ltd"},
    "address": {
      "addressLineOne": "1 High St",
      "city": "London",
      "postCode": "EC1A 1AA",
      "countryCode": "GB"
    },
    "corporate_reference": "CORP-8842"
  }
}

Reply

Payee created: Contoso Ltd (reference BEN-3310, status active).
Destinations: GBP via faster_payments (name verified).
No confirmation code was required for this corporate.

Reply as data

{
  "data": {
    "externalReference": "BEN-3310",
    "displayName": "Contoso Ltd",
    "status": "active",
    "createdAt": "2026-09-17T09:14:00Z",
    "destinations": [
      {
        "currencyCode": "GBP",
        "paymentRail": "faster_payments",
        "validationStatus": "matched"
      }
    ]
  }
}

`update_beneficiary`

Update Beneficiary · writes (destructive, idempotent) · touches an external system

Sparse PATCH of an existing payee's destination and identity details,
protected by the same two-call OTP flow as create_beneficiary (same
gate, same byte-match — including beneficiary_id — same code mechanics and
error states). Annotated destructive: it overwrites payee details that steer
future payments and the prior state is not recoverable through the API;
idempotent: re-applying the same patch converges.

What cannot be updated: displayName, entityType, countryCode, and
address are immutable upstream (

"<field> is immutable. Create a new
beneficiary to use a different value."

) — and the API only rejects them
after the OTP code has been consumed, so this tool refuses them up
front: the four parameters are accepted only to reject them clearly (a
schema that silently dropped them would let a mixed patch apply the rest
while the caller believes the rename happened). Changing them means a new
payee via create_beneficiary.

The API's own patch semantics, surfaced in the docstring:

Supply only the fields to change; omitted fields stay unchanged, and a
field cannot be cleared.

A supplied nested object must contain at least one field (rejected
locally otherwise).

For a multi-destination payee, payment_rail and currency_code
together are the destination selector, not an update. Upstream only
catches a missing payment_rail before the code is issued
(paymentRail is required when a beneficiary has multiple destinations.);
a missing currency_code would fail after the code is consumed
(currencyCode is required when a beneficiary has multiple destinations.)
— so the tool requires the two together, locally.

Selectors can ADD: selectors naming a (currency, rail) the payee does
not have, together with destination fields, add that destination — the
route's own description is "Partially update a beneficiary or add a
payment destination". Confirm which one the user means.

Merge-then-revalidate: the API merges the patch into the stored record
and re-validates the complete result against the create contract, so a
validation error can name fields the patch never sent.

404-before-OTP: the update guard resolves the beneficiary before the
OTP check, so an unknown payee fails with a named not-found and the code
is never consumed — on the trigger call none is emailed at all; on the
redeem call the message says the (already-emailed) code was not consumed.
The lookup is corporate-scoped, so a wrong corporate_reference also
reads as "Beneficiary not found" — the error names both possible causes. (A literal Corporate not found on this route
comes from the command handler, after OTP verification, so that variant
carries no burned-nothing reassurance.)

No dry-run pre-flight exists for patches (unlike create's
batch-validation), so the first call goes straight at the PATCH.

Parameter	Type	Required	Description
`beneficiary_id`	string	yes	The payee's `externalReference`; part of the byte-match
`currency_code` + `payment_rail`	string	multi-destination	Destination selectors, supplied together — not updates
`bank_account` / `e_transfer` / `virtual_account` / `sokin_internal` / `crypto` / `individual` / `company`	object	at least one	Fields to change (camelCase inner keys)
`display_name` / `entity_type` / `country_code` / `address`	—	refuse-only	Immutable upstream; accepted only to be refused up front, before any code is triggered or consumed
`corporate_reference`	string	no	Required in practice; part of the byte-match
`otp_code`	string	2nd call	The 6-character code from the user's email
`confirm_verified_payee_name`	boolean	no	VoP-mismatch override, same flow as create

content / structuredContent — the otp_required / otp_resent
shapes and the ambiguous-5xx rendering are identical to create_beneficiary's
(the 5xx wording here says whether the update was applied is unknown and
points at get_beneficiary). An identity patch is verifiable from the text:
the patched individual/company keys are echoed back as the record now
reads them; keys the API accepts but never returns (company.taxId, the
individual ID details) are listed as not confirmable from the response
rather than misread as failures; and a patch whose object mismatches the
payee's immutable entityType — which upstream silently drops with a
200 — is called out as IGNORED upstream; a successful update returns the full updated
record through get_beneficiary's shaping (envelope {"data": {...}},
full destinations, supportedRails/version/security answer dropped),
rendered as:

Payee updated.

Acme Ltd -- company, GB, active

Currency	Rail	Validation	Account
GBP	faster_payments	matched	87654321

Created 2026-01-01T00:00:00Z.

Full response adds: the envelope's message plus the raw record
(supportedRails, version, complete destination payloads — minus the
e-Transfer securityAnswer, withheld even here).

The docstring also carries two required companion steps: run the matching
validate_beneficiary name check on the new bank details before
patching (same rule as create), and run the beneficiary_id validation
after patching an EUR/SEPA destination — the patch resets it to
not_validated, which blocks payments until refreshed.

Validation errors (local, before any network call):

Error: beneficiary_id must not be empty.

Error: display_name cannot be updated -- displayName, entityType, countryCode, and address are immutable on the API. ... — the refuse-only parameters, rejected before anything else runs

Error: bank_account must include at least one field to update -- omit the parameter entirely to leave it unchanged (a field cannot be cleared).

Error: supply individual OR company, not both -- a payee has one immutable entity type, and the mismatched object would be silently ignored upstream after the code is consumed.

Error: supply at least one field to update: a destination object (bank_account / e_transfer / virtual_account / sokin_internal / crypto), individual, or company. ...

— also names the SELECTORS rule and the immutable fields

Error: supply payment_rail and currency_code together -- they jointly select which destination to update. ...

The same otp_code shape check, byte-match refusal, superseded-trigger refusal, and in-flight-claim refusal as create_beneficiary (create and update share the upstream action scopes, so a newer external-payee trigger of either tool supersedes a pending external draft of the other).

OTP-state and VoP errors: identical wording to create_beneficiary
(shared implementation), except the VoP mismatch says the payee was NOT
changed. A 200 whose payload lacks the updated record is reported as
API error (502) — whether the payee was updated is unknown; fetch it with
get_beneficiary before retrying.

Example

Request

{
  "name": "update_beneficiary",
  "arguments": {
    "beneficiary_id": "BEN-3310",
    "bank_account": {"accountNumber": "87654321"},
    "corporate_reference": "CORP-8842",
    "otp_code": "A1B2C3"
  }
}

The same call without otp_code is what triggers the email:

A 6-character confirmation code has been emailed to the user. Ask them for it, then call update_beneficiary again with the SAME arguments plus otp_code. The code is single-use and expires in 10 minutes; to get a fresh one, call again without otp_code (max 5 emails per 15 minutes).

Reply

Payee updated.

Contoso Ltd -- company, GB, active

Currency	Rail	Validation	Account
GBP	faster_payments	matched	87654321

Created 2026-09-17T09:14:00Z.

Reply as data

{
  "data": {
    "externalReference": "BEN-3310",
    "displayName": "Contoso Ltd",
    "entityType": "company",
    "countryCode": "GB",
    "status": "active",
    "createdAt": "2026-09-17T09:14:00Z",
    "destinations": [
      {
        "currencyCode": "GBP",
        "paymentRail": "faster_payments",
        "validationStatus": "matched",
        "account_number": "87654321"
      }
    ]
  }
}

`list_financial_institutions`

List Financial Institutions · read-only · touches an external system

Reference data listing institutions available for beneficiary creation
(e.g. Canadian EFT). Not corporate-scoped, not paginated, not filterable:
the upstream endpoint accepts no parameters, so neither does this tool.

Parameters: none.

content, a markdown table: see the Example below.

structuredContent, envelope {"message": "Success.", "data": [...]},
each item:

Field	Type	Description
`id`	integer	Institution id, a plain integer
`name`	string	Institution name
`bankNumber`	string	Institution's bank number

Full response adds: nothing. Compact is the identity of raw.

This list is a live proxy to a third-party provider that silently drops
any record failing validation, so a real, fetchable institution can be
absent from it. Do not treat it as an exhaustive allow-list.

Example

Request

{"name": "list_financial_institutions", "arguments": {}}

Reply

2 financial institutions:

Id	Name	Bank Number
1	Royal Bank of Canada	003
2	Toronto-Dominion Bank	004

Reply as data

{
  "message": "Success.",
  "data": [
    {"id": 1, "name": "Royal Bank of Canada", "bankNumber": "003"},
    {"id": 2, "name": "Toronto-Dominion Bank", "bankNumber": "004"}
  ]
}

`list_financial_institution_branches`

List Financial Institution Branches · read-only · touches an external
system

Lists an institution's branches (routing numbers and addresses) for
completing a beneficiary. Cursor-paginated.

Parameter	Type	Required	Description
`financial_institution_id`	integer or string	yes	The numeric `Id` from `list_financial_institutions` (not `Bank Number`, which is zero-padded and names a different bank). ASCII digits only, at most 9223372036854775807; surrounding whitespace is tolerated
`limit`	integer	no	Max branches per page
`next_token`	string	no	Cursor from the previous page

content, a markdown table: see the Example below.

structuredContent, envelope {"data": [...], "pagination": {...}},
each item carrying id, description, routingNumber, addressLineOne,
addressLineTwo, city, state, postalCode.

Full response adds: the envelope's message field only.

Validation errors:

Condition	Error
Non-numeric id (rejected locally before any upstream call)	`Error: financial_institution_id must be a numeric id from list_financial_institutions (at most 9223372036854775807), got 'abc'. Call list_financial_institutions to see valid ids.`
Unknown numeric id after an empty branches result	`Unknown financial institution id: '999'. Call list_financial_institutions to see valid ids.`

The unknown-id check runs only on an empty result, never before attempting the
branches call. The branches endpoint has no not-found signal of its own; an
unrecognized id returns an empty list, indistinguishable from an
institution that genuinely has no branches. Because the institutions list
can be missing real records (see above), gating upfront would reject a real
institution's real branches whenever that institution happened to be one of
the dropped ones.

Example

Request

{"name": "list_financial_institution_branches", "arguments": {"financial_institution_id": 1}}

Reply

1 branch:

Id	Description	Routing Number	Address	City	State	Postal Code
4412	Main Branch	000312345	200 Bay Street, Suite 400	Toronto	ON	M5J2J2

Reply as data

{
  "data": [
    {
      "id": 4412,
      "description": "Main Branch",
      "routingNumber": "000312345",
      "addressLineOne": "200 Bay Street, Suite 400",
      "addressLineTwo": null,
      "city": "Toronto",
      "state": "ON",
      "postalCode": "M5J2J2"
    }
  ],
  "pagination": {"nextToken": null, "previousToken": null, "totalItems": 1, "hasMore": false}
}

`get_documentation_links`

Get Documentation Links · read-only · touches no external system

Returns the URLs of Sokin's own documentation, so an agent can read the
real integration contract instead of guessing an endpoint or an API
version from memory. It returns pointers only, never documentation
content itself.

Answers come from the server's own configuration, so they always describe
the server the client is connected to.

Parameter	Type	Required	Description
`topic`	`"b2b_api"`, `"mcp_server"`, or `"all"`	no	Which documentation to look up. Default `"all"`

b2b_api: the Sokin B2B REST API this server calls: endpoints, auth,
API versions, request/response schemas.

mcp_server: this MCP server itself: its tools, their returns, and
how to connect: this documentation. A server with no such page configured
says so instead and points back at the tool list the connection already
provides.

all: every topic. The default, and the right choice when unsure.

content, a header naming the server, a markdown table, then any
applicable notes: see the Example below.

A topic with nothing configured renders as (none available) rather than
being omitted, and its summary column carries the reason: the row is
always there.

structuredContent, flat, no data envelope:

Field	Type	Description
`mcpServerUrl`	string	Public base URL of the server that answered, so a client can tell which server the links describe without inferring it from the URLs
`documentation`	array	One record per requested topic, in a stable order

Every documentation record has the same shape, so it can be iterated
without special-casing per topic:

Field	Type	Description
`topic`	string	`b2b_api` or `mcp_server`
`title`	string	Human-readable name of the reference
`url`	string, or null	Where to read it. Null when nothing is configured for that topic
`alternateUrl`	string, or null	A genuinely different second URL, when one exists; typically the human-readable page when `url` is an agent-oriented index
`summary`	string	One line on what lives there, or on why there is no URL

Where both an agent index and a human page are configured for b2b_api,
the index wins as url and the human page becomes alternateUrl. The
index is a flat list of markdown links; the human page is a client-rendered
application an agent gets little from fetching.

Full response adds: nothing. There is no API call behind this tool, so
compact and raw are the same object by design.

Example

Request

{"name": "get_documentation_links", "arguments": {"topic": "all"}}

Reply

Sokin documentation for the MCP server at https://mcp.sokin.com.

Documentation	URL	What's there
Sokin B2B API reference	https://docs.sokin.com/llms.txt	The Sokin B2B REST API this MCP server calls: every endpoint, authentication, API versions, and request/response schemas
Sokin MCP server reference	https://docs.sokin.com/sokin-mcp-10453423f0	This MCP server: the tools it exposes, what each returns, and how to connect a client

Sokin B2B API reference also has a human-readable page at https://docs.sokin.com. Append .md to any page URL listed in the index at https://docs.sokin.com/llms.txt to fetch it as raw markdown; the API pages include the OpenAPI spec.

Reply as data

{
  "mcpServerUrl": "https://mcp.sokin.com",
  "documentation": [
    {
      "topic": "b2b_api",
      "title": "Sokin B2B API reference",
      "url": "https://docs.sokin.com/llms.txt",
      "alternateUrl": "https://docs.sokin.com",
      "summary": "The Sokin B2B REST API this MCP server calls: every endpoint, authentication, API versions, and request/response schemas"
    },
    {
      "topic": "mcp_server",
      "title": "Sokin MCP server reference",
      "url": "https://docs.sokin.com/sokin-mcp-10453423f0",
      "alternateUrl": null,
      "summary": "This MCP server: the tools it exposes, what each returns, and how to connect a client"
    }
  ]
}

`visualize`

Visualize · read-only · touches no external system

Renders Mermaid diagrams and rich markdown inside the MCP client via its
own UI embed (ui://sokin-mcp/visualize). It is a diagramming tool, not a
prettifier: the caller writes the markdown, and this only renders it.

Parameter	Type	Required	Description
`markdown`	string	yes	Full CommonMark + GFM. Fenced blocks tagged `mermaid` render as diagrams. Raw HTML is sanitized, not rendered
`title`	string	no	The card's header. Defaults to a generic heading

Practical constraints worth knowing when generating content for it: card
width is fixed at roughly 600px, height is unconstrained. Prefer
top-to-bottom diagrams (TD, not LR), keep labels short, and keep any
single diagram to roughly 10 to 15 nodes. Do not include a

%%{init:
...}%%

theme directive; the card applies its own brand theme and yours
would clash.

content, the markdown string, echoed verbatim.

structuredContent, flat, no envelope:

Field	Type	Description
`title`	string	The title as passed
`markdown`	string	The markdown as passed

Full response adds: nothing; this tool calls no API, so there is no
raw payload to widen.

Validation errors:

markdown must not be empty.

Example

Request

{
  "name": "visualize",
  "arguments": {
    "title": "Balances by currency",
    "markdown": "```mermaid\npie title Balances\n  \"GBP\" : 48200\n  \"USD\" : 12000\n```"
  }
}

Reply

The card itself, rendered in the chat. There is no summary sentence — the text
half of the reply is the markdown you passed, echoed back unchanged.

Reply as data

{"title": "Balances by currency", "markdown": "```mermaid\npie title Balances\n  \"GBP\" : 48200\n  \"USD\" : 12000\n```"}

`play_cheetah_dash`

Play Cheetah Dash · read-only · touches no external system

Launches an endless-runner arcade game rendered inline via its own UI embed
(ui://sokin-mcp/cheetah-dash). It takes no arguments and calls no Sokin
API.

Parameters: none.

content, a plain string: see the Example below.

structuredContent: none. This is the only tool on this server that
returns a bare string rather than going through the compact/full
machinery, so it is also the only tool whose success result carries no
structuredContent at all.

Example

Request

{"name": "play_cheetah_dash", "arguments": {}}

Reply

Cheetah Dash is ready -- use Space or tap to jump, again mid-air to double jump.

Appendix: enumerations

Every closed value set an integrator will encounter. All of these are read
from the Sokin B2B API's own source definitions, not inferred from observed
responses: a value set you have not seen in testing is still one your code
should handle.

Instruction types

instructionType on list_instructions and get_instruction, the B2B
API's InstructionType enum (8 values):

Value	Meaning
`Payment`	Moves funds from a CCA to a beneficiary
`FX`	Moves funds between two CCAs owned by the same corporate, in different currencies
`FXPayment`	Moves funds from a CCA to a beneficiary in a different currency
`UnfundedPayment`	Funds may land in the account after the instruction is created, before sending
`UnfundedFXPayment`	The unfunded variant of `FXPayment`
`SokinDirect`	Same-currency transfer between two on-platform CCAs, at zero fees
`BoostDeposit`	Moves funds from a CCA, subject to treasury approval before completion
`ForwardSettlement`	Settles a Forward Contract at the contracted forward rate

Instruction display statuses

displayStatus, the user-facing status, present in the compact response.
The values contain spaces and are shown exactly as they appear (11 values):

Pending finalisation, Approval Initiated, Approval Completed,
Pending Partner, Booking FX Trade, Pending, Pending FX Settlement,
Pending Settlement, Processed, Failed, Unknown.

get_instruction can also return Rejected -- not one of the 11 values
above and not a value the backend itself ever sends. This server
synthesizes it when Failed carries an "Approval rejected: " prefix on
failureReason, to tell a human's portal rejection apart from a real
processing failure (the backend has no such distinction of its own). See
get_instruction's own section for the two fields this adds when it fires.

Instruction internal statuses (full response only)

status is dropped from the compact response and appears only when the
full-response opt-in is used. The API's own field description calls it the
internal status, though that description is known to omit several real
members; the full enum (14 values) is:

Created, ApprovalInitiated, ApprovalCompleted, Processed, Failed,
PaymentInstructed, FXTradeBooked, OutboundComplianceCompleted,
InboundComplianceCompleted, LiquidityConfirmed, FXTradeSettled,
PaymentSettled, BoostApprovalRequested, BoostApprovalCompleted.

Prefer displayStatus. These values track internal workflow transitions
and are not a stable public contract.

Instruction request statuses

status on get_instruction_request, the B2B API's
InstructionRequestStatus enum. Exactly 3 values, no more:

Created, Accepted, Rejected.

The naming is counter-intuitive and worth restating: Created means still
processing, Accepted means the instruction now exists, Rejected means
it never will. Render an unrecognized value verbatim rather than mapping it
onto one of these three.

errorCategory alongside it, and on validate_payment_instruction, is
backed upstream by a real closed enum, InstructionRequestErrorCategory
(10 members): fees, amount, amount_missing_funds,
corporate_currency_account, quote, beneficiary_reference,
reseller_reference, reseller_fee, payment_details,
corporate_reference. On the wire, though, both response models declare
this field as a plain optional string, not the enum itself, so treat it as
a documented, currently-closed set rather than a contract you can rely on
never growing a new member.

beneficiary_currency is an eleventh value, but it does not come from
that upstream enum. validate_payment_instruction and
create_payment_instruction both synthesize it locally, before the
backend is ever called, when a beneficiary genuinely exists but has no
destination in the source account's currency (the B2B API reports that
case the same way as a beneficiary that does not exist, and would otherwise
return beneficiary_reference for both). Same-currency
only: neither tool converts currencies, and a mismatch here means "retry
with a different beneficiary or account," not "the beneficiary doesn't
exist" -- use create_fx_payment_instruction for a cross-currency payment
to the same beneficiary instead.

Ledger entry type and direction

On get_account_ledger entries:

direction takes only two values in practice, credit or debit
(populated upstream as item.type.lower() of a Credit/Debit database
enum), though it is typed as a plain string on the wire rather than an
enforced enum.

type is not a short closed set, and this is the field most likely to
break a naive integration. Upstream, only four internal item types collapse
to two friendly labels; everything else is emitted under its own raw
snake_case value. The full set you can receive (14 values):

Value	Notes
`deposit`	Funds in
`withdrawal`	Funds out
`FX Trade`	Friendly label covering both `fx_trade_in` and `fx_trade_out` legs
`Forward settlement`	Friendly label covering both `forward_settlement_in` and `forward_settlement_out` legs
`sokin_direct_send`	On-platform CCA-to-CCA transfer, outgoing leg
`sokin_direct_receive`	On-platform CCA-to-CCA transfer, incoming leg
`boost_deposit`	Move into a Boost position
`boost_maturity_payout`	Boost payout at maturity
`manual_adjustment_fraud_recall`	Operational adjustment
`manual_adjustment_account_offboarding`	Operational adjustment
`manual_adjustment_good_will`	Operational adjustment
`manual_adjustment_fee_adjustment_refund`	Operational adjustment
`manual_adjustment_other_manual_credit`	Operational adjustment
`manual_adjustment_other_manual_debit`	Operational adjustment

Do not switch-case on deposit/withdrawal/FX Trade alone: the
operational and Sokin Direct values are real values on real accounts, and
new item types can be added upstream over time. Treat an unrecognized
type as displayable rather than an error.

The content table signs amounts from direction (+ for credit, - for
debit), while structuredContent.amount stays unsigned either way.

Account locality statuses

localAccountStatus and internationalAccountStatus on get_account, the
B2B API's CCALocalityStatus enum. Exactly 4 values, no others:

Value	Meaning
`ACTIVE`	The account is active and ready to receive payments
`PENDING`	Not active yet; still processing, or awaiting operational action
`NOT_PROVISIONED`	Can be set up, but account setup or terms acceptance is incomplete
`NOT_AVAILABLE`	Pay-in over this route is unavailable for this account. Also the default value when the field is otherwise unset

Beneficiary entity type and status

Field	Values
`entityType`	`individual`, `company`
`status`	`active`, `deleted`

Payment rails

paymentRail on a beneficiary destination, the B2B API's PaymentRail
enum. It has 67 values; the common ones are below, and the rest are local
rails named after their clearing system (for example sptr, spei,
imps_neft, elixir), which come through under those names. pix_siloc_ted
is a bank rail, not pix.

Group	Values
Internal	`internal`
International	`swift`
Europe	`sepa`
United Kingdom	`faster_payments`, `bacs`, `chaps`
United States	`ach`, `fedwire`, `fednow`
Canada	`eft`, `e_transfer`
Asia-Pacific	`fast_meps`, `npp`
Middle East	`fts_ipi`
Latin America	`pix`
Crypto networks	`base`, `tron`, `ethereum`, `polygon`, `solana`

For crypto destinations the rail is the on-chain network itself.

Corporate assignment types

assignmentType on list_corporates: direct or inherited.

Payment purposes

payment_purpose on validate_payment_instruction, create_payment_instruction,
submit_payment_instruction, create_fx_payment_instruction, and
submit_fx_payment_instruction is a declared schema enum, not free text. An
unrecognized value is rejected by schema validation before the tool body
runs, the same as an invalid fixed_side. When omitted entirely, the create
endpoints default it to ACCOUNTS_PAYABLE server-side.

The declared set is Sokin's current catalogue of 22 purposes:

ACCOUNTS_PAYABLE, COMMISSION, CUSTOMER_REFUND, CUSTOMS_DUTIES,
DIVIDEND_DISTRIBUTION, EXPENSE_REIMBURSEMENT, FREELANCER_CONTRACTOR,
INSURANCE_PREMIUM, INTERCOMPANY_TRANSFER, LOAN_REPAYMENT,
MARKETING_ADVERTISING, OFFICE_LEASE, OTHER, PROFESSIONAL_SERVICES,
ROYALTY_LICENSE_FEE, SALARY_PAYROLL, SHIPPING_FREIGHT_LOGISTICS,
SOFTWARE_SUBSCRIPTIONS, SUPPLIER_PAYMENT, TAX_PAYMENT,
TRAVEL_EXPENSE, UTILITIES.

The underlying B2B API accepts a wider, older set of purpose codes (about
150 more, largely Canadian clearing-system codes such as PAYROLL_DEPOSIT).
These tools reject those before any upstream call, because payout providers
reject them anyway. The B2B API's own listing endpoint,
GET /instruction-requests/payment-purposes, returns either list depending
on the caller's X-Api-Version header; it has no bearing on what these
tools accept.

One value, OTHER, can fail at the payout provider for some routes, whose
purpose mapping has no entry for it. Prefer a specific purpose where one
fits.

Request parameter enums

Closed sets on tool inputs. An out-of-range value is rejected by schema
validation before the tool body runs:

Parameter	Tool	Values
`fixed_side`	`get_fx_quote`, `create_fx_quote`, `create_fx_payment_instruction`	`BUY`, `SELL` (default `SELL`)
`search_mode`	`list_beneficiaries`	`contains`, `starts_with` (default `contains`)
`topic`	`get_documentation_links`	`b2b_api`, `mcp_server`, `all` (default `all`)
`payment_purpose`	`validate_payment_instruction`, `create_payment_instruction`, `submit_payment_instruction`, `create_fx_payment_instruction`, `submit_fx_payment_instruction`	22 values, see "Payment purposes" above
`exclude_display_status`	`list_instructions`	`Processed`, `Failed` (repeatable; mutually exclusive with `completed`)
`sort_order`	`list_instructions`	`desc`, `asc` (default `desc`)

Sokin MCP - Technical Docs

Server#

Authentication#

Anatomy of a result#

A stray message field#

Response modes: compact and full#

Errors#

Pagination#

Tools#

Card support and where the human control sits#

list_corporates#

list_accounts#

get_account#

get_account_ledger#

list_instructions#

get_instruction#

get_instruction_request#

validate_payment_instruction#

create_payment_instruction#

submit_payment_instruction#

get_fx_quote#

create_fx_quote#

settle_fx_quote#

create_fx_payment_instruction#

submit_fx_payment_instruction#

list_beneficiaries#

get_beneficiary#

get_beneficiary_schema#

validate_beneficiary#

create_beneficiary#

update_beneficiary#

list_financial_institutions#

list_financial_institution_branches#

get_documentation_links#

visualize#

play_cheetah_dash#

Appendix: enumerations#

Instruction types#

Instruction display statuses#

Instruction internal statuses (full response only)#

Instruction request statuses#

Ledger entry type and direction#

Account locality statuses#

Beneficiary entity type and status#

Payment rails#

Corporate assignment types#

Payment purposes#

Request parameter enums#

Server

Authentication

Anatomy of a result

A stray `message` field

Response modes: compact and full

Errors

Pagination

Tools

Card support and where the human control sits

`list_corporates`

`list_accounts`

`get_account`

`get_account_ledger`

`list_instructions`

`get_instruction`

`get_instruction_request`

`validate_payment_instruction`

`create_payment_instruction`

`submit_payment_instruction`

`get_fx_quote`

`create_fx_quote`

`settle_fx_quote`

`create_fx_payment_instruction`

`submit_fx_payment_instruction`

`list_beneficiaries`

`get_beneficiary`

`get_beneficiary_schema`

`validate_beneficiary`

`create_beneficiary`

`update_beneficiary`

`list_financial_institutions`

`list_financial_institution_branches`

`get_documentation_links`

`visualize`

`play_cheetah_dash`

Appendix: enumerations

Instruction types

Instruction display statuses

Instruction internal statuses (full response only)

Instruction request statuses

Ledger entry type and direction

Account locality statuses

Beneficiary entity type and status

Payment rails

Corporate assignment types

Payment purposes

Request parameter enums