Platform Income from Multiple Countries?

You have a Stripe account collecting payments from clients in the US, UK, and Germany. You sell digital products through Gumroad to customers in 40 countries. You do freelance work on Upwork for companies in Singapore and Australia. Your Amazon KDP royalties come from seven different Amazon marketplaces.

Where is that income "from"?

The answer depends on which tax authority is asking. And when you are earning through multiple platforms in multiple countries, several tax authorities are asking simultaneously — often reaching different conclusions about the same dollar.

Income sourcing is not where you get paid

The first confusion is between where money lands and where income is sourced. A payment hitting your Stripe account in USD does not mean the income is US-sourced. A payment from a German client for work you performed in Portugal is German-sourced, Portuguese-sourced, or both, depending on the analysis framework.

Income sourcing rules differ by country and by income type:

• Services income: Generally sourced where the work is performed. A developer in Portugal writing code for a US client is earning Portuguese-source income under most frameworks, regardless of where the client or payment processor is located.
• Royalties: Generally sourced where the intellectual property is used. Amazon KDP royalties from the UK marketplace are UK-sourced royalties.
• Sales of goods: Generally sourced where title passes or where the buyer is located, depending on the jurisdiction.
• Digital products/SaaS: This is where it gets complicated. Different countries apply different rules. The EU generally treats digital services as sourced where the customer is located. The US generally treats services income as sourced where the work is performed.

The invoice trail analysis maps how the same payment can be classified differently at each step — by the platform, by the payer's country, and by the founder's country.

The 1099-K reporting landscape

If you have a US-based Stripe account, PayPal business account, or receive payments through any US payment processor, those platforms report to the IRS.

The 1099-K threshold for 2026 tax year reporting:

The $5,000 threshold (lowered from $20,000 in prior years under the American Rescue Plan Act) captures most active freelancers and small business owners. If your gross Stripe volume exceeds $5,000 in 2026, Stripe sends the IRS a 1099-K showing that total.

The critical detail: 1099-K reports gross payments, not net income. Refunds, Stripe fees, cost of goods, and expenses are not subtracted. If you processed $50,000 through Stripe but $10,000 was refunds and $2,000 was fees, the 1099-K reports $50,000. The reconciliation happens on your tax return, not on the 1099-K. If the numbers do not reconcile clearly, that gap is visible to the IRS.

Multiple platforms, multiple 1099-Ks

A founder using Stripe for direct sales, Gumroad for digital products, and Teachable for courses may receive three separate 1099-Ks. Each reports gross volume through that platform. None of them coordinate with each other.

Your tax return needs to reconcile all of them with your actual income. If total 1099-K income across three platforms is $80,000 but your reported gross revenue is $65,000 (because $15,000 was refunds, chargebacks, and duplicate payments), you need documentation that explains the gap. Without it, the IRS sees unreported income.

The payment processor comparison maps the structural differences between processors — including which ones issue 1099-Ks and which handle tax remittance on your behalf. This distinction matters because platforms like Paddle act as the Merchant of Record, meaning they report the income as their own (with a payout to you) rather than reporting your gross sales to the IRS.

VAT/GST obligations from platform sales

If you sell to customers in the EU, UK, Australia, or other jurisdictions with digital services taxes, those sales may trigger VAT or GST obligations regardless of where you are located.

EU VAT on digital services

The EU's One-Stop Shop (OSS) framework requires that businesses selling digital services to EU consumers charge VAT at the rate applicable in the customer's country. For 2026:

• EU threshold: If your total EU B2C digital sales exceed EUR 10,000 per year, you charge VAT at the customer's local rate (ranging from 17% in Luxembourg to 27% in Hungary)
• Below threshold: You can charge your home country's VAT rate (or zero if you are outside the EU)
• OSS registration: Allows you to file a single VAT return covering all EU member states

If you sell a $50 digital product to a customer in Germany, you owe 19% VAT on that sale — $9.50 to the German tax authority. If you sell to a French customer, you owe 20%. Each sale generates a VAT obligation in the customer's country.

Some platforms handle this for you. Paddle, Lemon Squeezy, and Gumroad (when acting as merchant of record) collect and remit VAT on your behalf. Stripe does not — you are responsible. The Stripe vs Paddle vs Lemon Squeezy comparison maps which platforms handle tax remittance and which leave it to you.

UK VAT

The UK's digital services VAT applies to non-UK businesses selling to UK consumers. There is no registration threshold for non-established businesses — any B2C digital sale to a UK customer triggers a UK VAT obligation. The rate is 20%.

Australia GST

Australia's GST on low-value imports applies to non-resident businesses selling digital products to Australian consumers if your Australian turnover exceeds AUD 75,000. The rate is 10%.

The structural problem

For a founder processing sales through Stripe to customers in 30+ countries, the VAT/GST landscape creates obligations in potentially dozens of jurisdictions. Most founders either use a Merchant of Record platform (which handles all of this) or are unaware of the obligations.

The gap between "I sell digital products globally" and "I have VAT registration obligations in 27 EU member states" is the core structural exposure for platform-dependent founders selling direct. This is one reason why the platform risk analysis flags payment processor choice as a structural decision, not just a fee comparison.

Platform withholding vs. self-reporting

Different platforms handle tax differently:

Withholding platforms: Some marketplaces withhold tax on your behalf. Amazon KDP withholds 30% on US-source royalties paid to non-US persons (unless a tax treaty reduces the rate and you have a valid W-8BEN on file). Upwork may withhold on certain payments. Apple's App Store withholds in some jurisdictions.

Reporting-only platforms: Stripe reports via 1099-K but does not withhold. PayPal reports but generally does not withhold (except for certain backup withholding situations). Wise does not withhold.

Merchant of Record platforms: Paddle, Lemon Squeezy, and (in some configurations) Gumroad act as the seller of record. They collect payment from the customer, handle VAT/GST, and pay you a net amount. Your tax reporting is simpler — you report the net payout as revenue — but the gross-to-net reconciliation happens on their side.

The structural question: do you know which of your platforms reports what, to which tax authority, with what classification? If you cannot answer that, the documentation gap between what platforms report and what you report is a source of potential misalignment.

When platforms report to multiple countries

Stripe has entities in multiple jurisdictions. Depending on how your Stripe account is set up, reporting may go to the IRS, to HMRC, to the Irish Revenue Commissioners, or to another national tax authority.

PayPal reports to the IRS for US accounts and to local tax authorities for accounts in other jurisdictions under various information-sharing agreements.

Amazon reports marketplace sales data to tax authorities in the EU under DAC7 — a directive that requires digital platforms to report seller information and transaction data to EU member states.

If you operate across platforms in multiple countries, the information being reported about your income arrives at different tax authorities at different times, in different formats, with different classifications. The founder's tax return needs to be consistent with all of these reports simultaneously. The narrative consistency analysis maps what happens when different institutions see different stories about the same income.

Income attribution for multi-country work

A freelance developer on Upwork takes projects from a US company, a UK company, and an Australian company. All payments flow through Upwork to a US bank account. Three clients, three countries, one payment channel.

For US tax purposes, the income sourcing depends on where the work was performed, not where the client is located. If the developer performed all work from Portugal:

• The income is Portuguese-source under most analyses
• The US clients may still issue 1099s or generate 1099-K reporting (because the payment processor is US-based)
• Portugal may tax the income as Portuguese-source employment or self-employment income
• The US may or may not have a claim depending on the developer's US tax status

For a US citizen, the US taxes worldwide income regardless of source — so the sourcing question affects foreign tax credit calculations rather than whether the income is taxable. For a non-US person, the sourcing question determines whether the US has any taxing right at all.

The platforms do not resolve this for you. Upwork does not know where you are sitting when you write code. Stripe does not know whether the payment it processes is for services performed in the US or in Thailand. The income attribution analysis is yours to perform, and it requires tracking where work was actually done for each payment received. The cross-border compliance checklist maps the full set of reporting obligations that flow from this analysis.

Practical mapping for platform founders

If you earn through multiple platforms across multiple countries, the structural exposure compounds with each additional platform and jurisdiction. Mapping it starts with four questions:

1. Which platforms report to which tax authorities? List every platform that processes your payments. For each, identify whether it issues a 1099-K, withholds tax, or reports to a non-US tax authority. This determines what information tax authorities already have about your income.

2. Where is your income sourced? For each income stream, identify where the work was performed, where the customer is located, and how the income would be classified (services, royalties, product sales). Different answers trigger different reporting obligations.

3. What VAT/GST obligations exist? If you sell digital products or services to consumers (B2C) in the EU, UK, or Australia, identify whether your sales exceed the registration thresholds. If they do, identify whether your platforms handle remittance or whether you are responsible.

4. Can your tax return reconcile with all platform reports? Add up all 1099-Ks and other platform reports. Compare to your reported gross revenue. If there is a gap, document why (refunds, fees, duplicate payments, currency conversion). The gap is what the IRS sees first.

The META framework maps this across all four dimensions — Money flow through platforms, Entity structure receiving payments, Tax obligations triggered by multi-country income, and Accountability through documentation and reconciliation. The free risk check tool identifies which of these dimensions contains the most structural exposure for your specific setup.

---

Check your structural risk profile →