Fortris must show where gaming deposits end and its own treasury begins because prior source-attributed reporting alleged that it processed flows for offshore betting operators serving unauthorized U.S. markets. The allegation remains unadjudicated, but it makes ownership of every balance material: player deposits, merchant settlement funds, affiliate payouts, prefunded liquidity and Fortris’s corporate assets cannot be treated as one undifferentiated pool.
Fortris markets treasury management, digital-asset custody workflows and gaming deposits and payouts. Those functions can place different parties’ economic interests inside adjacent wallets and accounts. The accountability test is whether legal ownership, operational control, accounting treatment and emergency transfer authority remain clear before an incident forces the distinction into public view.
Triple-A’s statement sets a segregation benchmark
Triple-A said in its July 27, 2026 incident statement that it identified unauthorized access on July 25 to certain wallets holding company-owned digital assets. It said the incident was contained, normal service restored, client funds held separately in trust accounts with safeguarding institutions, and that it remained able to meet all liabilities.
Those are company statements, not an audit or regulator finding. Triple-A did not disclose the access method or a loss amount in the statement. Its account nevertheless illustrates the questions a payment provider must answer when it says corporate assets were exposed but client money was not: what counted as client funds, who held them, under what legal arrangement and how were the balances reconciled?
Fortris should provide a balance-by-balance map. Each line should name the contracting entity, legal owner, beneficial claimant, asset, chain, wallet or account type, custodian or safeguarding institution, key controller, ledger treatment and settlement status. A merchant balance awaiting payout is not necessarily the same as a player deposit in transit, corporate working capital or prefunded liquidity supplied by a partner.
Technical separation is only one layer
Different wallet addresses can improve operational clarity without proving legal segregation. The contractual terms must state whether assets are held for a customer, owed as a debt, controlled by a custodian or owned by Fortris after conversion. The accounting records should match that legal characterization, and daily reconciliation should connect on-chain balances with internal ledgers and external bank or custodian statements.
Control of private keys creates another layer. Fortris should disclose whether signing authority sits with the company, a custodian, a customer or a shared arrangement; how maker-checker or multisignature rules work; and who can move assets during an emergency. An emergency transfer right intended to protect funds can also defeat segregation if it permits customer balances to cover corporate obligations.
Creditor treatment belongs in the same map. Counterparties need to know what would happen if Fortris or a service partner entered insolvency, whether trust or safeguarding arrangements are legally recognized in the relevant jurisdiction and whether setoff or security interests could affect the balance. Marketing labels such as “dedicated” or “regional” wallet do not answer those questions.
For gaming flows, the map should extend through the operator, brand and payout beneficiary. A player deposit may pass through cashier infrastructure, conversion and merchant treasury before an affiliate or player receives value. Fortris should be able to identify when title changes, who bears loss at each stage and whether a disputed or restricted operator can still direct funds.
How counterparties could verify the map
Independent assurance should test a sample of balances through every layer: customer contract, internal subledger, blockchain address or bank account, custodian statement, reconciliation and final settlement. The reviewer should test both normal activity and exceptions, including failed conversions, disputed payouts and emergency transfers. A clean total at month-end can conceal intraday commingling or temporary use of restricted balances.
Fortris should also define how fees enter the structure. Processing charges, spreads, network costs and reserves may be deducted at different points. The ledger needs to show when a fee becomes Fortris property and whether a customer can still claim the gross amount. Ambiguous fee timing can make a supposedly segregated balance difficult to reconstruct after a failure.
Client reporting should be specific enough to reconcile. Merchants should receive opening balance, deposits, conversions, fees, payouts, adjustments and closing balance by asset and account, with identifiers that connect to transaction records. Exceptions should be explained rather than carried as unexplained suspense items. This evidence would let counterparties verify the boundary continuously instead of waiting for an incident statement.
The earlier offshore-betting allegation raises precisely this need for traceability. Fortris can demonstrate control without exposing customer identities by publishing the architecture, reconciliation standard, legal categories and assurance scope. What matters is proof that merchant, player, affiliate and corporate money remain distinguishable in records and law—not only on a dashboard—when a wallet is compromised or a provider fails.