Sell sales tax and VAT compliance as your own product, verify every merchant, and file the 1099-K, DAC7 and DAC8 reports you owe.
Offer indirect tax compliance as your own product: real-time calculation, exposure and threshold tracking, e-invoicing, registration and filing across 150+ jurisdictions, embedded in your platform and branded as yours. Plus verified tax identity: merchants at onboarding, payees before money moves, B2B exemption validation for their customers. And the reporting you owe yourself: 1099-K, DAC7 and DAC8.
Platforms come to TaxDo for two different reasons, and they are worth separating. One is a revenue opportunity you choose to take. The other is a filing obligation that already applies to you.
Capabilities you embed, brand as yours and sell to the merchants already on your platform. Discretionary, revenue-generating, and yours to price.
Reporting duties that fall on the platform itself, not on your merchants. Not discretionary, dated, and enforced with penalties per record and per filing.
Your merchants owe sales tax, VAT and GST on the transactions you process, and increasingly must issue structured e-invoices to get paid at all. Today they solve that with a separate vendor. Sell it to them instead — calculation, exposure tracking, registration and filing, delivered through one integration, priced by you and branded as yours.
A single call returns the correct sales tax, VAT or GST for any transaction you process — resolving state, county, city and district layers in the US, destination VAT rates across the EU and UK, and GST regimes worldwide, per merchant and per line item. Sub-second determination, called synchronously inside your payment or invoicing flow.
Structured invoices generated in each destination's mandated format with verified seller and buyer tax numbers embedded, and transmitted over Peppol. As ViDA and national mandates take effect, e-invoicing becomes a requirement for your merchants and a product capability for you.
Sales tax, VAT and GST registration and return filing offered to merchants under your brand. Registration lifecycle, filing calendar, remittance and status are managed per merchant inside your single tenant. Offered as a paid tier or bundled differentiator, configured per merchant.
You already hold every merchant's transaction volume by jurisdiction — the exact data needed to detect a registration obligation. Surface nexus and VAT threshold alerts as a retention feature before your merchants discover the obligation in an audit. US economic nexus plus EU distance selling and non-resident VAT and GST thresholds.
Merchants selling B2B need valid resale and exemption certificates on file before an exempt transaction is processed. Collection, validation, storage, expiry tracking and automatic application run inside your flow. Multistate Tax Commission and Streamlined Sales Tax forms plus state-specific formats.
Your processing, subscription and platform fees carry their own indirect tax treatment, which differs by customer location and by whether the service is exempt financial intermediation or a taxable digital service. Determined on the same engine as your merchants' transactions. Applied per fee type, per merchant jurisdiction and per contracting entity.
Three jobs, one verified record. Verify the merchant you onboard, verify the payee before money moves, and verify the business customers your merchants grant exemptions to. Checked against official government sources in 130+ countries, with sanctions screening returned on the same call — and resold to your merchants as part of your offering.
Validate a merchant's tax identification number and legal business registration against official government sources in real time inside your onboarding flow. Legal name, registration number, status and entity type returned structured, so clean merchants auto-approve and only exceptions reach review.
Before a payout, supplier payment or invoice settlement leaves your platform, confirm the beneficiary is a real, currently registered business at the tax number given — not a lapsed entity, a mismatched name or a screening hit. The business verification check runs in the payment flow, not after it. Built for AP automation, payout, creator and marketplace platforms moving funds to third parties.
Your merchants sell B2B and must zero-rate or reverse-charge only against a verified registration. Validation runs at invoice time inside your platform, the evidence is retained with the transaction, and the capability is theirs to use — sold by you. EU VIES, HMRC and national tax authority databases, checked in real time.
Screen every merchant, payee and beneficial owner against official sanctions lists, watchlists and adverse media on the same verified identity record used for tax — one check, not two disconnected vendors and two invoices. 290+ authoritative sources, at onboarding and continuously thereafter.
Registrations lapse, deregister and change status after onboarding. Continuous monitoring detects the change and alerts you, so a stale record does not silently invalidate a tax treatment, a payout decision or a reporting position. Webhook alerts on deregistration, status change or new screening match.
Verify an existing merchant or payee book in bulk rather than record by record. Every entry returns a status and exception reason, so only failures and near-matches need attention and the rest flow straight into tax determination and reporting. Batch and SFTP interfaces sized for portfolios of any scale.
This is the part that is not optional. If you settle funds to sellers, facilitate transactions, hold client money, issue e-money or touch crypto rails, the reporting obligation sits with your platform — not with your merchants. DAC8 has applied since 1 January 2026, with first reports due January to September 2027. Due diligence, income aggregation and schema-compliant filing run on the merchant records you already verified.
Payee tax identification numbers collected and validated, current reporting thresholds applied, TIN matching performed to prevent mismatch notices, filings generated and payee statements produced. Backup withholding logic applies where a TIN is missing or fails matching. Built for payment settlement entities and third-party settlement organisations.
DAC7 reporting covers seller due diligence, tax identity verification, income aggregation by activity type and jurisdiction, and annual XML reporting to the competent authority. Relevant activities: sale of goods, personal services, immovable property rental and transport rental. Reportable sellers determined automatically from the transactions you already process.
DAC8 is widely read as a crypto-exchange rule. It is broader. Platforms holding an e-money licence, issuing e-money tokens or running stablecoin and crypto rails can fall in scope — which captures a large share of modern payment institutions and payout platforms.
Merchants and sellers never fill a tax form. A conversational interview asks plain questions, validates tax residency and identity in real time, presents a pre-populated certification for digital signature, and returns a completed record — on your domain, under your brand. One interview satisfies multiple frameworks where a seller is in scope for more than one.
Conflicting or incomplete seller data is detected, tested for reasonableness against the verified identity record, and resolved automatically wherever it can be — so your compliance team reviews exceptions rather than the whole book. 95%+ of discrepancies resolved without manual intervention.
Platforms holding client funds or dealing in crypto-assets can fall within financial account and crypto-asset reporting alongside DAC7 and DAC8. Reports are generated in each authority's required schema, validated before submission and filed with a full audit trail from source transaction to acknowledgement. One verified merchant record serves every framework. Filing status, rejections and corrections tracked per jurisdiction.
Scope turns on your licence type, where your merchants are established and what you actually settle — and it is genuinely fact-specific. Most platforms discover they are in scope for more than one framework, and a few discover they are in scope for none. We will walk your licence and settlement model against each regime and tell you plainly which apply, before any commercial conversation.
Request a Scope ReviewPayment processing is commoditised and margins are compressed. Tax compliance is the capability your merchants already pay someone else for — and the one you are best positioned to sell them, because you already hold the transaction data it runs on.
Your merchant remains the taxpayer. TaxDo provides the determination, the verification and the filing mechanics; the merchant retains the registration, the tax position and the obligation to the authority. Embedding the capability in your platform does not transfer their tax liability to you, and the contractual structure is written to make that boundary explicit.
Every determination is stored with the rule version, rate and evidence applied at the time of the transaction, so your merchant — not your support team — can answer an audit.
Commercial terms are agreed per partner and structured around how you go to market — whether you price the capability yourself, bundle it to reduce churn, or run it as a shared revenue line. Bring your merchant mix and volume profile to the first conversation and we will model it with you.
Verify the merchant once, then reuse that record for every tax determination and every report — Tax Identity, Indirect Tax and Regulatory Compliance.
Tax identification number, business registration and sanctions screening validated against official sources during your onboarding flow. Clean merchants activate automatically; exceptions route to review with a reason attached.
Every processed transaction returns the correct sales tax, VAT or GST, with structured e-invoices issued in the destination format where a mandate applies. Nexus and threshold alerts surface to the merchant under your brand.
Merchant VAT and sales tax returns are filed on schedule, and your own 1099-K, DAC7 and other framework reports are generated and submitted from the same verified records — no second data collection.
Four exposures sit with the platform rather than the merchant — and none of them can be pushed downstream.
Onboarding merchants on self-declared tax numbers produces mismatch notices, failed filings and backup withholding obligations — and leaves the platform, not the merchant, answering for the data.
Settling funds to sellers usually makes the platform a reporting entity. Failing to identify reportable sellers, or reporting on unverified identity data, carries penalties per record and per filing.
As ViDA and national mandates take effect, an invoicing platform that cannot issue structured invoices in the destination format stops being usable in that market — and merchants migrate to one that can.
Merchants increasingly expect tax handled inside the platform that processes their payments. A platform without it competes against one where compliance is already solved.
Your merchants never see TaxDo. Every flow runs on your domain, under your brand, from a single integration serving your whole book.
Merchant-facing flows on your domain with your branding, and verification and reminder emails from your sender. A config portal controls what each merchant tier sees.
REST APIs for verification, determination, e-invoicing and reporting. Embeddable flows where you would rather not build the screens. Webhooks, SFTP and batch for volume.
One integration serving many merchants with data segregated per tenant. Dedicated single-tenant and on-premise deployments where your regulatory position requires them.
We will respond to you at any time.
Just use our help center or contact us.
Yes. White-label is the default deployment for platforms. Merchant-facing flows run on your domain, not a TaxDo subdomain, with your branding and your email sender for verification and reminder messages. Your merchants never see TaxDo. A configuration portal lets you control branding, messaging, thresholds and which capabilities are exposed to which merchant tiers.
TaxDo validates a merchant's tax identification number and business registration against official government sources in real time during your onboarding flow, through a single API call. Coverage spans 130+ countries, 1,000+ tax ID types and 120+ official business registries, with sanctions, watchlist and adverse media screening returned on the same record. Results are structured so you can auto-approve clean merchants and route only exceptions to manual review.
Yes. Payment settlement entities and third-party settlement organisations must report payee gross transaction volume to the IRS and furnish statements to payees. TaxDo collects and validates payee tax identification numbers, applies current reporting thresholds, performs TIN matching to prevent mismatch notices, generates the filings and produces payee statements. Backup withholding logic is applied where a TIN is missing or fails matching.
DAC7 requires digital platforms operating in the EU to collect and verify seller tax identity information, track seller income by activity and jurisdiction, and report it annually to a competent authority in XML. It applies to platforms facilitating the sale of goods, personal services, rental of immovable property and rental of transport. Payment platforms that facilitate transactions between sellers and buyers frequently fall in scope. TaxDo handles seller due diligence, verification, income aggregation and schema-compliant XML filing on the same platform as your merchant onboarding.
VAT in the Digital Age introduces structured electronic invoicing and digital reporting requirements across the EU, and member states are already mandating e-invoicing on their own timetables. In practice any invoicing or billing platform serving EU customers must become capable of issuing structured invoices carrying verified seller and buyer tax numbers in each destination format, and of transmitting them over a network such as Peppol. TaxDo provides the format generation, the network access and the identity verification underneath, so you add e-invoicing as a product capability rather than a compliance project.
Yes. Platforms typically expose tax calculation, registration monitoring and filing as a paid tier or a bundled differentiator. TaxDo returns the determination through your API and your interface, and supports per-merchant configuration so each merchant's jurisdictions, product taxability and registration status are handled independently within your single integration. Commercial terms for platform distribution are agreed per partner.
Existing portfolios are verified in bulk rather than merchant by merchant. Tax identification numbers and business registrations across your book are validated against official sources, screened against sanctions and watchlist sources, and returned with a status and exception reason per merchant. Only failures and near-matches require attention, and the verified records then feed reporting and tax determination without a second data collection exercise.
All three. REST APIs cover verification, tax determination, e-invoicing and reporting for platforms building their own interface. Embeddable flows are available where you would rather not build the merchant-facing screens, including a white-label self-certification interview that collects and validates tax identity information conversationally and returns a signed, completed record. Webhooks, SFTP and batch interfaces support high-volume and asynchronous workflows.
It may. DAC8 is widely read as a crypto-exchange rule, but its scope is broader and can reach platforms that hold an e-money licence, issue e-money tokens, or operate stablecoin and crypto rails alongside conventional payment services. That captures a large share of modern payment institutions, payment facilitators and payout platforms. DAC8 has applied since 1 January 2026 across the 27 EU member states, with first reports due January to September 2027. Whether your specific licence and activity bring you in scope is fact-specific, so treat this as a prompt to check rather than a conclusion, and we will walk your licence and settlement model against the regime with you.
Possibly. DAC7 applies to platforms that allow sellers to connect with users to carry out a relevant activity, which covers the sale of goods, personal services, rental of immovable property and rental of transport. The test is about facilitation, not about whether you call yourself a marketplace. Payment platforms, payout providers and billing platforms that sit between a seller and their customer frequently fall in scope even where the commercial relationship looks purely like payment processing. Because the analysis turns on your contractual position and what you actually facilitate, it is worth a scope review rather than an assumption in either direction.
No. Your merchant remains the taxpayer. TaxDo provides tax determination, identity verification and filing mechanics; the merchant retains the registration, the tax position and the obligation to the authority. Embedding the capability in your platform does not transfer their liability to you, and the contractual structure is written to make that boundary explicit. Every determination is stored with the rule version, rate and evidence applied at the time of the transaction, so the merchant can evidence their own position in an audit.
Terms are agreed per partner and structured around your go-to-market. Some platforms price the capability themselves and treat it as a margin product, some bundle it into a premium tier to reduce churn, and some run it as a shared revenue line. The right structure depends on your merchant mix, volume profile and whether tax is positioned as a differentiator or an upsell. Bring those details to the first conversation and we will model the economics with you.
Yes. Before a payout, supplier payment or invoice settlement leaves your platform, TaxDo confirms the beneficiary is a real and currently registered business at the tax number provided, checks the legal name and status against official registries, and screens against sanctions and watchlist sources. The check runs inside the payment flow rather than as a periodic review, so a lapsed entity, a name mismatch or a screening hit is caught before funds move.
Yes. The platform is built for one integration serving many merchants, with data segregated per merchant and per platform tenant. Merchant-level configuration, jurisdiction coverage, registration status and reporting obligations are maintained independently. Dedicated single-tenant and on-premise deployments are available where a platform's regulatory position requires them.
Payment and billing platforms are the one segment that runs the entire operating system — because your merchants generate every kind of obligation it covers.
Real-time calculation, VAT and GST determination, e-invoicing and Peppol, registration, threshold monitoring and filing for the merchants on your platform.
Merchant tax ID verification, business registry checks, sanctions screening and continuous re-verification across 130+ countries.
1099-K, DAC7, CRS 2.0, DAC8 and CARF reporting with white-label self-certification and schema-compliant XML filing.
Calculation, exposure tracking, registration and filing, merchant and payee verification — embedded in your platform, branded as yours, and priced by you. One integration, your entire merchant book.
Get in touch
