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 freelance on Upwork for companies in Singapore and Australia. Your Amazon KDP royalties come from seven different marketplaces.

Where is that income "from"?

It depends on which tax authority is asking. When you earn through multiple platforms in multiple countries, several tax authorities ask simultaneously and often reach different conclusions about the same dollar.

Income sourcing is not where you get paid

Most founders assume the money is "from" wherever the payment lands. Wrong. A payment hitting your Stripe account in USD does not make it US-sourced income. A German client paying you for work you did in Portugal? That income is German-sourced, Portuguese-sourced, or both, depending on the framework.

The rules differ by country and income type:

• Services income: Sourced where the work is performed. A developer in Portugal writing code for a US client earns Portuguese-source income under most frameworks, regardless of where the client or payment processor sits.
• Royalties: Sourced where the intellectual property is used. Amazon KDP royalties from the UK marketplace are UK-sourced.
• Sales of goods: Sourced where title passes or where the buyer is located, depending on jurisdiction.
• Digital products/SaaS: The messy one. The EU treats digital services as sourced where the customer is located. The US treats them as sourced where the work is performed. Same transaction, two different answers.

The invoice trail analysis shows how the same payment gets classified differently at each step by the platform, the payer's country, and the founder's country.

The 1099-K reporting problem

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:

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

Here is the part that trips people up: the 1099-K reports gross payments, not net income. Refunds, Stripe fees, cost of goods, expenses? Not subtracted. Process $50,000 through Stripe but $10,000 was refunds and $2,000 was fees? The 1099-K still says $50,000. You reconcile on your tax return. If those numbers do not line up cleanly, the IRS sees a gap.

Multiple platforms, multiple 1099-Ks

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

Your tax return has to reconcile all of them. 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 explaining the gap. Without it, the IRS sees unreported income.

The payment processor comparison covers which processors issue 1099-Ks and which handle tax remittance for you. That distinction matters because platforms like Paddle act as the Merchant of Record. 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

Sell to customers in the EU, UK, or Australia? Those sales may trigger VAT or GST obligations regardless of where you are located. Most founders selling digital products globally have no idea this is the case.

EU VAT on digital services

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

• EU threshold: Total EU B2C digital sales above EUR 10,000/year means you charge VAT at the customer's local rate (17% in Luxembourg up to 27% in Hungary)
• Below threshold: You can charge your home country's VAT rate (or zero if outside the EU)
• OSS registration: File a single VAT return covering all EU member states

Sell a $50 digital product to someone in Germany? You owe 19% VAT on that sale, $9.50 to the German tax authority. France? 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. The Stripe vs Paddle vs Lemon Squeezy comparison breaks down 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 the obligation. Rate: 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 real problem

If you process sales through Stripe to customers in 30+ countries, you potentially owe VAT or GST in dozens of jurisdictions. Most founders either use a Merchant of Record platform (which handles all of this) or have no idea the obligations exist.

The gap between "I sell digital products globally" and "I have VAT registration obligations in 27 EU member states" is where the exposure lives. This is why the platform risk analysis treats payment processor choice as a structural decision, not a fee comparison.

Platform withholding vs. self-reporting

Not all platforms handle tax the same way, and the differences matter more than most founders realize.

Withholding platforms: 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 withholds 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 backup withholding). 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, handle VAT/GST, and pay you a net amount. Your reporting is simpler since you report the net payout as revenue, but the gross-to-net reconciliation happens on their side.

The question worth asking: do you know which of your platforms reports what, to which tax authority, with what classification? If not, the documentation gap between what platforms report and what you report is where misalignment starts.

When platforms report to multiple countries

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

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

Amazon reports marketplace sales data to EU tax authorities under DAC7, a directive requiring digital platforms to report seller information and transaction data to EU member states.

If you operate across platforms in multiple countries, information about your income arrives at different tax authorities at different times, in different formats, with different classifications. Your tax return has to be consistent with all of them simultaneously. The narrative consistency analysis covers 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.

Where was the work performed? That is the question that matters for income sourcing, not where the client sits. If the developer did all the work from Portugal:

• The income is Portuguese-source under most analyses
• US clients may still issue 1099s or generate 1099-K reporting (because the payment processor is US-based)
• Portugal may tax it as Portuguese-source self-employment income
• The US may or may not have a claim depending on the developer's 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, sourcing determines whether the US has any taxing right at all.

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 work done in the US or in Thailand. That attribution is yours to perform, and it means tracking where work was actually done for each payment received. The cross-border compliance checklist covers the full set of reporting obligations that flow from this.

Practical mapping for platform founders

Exposure compounds with each additional platform and jurisdiction. Four questions to start with:

1. Which platforms report to which tax authorities? List every platform that processes your payments. For each one: does it issue a 1099-K? Withhold tax? Report to a non-US tax authority? This tells you what information tax authorities already have about your income.

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

3. What VAT/GST obligations exist? If you sell digital products B2C in the EU, UK, or Australia, check whether your sales exceed registration thresholds. If they do, check whether your platforms handle remittance or whether you are on the hook.

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 looks at first.

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

Key Takeaways

• Income sourcing is where the work is performed, not where payment lands. A developer in Portugal coding for a US client earns Portuguese-source income regardless of Stripe payout currency.
• The 2026 1099-K threshold is $5,000 in gross payments. That number includes refunds and fees. The gap between 1099-K totals and reported revenue is what the IRS looks at first.
• Selling digital products to EU consumers through Stripe triggers VAT obligations in up to 27 member states once B2C sales exceed EUR 10,000. Paddle and Lemon Squeezy handle remittance; Stripe does not.
• UK digital services VAT (20%) has no registration threshold for non-established sellers. Any B2C digital sale to a UK customer triggers it.
• Merchant of Record platforms (Paddle, Lemon Squeezy) collect and remit taxes for you. Stripe, PayPal, and Wise report but do not remit.

References

• IRS: Tax Information for International Businesses — Income sourcing rules and reporting requirements for cross-border business activity
• IRS: Understanding Your Form 1099-K — Platform reporting thresholds and reconciliation with tax returns
• OECD: Model Tax Convention — Framework for income classification and sourcing across treaty jurisdictions

---

Check your structural risk profile →