Skerry — global payment orchestration

Money movement is many integrations pretending to be one product

Skerry is the layer that holds them together. The regulated act stays with the institution licensed to perform it.

Direct integration · Per rail, per country

One bank, one rail, one contract at a time.

Every corridor arrives with its own onboarding, file format, settlement window and reconciliation model. The engineering cost scales with the map rather than with the business, and the logic ends up spread across the integrations instead of living in one place.

Skerry · One orchestration layer

One programmable surface over accounts, rails and conversions.

Skerry routes the instruction and holds the state. Bridge and Stripe execute it under their own licences. Your systems integrate once, and each layer does the part it is built for.

How responsibility is split

What the platform does5

Five capabilities, one of them coming soon, each described as software, each naming the partner that performs the regulated act.

01
Virtual accounts
Programmatic routing across USD and EUR virtual accounts issued by Bridge. Skerry addresses them through one API surface; Bridge issues and operates them.
02
Stablecoin conversion
Automated stablecoin-to-fiat payout execution, triggered by your rules and carried on the underlying rails. The conversion itself is performed by the regulated partner.
03
Global money movement
Cross-border payout and treasury orchestration software. Today that is USD and EUR payouts from a stablecoin balance, conversions between a customer’s own balances with a priced, expiring quote, and a ledger you can export. Per-corridor configuration is not available.
04
API onboarding
Automated end-customer KYB flow orchestration. Skerry sequences collection, submission and status; the verification decision belongs to the partner.
05
CardsComing soon
Stablecoin-backed cards issued to your customers, with spend controls, freezes and transaction history. The endpoints are documented; issuing is not switched on yet.

Delegate payments to your agents. You set the limits; you stay accountable.

Agentic commerce on Skerry: an agent acts on a key a person issued, against wallets that belong to a verified business. Anything not yet switched on is marked.

Delegation · People, machines and agents

Every agent is tied to a person and their wallet.

The person or business behind an agent is identified and accountable. They delegate to the agent from their own identity and wallet, decide what it may do, and can take that authority back at any time.

Accountable owner: Each business is onboarded and verified through Bridge, and its wallets and accounts are held in its name. Keys are issued in the console by a signed-in person and recorded against them.
Wallet: An agent pays from the business's own custodied stablecoin wallets and accounts. The keys to those wallets stay with the regulated custodian; neither Skerry nor the agent holds them.
Scope: Every operation names its scope, and a key narrower than the call is refused.
Revocation: Any key can be revoked from the console at any time. The next call it makes is refused.
Sandbox and live: Sandbox keys work at once. A live key works only after live is approved for the project.
Spending limits: Spend policies per key and per agent: per-payment, daily and monthly limits, destination allow-lists, currencies, an expiry date on the policy, and immediate revocation. A key that has had a policy stays restricted. A key has no expiry date of its own.
Approvals: Above an amount you set, a payout, refund, conversion or charge waits for a person to approve it with a different key. The agent that asked cannot approve its own request.
People: Individuals as verified owners in their own right, alongside businesses.Coming soon
Machines and agents: An identity and a wallet of their own for machines and agents, acting by delegation from the accountable person or business.Coming soon

For agents · The same API

Agents call Skerry the way any client does.

No separate agent product with its own rules: the key, the scopes and the approvals are the ones the API already enforces.

The API reference

MCP: Skerry over the Model Context Protocol at skerry.mcp.praecise.cloud/mcp. The agent presents its own key; scopes and approvals are applied by the API exactly as for any other client.
Moving money: The one tool that moves money says so, asks the agent to confirm the amount and the beneficiary with the person it acts for, and requires an idempotency key.
OpenAPI: The whole reference as one OpenAPI 3.1 document, for a generator or an agent.
Events: Events for customers, payments, refunds, disputes, settlements, subscriptions, payouts, conversions and approvals, delivered to your webhooks and replayable. Not every change emits one: wallets, payees and standing orders do not yet.
Agent checkout: Agents paying merchants at checkout.Coming soon

Stablecoin payments and treasury

Stablecoin rails with Bridge. Coins, chains and rails are listed as they are switched on.

Treasury · Held in stablecoin

A business treasury in stablecoin, paid in and out in local currency.

Money paid into a virtual account arrives as stablecoin, is held in custodied wallets, and leaves as a bank payment or a stablecoin transfer. Custody and conversion are performed by Bridge.

Stablecoins: USDC, EURC, USDB and USDT. Which of them a customer may hold is settled with the banking partner when the customer is verified; Skerry does not filter coins by region itself.
Card and wallet payments: Hosted checkout, payment links, refunds, disputes, saved payment methods and subscriptions, processed by Stripe on the business’s own account. Card details never reach Skerry.Test mode
Chains: Base, Ethereum, Solana and Tron.
Treasury: Balances and conversions across a business's wallets, and a double-entry ledger of what moved, exportable as CSV or JSON.
Money in: USD and EUR virtual accounts in the business's name. Deposits convert to stablecoin on arrival.
Money out: USD by wire and ACH, EUR by SEPA, paid from a stablecoin balance. Stablecoin transfers to an address or another wallet.
Standing conversion: An address that converts and pays out whatever arrives, with no payout to create per payment.
More rails: GBP by Faster Payments, MXN by SPEI, BRL by PIX.Coming soon
Cards: Stablecoin-backed cards with spend controls.Coming soon

How an instruction becomes a settlement

Skerry holds the logic and the state. The money moves on the partner’s licence.

01 · Onboard

The KYB flow is orchestrated, not adjudicated.

The business owner finishes onboarding on hosted pages you link to, so you send no people, birth dates or documents. Partners that already collect and may lawfully send them can still submit them through the API. Skerry sequences the steps and reports the status; the partner performs the check.

02 · Route

The currency selects the account and the rail.

Deposits land in the virtual account for their currency, and a payout leaves by wire or ACH in USD and by SEPA in EUR. Routing by rule, corridor or cut-off is not available yet.

03 · Execute

The instruction is executed by the licensed partner.

Account issuance, payment processing, conversion and custody are performed by Bridge and Stripe. Skerry records the resulting state and returns it to your systems.

Language, kept strictly functional

By keeping language strictly functional, Skerry emphasises platform power while remaining clearly outside the scope of regulated financial services.

Virtual bank accounts: Programmatic virtual account routing (USD, EUR) issued by Bridge
Stablecoin conversion: Automated stablecoin-to-fiat payout execution via underlying rails
Global money movement: Cross-border payout & treasury orchestration software
API onboarding: Automated end-customer KYB flow orchestration

The same wording is used in the product, the API documentation and every sales material. It is not a disclaimer bolted on at the end — it is how the capability is actually built.

Executed by regulated partners

Named, not implied. Each regulated act is performed by the partner licensed for it.

Bridge Building Inc.

Virtual accounts, stablecoin conversion, custody.

Multi-currency virtual account creation in USD and EUR, stablecoin-to-fiat conversion, and custody of funds and digital assets are executed directly by Bridge under its own licences and agreements with your end customers.

Stripe, Inc.

Payment processing.

Payment processing is executed directly by Stripe under its own licences. Card and wallet acceptance is available in test mode today and is not yet open for live payments. Skerry carries the instruction and records the result; it never sits in the flow of funds.

A clear division of responsibility

Each side does what it is built and licensed to do, and it is described the same way everywhere it appears.

Skerry · Software

The orchestration layer.

Instructions, state and a ledger export, exposed to your systems as one programmable surface. Funds and digital assets stay with the institutions that hold them.

Partners · Regulated activity

The licensed infrastructure.

Banking, multi-currency virtual account creation, payment processing, stablecoin conversion and asset custody are executed by licensed and regulated partners, under their own permissions.

The full disclosure

Global payment orchestration for modern businesses.