Which APAC & ME markets is Taxbit live in today? +
In APAC, Taxbit supports regulatory reporting across Singapore, Australia, New Zealand, the United Arab Emirates, and Hong Kong, with coverage expanding as jurisdictions publish new requirements. These sit within our broader global coverage of 70+ reporting jurisdictions.
Can we start with one framework and add jurisdictions over time? +
Yes. The platform is modular. Teams can start with CARF and CRS 2.0 and extend into jurisdiction-specific reporting requirements on the same platform as their operating footprint grows.
Does CARF apply only to crypto exchanges, or also to payment and fintech platforms? +
CARF scope is based on activity, not company type. It applies to any business that effectuates crypto-asset transactions for customers, which can include exchanges, custodians, brokers, and payment or fintech platforms that handle digital assets. A platform with no crypto-asset activity is generally outside CARF, though it may have obligations under other reporting regimes.
Not sure which applies to your platform? Talk to one of our CARF specialists
What is the difference between CARF and CRS 2.0, and which applies to our platform? +
CARF covers crypto-asset transactions at the transaction level. The amended CRS, often called CRS 2.0, covers financial account information and now extends to certain digital financial products, including some stablecoins and e-money tokens that fall outside CARF. Many platforms have obligations under both, and which applies depends on the products and services offered.
Read more: CARF and CRS 2.0: What's the difference?
How does Taxbit fit alongside our existing stack? +
Taxbit is API-first and connects to existing source systems through APIs and batch ingestion, with data collection embedded into current workflows rather than replacing them. Taxbit maintains the schema and jurisdiction-specific logic, so internal engineering does not have to re-implement rules as requirements change.
.png)
