One payment, many GST questions: Why payment businesses need a transaction map
GSTIn this article, we explore why payment businesses need transaction mapping to identify GST risks and compliance gaps.
By: Jeremy O’Neill
24 Aug 2026 5 min read

A platform starts by serving Singapore customers, then expands regionally, then finds itself processing transactions for users, merchants and counterparties across multiple jurisdictions, often through the same Singapore entity, the same servers, and largely the same team that built the original product. The business model has gone cross-border. The documentation supporting it, in many cases, has not caught up.
Cross-border payment and digital token models are attracting more regulatory attention than they were even a year ago. MAS’s Digital Token Service Provider regime and the expanded perimeter of the Payment Services Act have both sharpened the question of what counts as a Singapore-regulated activity, even where the customer base sits offshore. We are seeing a similar sharpening on the tax side. Where a business belongs, where its customers belong and where the substantive work of the transaction actually happens are no longer questions that can be answered by a company’s marketing description of itself.
This matters because GST treatment for cross-border services depends heavily on customer location and belonging status which are concepts that sound straightforward until a business tries to prove them at scale, across app-based, platform-based and wallet-based models that were not necessarily designed with tax evidence in mind.
A few patterns come up repeatedly when we work with payment and fintech businesses on their cross-border positions.
The first is a mismatch between contracting entity and operating reality. A business may contract with customers through an offshore entity for commercial or regulatory reasons, while the people, systems and decision-making that actually deliver the service sit in Singapore. Regulators and tax authorities alike are increasingly looking past the contracting structure to ask where the service is genuinely performed.
The second is customer location evidence that has not kept pace with the product. Many platforms were built to capture the data needed for onboarding, fraud checks and compliance but not necessarily the data needed to evidence customer belonging status for GST purposes. IP addresses, billing addresses, registered business addresses and payment instrument origin do not always point the same way, and businesses are often surprised at how thin their evidence trail becomes once someone asks for it directly.
The third is scale outpacing governance. A cross-border assumption that was reasonable when a business had a handful of overseas customers becomes much riskier once that activity represents a meaningful share of revenue. We regularly help clients revisit positions that were set early and never formally revisited, even as the underlying business changed substantially around them.
None of this points to a single correct answer. Cross-border GST positions are genuinely fact-specific and the right treatment depends on the particular contracting model, customer base and operating footprint involved. But there are areas worth reviewing before a regulator or auditor asks first.
It is worth revisiting how customer location and belonging status are actually evidenced today, rather than how the original product design assumed they would be. It is worth checking whether the contracting entity named in customer agreements matches where the operational substance of the business sits. And it is worth asking whether cross-border assumptions made early in a company’s life have been formally reassessed as transaction volumes, geographies or customer types have grown.
Businesses that treat this as a live, evolving question, rather than something settled once at product launch, tend to find the conversation much easier when it eventually comes up with a regulator, auditor or acquirer.
Control question to ask internally: If challenged, could you evidence customer belonging status, contracting entity rationale and Singapore operating involvement from existing onboarding, KYC, transaction and finance records, without having to rebuild the trail manually?
This is exactly the kind of area where a practical outside perspective helps. Our clients are increasingly asking us to walk through their cross-border payment flows end-to-end mapping where customers actually sit, where contracts are signed and where the substantive work of the transaction happens, before assumptions harden into positions that are difficult to unwind later.
We help payment businesses review cross-border GST assumptions by mapping transaction flows, customer evidence, contracting arrangements and operating substance. Where the issue extends beyond tax treatment, our Business Risk Solutions team can support MAS compliance readiness, regulatory perimeter reviews and control testing over onboarding, KYC evidence and reporting processes thereby helping clients build a documentation trail that holds up under scrutiny, not just at product launch.
If your cross-border payment model has grown faster than the evidence supporting it, it may be worth a conversation before that gap becomes someone else’s question to ask.
In this article, we explore why payment businesses need transaction mapping to identify GST risks and compliance gaps.
As indirect tax compliance shifts from periodic reporting to transaction‑level transparency, many businesses are unsure what this change means in practice. In this article, we explore how InvoiceNow signals the future of GST compliance and its impact on companies and tax administrations.
As InvoiceNow moves toward mandatory adoption, businesses face growing pressure to get systems and data right. In this article, we explore compliance timelines and a practical roadmap for preparation.