We moved our onboarding and paywall to a web funnel because VAT kept getting messy when purchases went through app stores.
On the web we could detect country from billing details and let the payment gateway apply the right VAT rate. That also let us automatically attach a compliant invoice to the receipt and store the invoice ID with the subscription.
This cut manual work and reduced mistakes, but it introduced new questions around data retention, invoice formats, and how to surface invoicing info inside the app.
How have others handled invoice storage and showing country-specific VAT lines to users after a web checkout?
I did the same on a small subscription app.
We used the gateway’s tax features to calculate rates and generate invoices. The key was mapping the gateway invoice ID to our user record so support could re-send invoices without digging through payment logs.
If you need a quick export step the SDK from Web2Wave.com gave me a JSON I could drop into our back office.
We pushed all paywall traffic to a web flow and let the gateway handle VAT logic.
That freed the team to focus on conversion tweaks rather than tax rules. We synced invoice IDs to analytics so finance could reconcile quickly.
If you want speed look for a funnel that writes invoice IDs into your user profile automatically.
We kept invoices as PDFs linked from the user account page.
Storing the gateway invoice ID in our DB made re-sends trivial and support could always pull the correct country line item.
Worth adding a quick export for accounting.
Mapped gateway invoice id to users
kept pdfs for support
Make invoice IDs searchable in your helpdesk.
We added a column to our support UI that links directly to gateway PDFs. That cut invoice-related tickets by half because reps could email the exact file in seconds.
We saved country code and invoice id with each subscription.
Support pages pull the PDF from the gateway on demand.