An international operator usually runs on a handful of disconnected tools: one for accounts, one for cards, one for FX, one for reporting, and a spreadsheet holding it all together. The portal is SUPA's answer to that — a single workspace where a unit's activity lives in one place.

One perimeter, one view

The workspace is built around the unit. Accounts, FX, payouts, cards and card acceptance sit behind one interface, with around ten currencies supported. Because everything is tied to the unit rather than to separate providers, you see one picture instead of five partial ones. When a payment leaves, it does not disappear into another vendor's dashboard; the operation stays attributable to the principal, the agent and the policy version that produced it.

The day-to-day it enables

The value of one workspace shows up in ordinary tasks:

  • Checking what a project earned, in one place, in the currency it earned it.
  • Sending a payout on local rails without switching systems.
  • Applying policy limits to an agent without negotiating with it.
  • Producing signing-ready documents for a unit on request.

Each of those is unremarkable on its own. Together they remove the reconciliation tax that grows as an operator adds currencies, projects and people.

Checks that happen once

Behind the interface, every operation passes a single compliance function once — reliance confirmation, sanctions screening, agent mandate, client-profile fit and network anomaly signals. An operation above a limit becomes a human approval request rather than an outright rejection. That is the quiet advantage of a single perimeter: oversight is applied at one point instead of being repeated across vendors that cannot see each other.

The workspace is not a bank. Balances sit with licensed partners, and SUPA does not hold client money in its own name before it holds a banking licence. What the portal offers is structure around activity, not custody of it.

In short:

  • The portal is one workspace built around the unit.
  • Accounts, FX, payouts, cards and acceptance sit behind one interface.
  • Every operation stays attributable to principal, agent and policy version.
  • Checks run once, at a single point.

Explore the workspace: business.