| Question | Suggested Answer |
| What is cryptocurrency and virtual asset compliance? | Cryptocurrency and virtual asset compliance refers to the controls businesses use to detect, prevent, and report financial crime risks involving digital assets. This includes sanctions screening, AML monitoring, Travel Rule compliance, customer due diligence, counterparty risk checks, case management, and audit-ready reporting. |
| How is crypto compliance different from traditional finance compliance? | Crypto compliance combines traditional AML/CFT requirements with blockchain-specific controls, including wallet screening, blockchain transaction monitoring, Travel Rule data exchange, counterparty VASP due diligence, and multi-chain risk assessment. Unlike traditional finance, crypto transactions can be pseudonymous, cross-border, irreversible, and routed through self-hosted wallets or decentralized infrastructure. |
| Is Ospree right for my business? | Ospree is designed for regulated or compliance-conscious businesses handling virtual asset transactions, especially VASPs, exchanges, payment companies, asset managers, OTC desks, remittance firms, liquidity providers, and digital asset infrastructure companies. |
| What makes Ospree different from other crypto compliance solutions? | Ospree combines Travel Rule workflows, blockchain analytics, account data, case management, reporting, and API integration in a modular platform. This helps businesses manage compliance operations from transaction screening to regulatory reporting without relying on multiple disconnected tools. |
| Why do crypto service providers need a compliance solution? | Crypto service providers need compliance tools to meet AML/CFT, sanctions, Travel Rule, licensing, audit, and reporting obligations. A dedicated compliance solution helps teams reduce manual work, improve risk visibility, and maintain operational readiness as regulations evolve. |
| Is Ospree scalable? | Yes. Ospree is built as a modular platform that can support businesses as transaction volumes, user teams, jurisdictions, and compliance requirements grow. Customers can start with the modules they need and expand over time. |
| How does Ospree’s Accounts Directory support customer and compliance data management? | The Accounts Directory acts as a shared account layer that helps different Ospree modules reference consistent customer, account, and counterparty information. It can reduce duplication, streamline onboarding, and improve data consistency across Travel Rule, blockchain analytics, case management, and reporting workflows. |
| How do I partner with Ospree? | Companies can contact Ospree through the partner application or sales channels. Partnership opportunities may include blockchain ecosystems, compliance consultancies, data providers, infrastructure providers, and regional implementation partners. |
| Question | Suggested Answer |
| What is the Travel Rule? | The Travel Rule requires certain information about the originator and beneficiary of a transfer to be collected and transmitted between obliged institutions. For virtual assets, VASPs are expected to obtain, hold, and transmit required originator and beneficiary information securely when conducting qualifying virtual asset transfers. |
| What are Travel Rule protocols and service providers? | Travel Rule protocols are technical messaging standards used by VASPs to exchange required originator and beneficiary information in compliance with the FATF Travel Rule. Travel Rule service providers are the platforms that facilitate this exchange between regulated entities. Different providers and jurisdictions may use different protocols, messaging frameworks, and data-sharing requirements, which makes interoperability important. |
| Which protocols do you support? | Ospree is flexible and interoperable across multiple Travel Rule protocols and service platforms. Rather than taking a one-size-fits-all approach, connectivity is configured around each customer's counterparty network, jurisdictional requirements, and data-sharing frameworks — with security and data protection standards assessed as part of every integration. Ospree's integration portfolio and roadmap include TRP, CryptoSwift, CODE, TRISA, TRUST, and GTR. Contact our team to discuss your specific counterparty network or protocol requirements. |
| Who is the Financial Action Task Force, FATF? | FATF is the global standard setter for anti-money laundering, counter-terrorist financing, and counter-proliferation financing. Its standards influence how jurisdictions regulate financial institutions and virtual asset service providers. |
| What is the “Sunrise Issue,” and can Ospree help manage it? | The Sunrise Issue refers to uneven global implementation of the Travel Rule. Some jurisdictions require VASPs to exchange Travel Rule data, while others do not yet have equivalent rules or infrastructure. Ospree can help manage this through counterparty due diligence, alternative workflows, manual review, and secure data exchange options. |
| How does Ospree ensure compliance with the Travel Rule for cross-border transactions? | Ospree helps collect, validate, exchange, and record required originator and beneficiary information. It also supports counterparty VASP due diligence, protocol interoperability, wallet verification, escalation workflows, and audit-ready records. |
| How many Travel Rule data transfers can Ospree process? | Ospree is designed to support scalable Travel Rule data transfer volumes. Specific capacity, throughput, and service-level expectations should be confirmed during technical onboarding based on the customer’s volume profile. |
| Does Ospree conduct due diligence on counterparty VASPs? | Yes. Ospree supports counterparty VASP due diligence workflows to help businesses assess whether counterparties are regulated, legitimate, and operationally prepared to exchange Travel Rule information. |
| In which countries is the Travel Rule enforced? | Travel Rule implementation varies by jurisdiction and continues to evolve. Ospree helps customers monitor and manage multi-jurisdictional obligations, but customers should confirm local legal requirements with qualified counsel. |
| Do I need a Travel Rule solution if my country hasn’t adopted the Travel Rule yet? | It may still be useful. Even if your country has not implemented the Travel Rule, counterparties in enforced jurisdictions may require Travel Rule information before transacting with you. Preparing early can reduce friction and support future regulatory readiness. |
| Does Ospree support IVMS101? | Yes. Ospree supports IVMS101-aligned Travel Rule data structures. IVMS101 is a widely adopted messaging standard used to structure originator and beneficiary information for Travel Rule data exchange between VASPs. |
| Can Ospree support MiCA Transfer of Funds Regulation requirements? | Yes. Ospree can support workflows aligned with the EU Transfer of Funds Regulation, which extends information requirements to certain crypto-asset transfers involving crypto-asset service providers. Ospree helps collect, validate, transmit, and retain originator and beneficiary information, while supporting counterparty due diligence, reporting, and audit records. |
| Can Ospree support VARA, UK, EU, and Singapore compliance workflows? | Yes. Ospree is designed to support multi-jurisdictional Travel Rule and crypto compliance workflows, including configurations relevant to the UAE/VARA, UK, EU, and Singapore. Requirements vary by jurisdiction, so Ospree helps customers configure workflows for required data collection, counterparty review, risk checks, escalation handling, reporting, and audit evidence. |
| What happens when the counterparty VASP is not on the same Travel Rule network? | Ospree helps manage this through interoperability and counterparty outreach workflows. If a counterparty VASP is not on the same network or protocol, Ospree can support alternative workflows such as counterparty identification, due diligence, secure data exchange, invitation flows, manual review, or escalation depending on the customer’s policy and jurisdictional requirements. |
| How does Ospree handle failed, rejected, or incomplete Travel Rule transfers? | Ospree can support configurable workflows for failed, rejected, or incomplete Travel Rule transfers. This may include identifying missing originator or beneficiary information, flagging incomplete counterparty responses, creating review cases, escalating to compliance teams, retrying or resubmitting information, rejecting transfers, and retaining an audit trail of the decision. |
| Question | Suggested Answer |
| Does DORA apply to crypto-asset service providers? | Yes, if you operate in the EU. CASPs authorised under MiCA are explicitly in scope for DORA, as are the ICT third-party providers they rely on. |
| Does using Ospree make us DORA-compliant? | No — and any vendor that claims this should be treated with caution. DORA compliance is your organisation's obligation across your full ICT estate, governance framework, and operational processes. Ospree is designed to make your compliance technology infrastructure a strong and well-evidenced part of that programme. |
| What contractual documentation can Ospree provide for vendor due diligence? | We can provide our MSA, DPA, DORA Contractual Schedule, Security Overview, and sub-processor list. Contact your account manager or sales@ospree.io to request these. |
| Question | Suggested Answer |
| What is blockchain analytics, and why is it important for compliance? | Blockchain analytics helps businesses assess the risk of wallet addresses and transactions by identifying exposure to sanctions, illicit activity, fraud, hacks, mixers, darknet markets, scams, and other risk typologies. It is important because virtual asset transactions are public on-chain but often pseudonymous. |
| What methodology is used for risk scoring? | Risk scoring combines blockchain data, exposure analysis, attribution data, typology indicators, transaction history, sanctions lists, and configurable business rules. Ospree can help customers compare and operationalize risk insights from multiple analytics providers. |
| How does Ospree integrate blockchain analytics with Travel Rule processes? | Ospree can use blockchain analytics before, during, or after Travel Rule workflows to assess wallet and transaction risk alongside originator, beneficiary, and counterparty VASP information. This allows businesses to make better transfer decisions. |
| Can I request specific blockchain analytics features or updates for my business? | Yes. Ospree’s modular approach allows customers to discuss specific feature requirements, custom workflows, risk rules, integrations, and reporting needs. |
| Can I use Ospree without replacing my existing blockchain analytics vendor? | Yes. Ospree is designed to be data-agnostic, meaning customers can integrate existing blockchain analytics providers instead of replacing them. This allows compliance teams to centralize workflows, case management, Travel Rule data, reporting, and risk decisions while continuing to use their preferred analytics vendor. |
| How does Ospree’s blockchain analytics enhance risk assessment accuracy? | Ospree improves risk assessment by combining blockchain analytics with customer account data, Travel Rule information, counterparty information, rules, case workflows, and reporting. This gives compliance teams more context than a standalone score. |
| Is there a way to automate reporting for blockchain analytics in Ospree? | Yes. Ospree’s reporting capabilities can help teams generate audit-ready reports and reconcile blockchain analytics data with related compliance workflows. |
| What data sources are supported by Ospree’s Blockchain Analytics? | Ospree can work with blockchain data, wallet address risk indicators, transaction risk indicators, sanctions data, typology data, and third-party analytics provider outputs. Supported sources may vary by integration. |
| How many tokens does Ospree support? | Ospree supports multiple chains and tokens, with coverage depending on the selected modules and connected analytics providers. The supported asset list should be confirmed during onboarding. |
| What does data agnostic mean? | Data agnostic means Ospree is designed to work with multiple data sources and analytics providers rather than locking customers into one provider. This gives businesses more flexibility and helps support different risk methodologies. |
| Can Ospree perform real-time sanctions screening? | Yes. Ospree can support sanctions screening workflows for wallet addresses, transactions, and counterparties, depending on the customer’s configuration and integrated data providers. |
| Can Ospree help create comprehensive customer risk profiles? | Yes. Ospree can help build customer risk profiles by combining wallet exposure, transaction behavior, Travel Rule information, account data, counterparty relationships, and case history. |
| What are false positives, and how does Ospree reduce them? | False positives are alerts that are flagged as risky but, after review, do not represent actual compliance concerns. Ospree helps reduce false positives by combining multiple data points, configurable rules, contextual risk assessment, case management, and workflow controls so compliance teams can prioritize genuinely material risks. |
| Question | Suggested Answer |
| How customizable is the API for different business needs? | Ospree’s API is designed to support flexible integration across different compliance workflows, including Travel Rule, blockchain analytics, account data, case management, and reporting. Customers can integrate based on their internal systems and operational requirements. |
| How do I report an issue or bug related to the API? | API issues can be reported through Ospree’s customer support channel. Customers should include the endpoint, request ID, timestamp, environment, error message, expected behavior, and screenshots or logs where possible. |
| Are there usage limits for Ospree’s API? | API usage limits depend on the customer’s plan, expected transaction volume, and technical configuration. Rate limits and throughput expectations should be reviewed during onboarding. |
| How long does it take to complete an integration? | Integration timing depends on the customer’s systems, selected modules, API scope, internal engineering resources, and testing requirements. Simple integrations may be faster, while enterprise implementations may require additional configuration and validation. |
| What level of integration support does Ospree provide for third-party systems? | Ospree can provide API documentation, technical onboarding, integration guidance, testing support, and troubleshooting for third-party system integrations. |
| Can Ospree handle high transaction volumes through the API? | Yes. Ospree’s API is designed for scalable compliance operations and high-volume workflows. Customers with high-volume requirements should review expected throughput, rate limits, and resilience requirements during technical onboarding. |
| How does Ospree ensure API security during integration? | Ospree secures API integrations using authentication, encrypted connections, access controls, secure configuration, logging, and monitoring. Customers should also follow secure credential management and least-privilege access practices. |
| Does Ospree provide error handling and logging in the API? | Yes. Ospree’s API should provide structured responses and logging support to help customers identify, investigate, and resolve integration issues. |
| What documentation and support are available for API integration? | Ospree provides developer documentation, integration support, and customer guidance to help teams connect Ospree with internal systems and third-party tools. |
| Is the Accounts Directory interoperable with external systems? | Yes. The Accounts Directory is designed to interoperate with external systems through APIs and integrations, helping customers connect Ospree with internal compliance, customer, or transaction systems. |
| Does the Accounts Directory support standardized data formats? | Yes. The Accounts Directory is designed to support standardized data exchange across Ospree modules and integrated systems, including Travel Rule-related data structures where applicable. |
| Question | Suggested Answer |
| How secure is Ospree, and how is data stored and managed? | Ospree applies enterprise-grade security controls, including encrypted connections, encryption at rest, access controls, role-based permissions, and data retention practices. Customer data is managed according to contractual, operational, and applicable legal requirements. |
| What certifications do Ospree’s data centers have? | Ospree uses cloud infrastructure and data centers aligned with recognized security standards such as ISO 27001, ISO 27017, and ISO 27018. For procurement or vendor due diligence, Ospree can provide further security documentation through the appropriate review process. |
| Does Ospree support multi-user access with role-based permissions? | Yes. Ospree supports multi-user access and role-based permissions so organizations can manage user responsibilities, restrict access to sensitive information, and support internal compliance governance. |
| Where is data stored? | Data storage depends on Ospree’s cloud infrastructure configuration and customer requirements. For enterprise customers, data residency and infrastructure details can be reviewed during onboarding or procurement. |
| Is Ospree GDPR compliant? | Ospree is designed to support GDPR-aligned data protection practices where applicable. Organizations should define controller and processor responsibilities when processing personal data. |
| How secure is the data stored in Ospree’s Accounts Directory? | Data in the Accounts Directory is protected through access controls, encryption, permission management, and secure infrastructure practices. Access should be limited based on user roles and operational needs. |
| What audit logs are available? | Ospree can provide audit logs that record key compliance and operational events, including user actions, Travel Rule transfer status changes, data submissions, counterparty interactions, case activity, rule-triggered alerts, API events, and reporting actions. These logs help teams evidence compliance decisions, investigate issues, and prepare for audits or regulatory reviews. |
| Does Ospree offer a trial period? | Ospree may offer trial or evaluation access depending on the customer profile, use case, and onboarding requirements. Prospective customers should contact the sales team to discuss trial eligibility. |
| How do you price your solution? | Ospree pricing depends on selected modules, number of users, transaction volumes, blockchain analytics usage, integration needs, and support requirements. Customers can choose a plan based on their operational and compliance needs. |
| Does Ospree offer a start-up package? | Yes. Ospree can support start-ups and smaller teams with entry-level packages designed to make compliance infrastructure more accessible while allowing customers to scale as usage grows. |
| Is there a minimum contract length required? | Ospree typically operates with defined subscription terms. The exact contract length depends on the selected plan, customer requirements, and commercial agreement. |
| Question | Suggested Answer |
| How quickly are support tickets addressed? | Support response times depend on the customer’s plan, severity of the issue, and support agreement. Critical issues are prioritized, while general requests are handled according to standard support workflows. |
| What training resources does Ospree provide for platform adoption? | Ospree can provide onboarding support, documentation, user guidance, API documentation, and training sessions to help teams adopt the platform effectively. |