After Scam-Or Project identified CAPITOLIO INC. as the visible payee within a tested 1Go Casino Revolut/Yapily open-banking deposit route, the Canadian MSB issued a legal demand requesting removal of the report. However, the notice itself does not appear to dispute the central payment-rail observation. Instead, Capitolio effectively acknowledges that its entity may appear as the named payee in transactions routed through its open-banking on-ramp infrastructure.

Following publication, two notable developments occurred:

• Capitolio appears to have revised regulatory information displayed on its website;
• 1Go Casino appears to have removed the Revolut funding option from its cashier.

These developments further support the core Rail Atlas methodology: public scrutiny of payment infrastructure can trigger rapid operational adjustments.

Two-Minute Briefing

The Scam-Or Project Rail Atlas initiative was designed to map how offshore casino deposits travel through:

• payment gateways,
• open-banking providers,
• wallet infrastructure,
• crypto payment rails,
• regulated processors,
• and bank-facing authorisation layers.

The 1Go Casino / Capitolio case has become a particularly clear example of this methodology in action.

In the original review, a tested deposit flow from the 1Go Casino cashier passed through multiple intermediary routing layers before ultimately reaching a Revolut/Yapily open-banking authorisation screen displaying CAPITOLIO INC. as the visible payee.

Capitolio later sent a formal legal notice demanding complete removal of the article. The company alleged defamation and misleading reporting. However, the notice does not appear to directly challenge the screenshot-based evidence showing Capitolio as payee. Instead, Capitolio states that appearing as payee is part of the standard architecture of its open-banking on-ramp infrastructure.

That clarification is highly significant.

The core issue is no longer whether Capitolio appeared as payee — Capitolio’s own position appears to confirm that possibility. The real compliance question becomes:

When a user initiates a deposit from an offshore casino cashier, do banks, PISPs, MSBs, and transaction-monitoring systems still see the underlying gambling context if the bank-facing payee is a payment infrastructure entity rather than the casino brand itself?

If not, the structure may create what Scam-Or Project describes as payment-purpose dilution.

Key Findings

What Capitolio’s Notice Actually Confirms

Capitolio’s legal notice relies on arguments involving:

• Alberta defamation law,
• Austrian legal provisions,
• GDPR-related concerns,
• and EU platform rules.

However, from a payment-infrastructure perspective, the most important element of the notice is this:

Capitolio presents this as a standard technical arrangement. Scam-Or Project’s interpretation differs.

If an infrastructure provider consistently appears as the bank-facing payee in transactions originating from casino cashiers, then several compliance questions emerge:

• Does the bank still see the upstream merchant?
• Is the gambling context preserved?
• Is the payment classified correctly?
• Can monitoring systems detect casino-origin funds?
• Does the customer understand who ultimately receives the payment?

This is the core Rail Atlas concern.

Capitolio’s Position vs. Scam-Or Project’s Interpretation

Why the Capitolio Case Matters

The Capitolio response illustrates a recurring pattern in modern payment-rail investigations.

Infrastructure providers often do not deny the underlying architecture. Instead, they argue:

• the structure is standard,
• technically necessary,
• or common within open-banking environments.

However, “standard architecture” does not automatically eliminate systemic compliance risk.

If the consumer-facing merchant differs from the bank-facing payee, regulators and compliance teams must ask:

• Who is the actual merchant?
• Who onboarded the merchant?
• Who knows the payment originated from a casino?
• What information reaches the bank?
• What information reaches the PISP?
• How is the transaction categorised?
• Are gambling restrictions being bypassed indirectly?

The CSSF / RCS Issue and the Website Changes

One of the original findings concerned unusual regulatory information previously displayed on Capitolio’s website.

Earlier screenshots reportedly showed:

These identifiers correspond to Luxembourg-style regulatory references associated with Banking Circle S.A., whose official website lists:

• financial registration number LUB00000408,
• trade register number B222.310,
• CSSF registration number B00000408.

Scam-Or Project did not claim that Capitolio was connected to Banking Circle. The concern related to regulatory representation and website integrity.

Following publication, Capitolio appears to have revised the displayed information. Current pages reportedly show:

• FINTRAC registration number M24928320,
• Alberta Corporate Access Number 2025599024.

This represents a concrete compliance-reporting outcome: a publicly visible regulatory-information anomaly appears to have been corrected after exposure.

Updated 1Go Casino Cashier Review

A subsequent review of the 1Go Casino cashier suggests the Revolut funding route has disappeared.

The updated cashier still displayed:

• Crypto Currency,
• ByBit,
• Pay by Bank,
• additional account-to-account payment rails.

This suggests that the original Revolut/Yapily route may have been disabled or replaced following publication.

However, the broader infrastructure issue remains unresolved.

The updated review reportedly identified:

• Domus Payment Solutions as payee within another Pay by Bank route;
• routing through secure.bankgate.io;
• bank authentication pages referencing Bridge SaltEdge API.

Both Bridge and Salt Edge publicly market open-banking and payment-initiation services.

Updated 1Go Rail Map

Original Revolut / Yapily / Capitolio Route

Updated Pay by Bank / Bridge / SaltEdge Route

Rail Atlas Methodology: Why This Case Matters

The Capitolio case demonstrates why Scam-Or Project maps complete payment rails instead of merely listing payment options.

A casino cashier screenshot is only the starting point.

The real questions emerge later:

• Which gateway appears?
• Which intermediary domains are used?
• Which PISP becomes involved?
• Which bank-facing authorisation screen appears?
• Who is shown as payee?
• Does the gambling context remain visible?
• Do the rails change after public exposure?

That may be technically accurate.

But if the transaction originated from an offshore casino cashier, the compliance implications remain highly relevant.

Why This Matters for Payment Processors

Scam-Or Project’s reporting focuses on visibility and accountability across high-risk payment rails.

The objective is not opposition to open banking or financial innovation.

The concern is whether regulated or semi-regulated infrastructure is being used to facilitate offshore casinos operating in jurisdictions where they may lack local authorisation.

1Go Casino publicly references:

• Galaktika N.V. as operator,
• Curaçao licence OGL/2024/169/0146,
• Unionstar Limited as payment agent.

A Curaçao licence does not automatically permit unrestricted operation across EU jurisdictions.

That is where payment processors, PISPs, MSBs, and banks become relevant.

Regulatory Questions Raised

The Capitolio response and updated 1Go flows raise several unresolved questions:

1. If an open-banking provider appears as payee, how is the underlying merchant disclosed?
2. Who classifies the transaction as gambling-related?
3. Can banks detect casino-origin funds if the payee is an MSB or PSP?
4. Do PISPs receive upstream merchant-category information?
5. Must processors block casinos targeting unauthorised jurisdictions?
6. When one rail disappears after exposure, is the merchant terminated or simply rerouted?
7. Does replacing one rail with another represent remediation or rotation?
8. Should open-banking consent screens disclose the underlying merchant rather than only the technical payee?

These questions are no longer theoretical. They are visible in live payment flows.

Conclusion

Capitolio’s legal notice did not weaken the Rail Atlas methodology. It reinforced it.

The central finding remained unchanged:

A tested 1Go Casino Revolut/Yapily deposit flow displayed CAPITOLIO INC. as the visible payee.

Capitolio’s response did not clearly dispute that observation. Instead, it explained that such payee appearances are part of its infrastructure model.

That is precisely why the case matters.

If the casino brand disappears before the payment reaches the bank-facing layer, then payment-purpose dilution may occur.

The aftermath is equally revealing:

• Capitolio appears to have revised website regulatory information;
• the Revolut rail appears removed;
• other Pay by Bank routes remain active;
• Domus Payment Solutions still appeared as payee;
• Bridge/SaltEdge infrastructure now appears within updated flows.

The rail changes.

The payee changes.

The gateway changes.

The compliance question remains.

Scam-Or Project will continue mapping payment rails and examining how offshore casino deposits move through regulated financial infrastructure.

The essential question remains:

Do banks, processors, PISPs, and monitoring systems know when an ordinary-looking account-to-account payment actually originated from an offshore casino deposit?

Call for Information

If you have information regarding Capitolio or other payment facilitators linked to offshore casino infrastructure, you may submit documentation, screenshots, or payment records through the Scam-Or Project Complaints section. Relevant whistleblower materials may assist ongoing payment-rail investigations.