A stablecoin transfer settles on a blockchain in seconds. The compliance obligations attached to it do not settle themselves. The institution sending it has to identify the counterparty, exchange originator and beneficiary information, assess the risk, and keep a record of what was decided and why.
Ospree builds the infrastructure for that work. This primer is written for financial institutions, digital asset businesses, and the lawyers and compliance officers who advise them. It covers what Ospree does, how a transfer moves through the product, how self-hosted wallets are handled, and the terms you will meet along the way. It takes about ten minutes to read.
What Ospree does
Ospree provides compliance infrastructure for stablecoins and other digital assets. We help institutions that transfer digital assets identify their counterparties, exchange required customer information, assess risk, and keep evidence of their decisions.
The same obligations apply whether the asset is a fiat-backed stablecoin used for settlement or another digital asset. With manual steps and disconnected tools, transfers stall while teams wait on counterparties. Exceptions are chased by hand. When a regulator or auditor asks for evidence, it is scattered across systems. Ospree replaces that with one workflow:
Transfers keep moving. Each transfer gets a route: a Travel Rule message to the counterparty, a stored record, or a wallet ownership verification.
Less manual work. Rules handle the routine cases, so people review only the exceptions.
Evidence on demand. Every check and decision is kept as an audit record.
One integration, not many. Travel Rule messaging, self-hosted wallet verification, blockchain analytics, a rule engine, case management, and reporting share one API and one Console.
Room to grow. Institutions start with the modules they need and add more as they expand.
In one sentence: Ospree helps institutions meet their compliance requirements for stablecoin and digital asset transfers while keeping those transfers moving and cutting manual work.
How a transfer moves through Ospree
Customers use Ospree through the web Console, the REST API, or both. The API connects Ospree to their existing systems. The Console is where their teams review transfers, manage exceptions, and investigate cases.
Each customer is set up as a Business with its own users, customer accounts, and segregated data. In a typical Travel Rule transfer, the sending Business identifies the counterparty, checks which messaging routes are available, and creates one of two transfer types:
Instruction. Exchanges Travel Rule information with the counterparty through a supported protocol. Used when a compatible messaging route exists.
Record. Stores the information without sending a message. Used when there is no compatible route, or when the transfer involves a self-hosted wallet.
Depending on their modules, customers can also screen blockchain addresses with blockchain analytics, verify wallet ownership, and apply their own compliance rules. Transfer history, statuses, and audit records help teams track outcomes and handle exceptions.
Where responsibility sits. Ospree supports the compliance workflow. The customer remains responsible for its compliance decisions and for executing the blockchain payment. Ospree does not hold or move customer funds. For technical detail, see the product documentation.
Who uses Ospree
We serve banks, payment providers, custodians, digital asset exchanges, OTC desks, and other financial institutions that handle stablecoins and digital assets. Inside each institution, different teams use Ospree for different reasons:
Compliance and legal teams assess risk, review exceptions, and retrieve audit records.
Operations teams manage transfer workflows.
Developers integrate the API.
Management uses it for oversight and reporting.
We sell directly and through white-label partners, who offer Ospree under their own brand. Each partner’s client remains its own Business, with its own VASP identity and segregated data.
The Travel Rule in two minutes
The Travel Rule comes from FATF Recommendation 16. It requires covered institutions to obtain, hold, and transmit specified information about the originator (sender) and beneficiary (receiver) of a transfer. For digital assets, including stablecoins, the sending and receiving service providers exchange that information with each other.
The payment and the data travel separately. A blockchain transaction moves assets between addresses but usually carries no customer identity. The compliance information goes through a separate channel. A typical workflow looks like this:
The sending institution collects the required originator and beneficiary information.
It identifies the receiving institution and exchanges the information through an available channel.
Both institutions run their checks, handle exceptions, and retain evidence.
Requirements vary by jurisdiction, including thresholds, data fields, and timing. Ospree provides the infrastructure for these workflows. Each customer decides which rules and decisions apply to its business.
Self-hosted wallets: verifying wallet ownership without a test transfer
Self-hosted wallets are different. When a customer withdraws to a wallet they control themselves, there is no institution on the other side to exchange Travel Rule data with. Regulators treat these transfers as higher risk. Some regimes, the EU Transfer of Funds Regulation among them, require providers in certain cases to verify that the customer owns or controls the wallet.
The common workarounds are weak. Screenshots are easy to fake. Small test transfers are slow and cost network fees. With Ospree, the customer proves control of the wallet by signing a message, in five steps:
Choose the wallet. The customer selects the self-hosted address they want to use.
Send the request. Ospree creates a one-time message based on the CAIP-122 standard, locked to Ospree’s domain and protected by a single-use code and timestamps so it cannot be reused. Through the API, the business sends the customer a secure link by email, SMS, or in-app message.
Sign. The customer signs the message in their wallet. It is instant, costs no network fees, moves no funds, and the private key never leaves the wallet.
Verify. Ospree checks that the signature matches the address and that the message is valid and unexpired.
Record. Ospree links the proof to the customer’s verified identity and saves an audit record. The wallet is labelled self-hosted, screened for risk, and recognised on future transfers.
Institutions value it for four reasons:
Better experience: verification takes seconds and costs the end customer nothing.
Stronger evidence: a cryptographic signature is far harder to fake than a screenshot.
Broad coverage: Ethereum and EVM-compatible chains, Solana, Bitcoin, and Tron, across 40+ wallets.
Audit-ready: every verification is stored with the message, signature, timestamps, and outcome.
A point for counsel. Proving control of a wallet is not the same as proving legal ownership. That is why Ospree ties the proof to the customer’s KYC record and applies risk-based checks. The full detail is in the Self-Hosted Wallet guide.
Who we are
Ospree is a remote-first B2B software company, with a team based across Europe, Asia, and the USA. Our founder’s background spans banking, compliance, and computer science, and that shapes how we work: understand the operational and regulatory problem first, then build technology that makes it easier to handle.
Our customers operate across jurisdictions and use different technology providers. So we connect fragmented compliance systems, messaging protocols, and workflows, and keep interoperability and modularity at the centre of the product.
Our work depends on trust. We handle sensitive information, describe our capabilities accurately, and respect customer data boundaries. We never share customer data with other companies for their own use. Any authorised exchange must serve the customer’s intended workflow.
Platform data is hosted on Google Cloud. The default region is Frankfurt, Germany. Where a customer’s data residency requirements call for it, data can be hosted in the United States or another jurisdiction. Our uptime and support commitments are in the Service Level Agreement, and every third party that may process customer data is listed in the Subprocessor Register.
Key terms
Digital asset: a digital representation of value that can be transferred on a blockchain. FATF uses the term virtual asset.
Stablecoin: a digital asset designed to hold a stable value against a reference asset, usually a fiat currency.
VASP: virtual asset service provider. An exchange, custodian, or similar regulated digital asset business. EU law uses the term crypto-asset service provider (CASP).
AML: anti-money laundering, the controls that keep criminal funds out of the financial system.
FATF: the Financial Action Task Force, the global body that sets AML standards.
Travel Rule: obtaining, holding, and passing on originator and beneficiary information with each transfer (FATF Recommendation 16).
Originator and beneficiary: the sender and the receiver of a transfer.
Self-hosted wallet: a wallet the owner controls directly, with no VASP behind it.
Instruction: a transfer that exchanges Travel Rule data with the counterparty through a supported protocol.
Record: a transfer that stores Travel Rule data without sending a message.
Console: Ospree’s web app for reviewing transfers, managing exceptions, and investigating cases.
IVMS101: the shared data format for Travel Rule messages.
KYC: know your customer. Verifying who a client is.
Read more
Product documentation: how the platform and API work.
FATF: Updated Guidance on Virtual Assets and VASPs (2021): the official source of the Travel Rule for virtual assets, including stablecoins.
FATF: Best Practices in Travel Rule Supervision (2025): how supervisors check Travel Rule compliance today.
This article is general information, not legal advice. To see a stablecoin transfer go from policy check to audit record, Request a Demo.

