BazPay–Zinzipay: Suspected Common Control in Offshore Gambling Payments — Information Wanted

Overview

Evidence gathered to date suggests BazPay (bazpay.com) and Zinzipay (zinzipay.com) are more than casually related. In test checkouts from gambling sites, sessions frequently touch app.zinzipay.com and then transition to bazpay.com or app.bazpay.com. Independent traffic intelligence also points to sustained cross-referral patterns between both ecosystems (source). We invite knowledgeable insiders to help determine whether the two gateways are operated by the same principals and used to process offshore gambling transactions.

Findings at a Glance

Parallel checkout apps and redirects

• Both brands surface nearly the same “processing/checkout” application endpoints: app.zinzipay.com and app.bazpay.com.

• Observed payment journeys show repeatable hand-offs between these domains—behavior typical of tightly connected or co-managed PayFac flows.

Interlinked traffic signals

• Third-party analytics indicate material referral dependence for zinzipay.com and app.zinzipay.com, consistent with a network that exchanges users with closely tied services.

• While exact percentages fluctuate, the structural pattern is stable over time.

Corporate trail (BazPay)

• BazPay’s website names NEWERA PAYMENT TECHNOLOGIES LTD (UK company number 14154791) and publishes policy pages (Privacy/PCI-DSS).

• Companies House records identify Oleh YUNAK (born 03/2000, Ukrainian) as director and person with significant control (≥75%).

Commercial stance

• A BazPay profile on LinkedIn claims cooperation with high-risk businesses, which aligns with gambling merchant acceptance and routing.

Why This Should Concern Compliance Teams

If BazPay and Zinzipay share beneficial ownership or operational control, a single PayFac stack could be distributing gambling card traffic across both labels. Given earlier allegations concerning Zinzipay (e.g., fake descriptors/MCC masking), any unity of control would amplify:

• Exposure to transaction-laundering typologies,

• Potential card-scheme violations around proper use of MCC 7995, and

• AML/CTF scrutiny for acquirers, issuers, and BIN sponsors.

Evidence Map — Signals vs. Compliance Impact

Questions for Insiders and Practitioners

Ownership & Operations

• Do BazPay and Zinzipay share beneficial owners, engineering resources, support staff, or decision-making lines?

• Are there white-label or services agreements binding the two?

Individuals & Entities

• Oleh YUNAK: background, prior roles, linked companies, and ties to gambling/PayFac programs.

Acquiring/BIN Sponsorship

• Which acquirers/PSPs/BIN sponsors stand behind these flows?

• Any chargeback or brand monitoring anomalies traced to either label?

Onboarding & KYC/KYB

• What standards govern the onboarding of casino merchants?

• How often are KYC/KYB records refreshed, and by whom?

MCC Handling

• Are deposits coded MCC 7995 end-to-end?

• Any instances of third-party descriptors or MCC substitution?

Routing & Redirect Design

• Do casino checkouts systematically swing between app.zinzipay.com and bazpay.com/app.bazpay.com?

• Please share timestamped URL chains and header traces.

PCI-DSS Status

• Is the cited PCI program valid and current?

• Provide AoC/ROC numbers, scope, and assessor if available.

Licensing & Jurisdictions

• Do the operating entities behind BazPay/Zinzipay hold any PI/EMI authorization or equivalent registrations relevant to acquiring or money transmission?

What to Submit (Artifacts Checklist)

• Full checkout chains (URLs, parameters, and timestamps)

• HTTP headers and payment payload fragments (redact PII/PANs)

• Merchant descriptors, MCC logs, dispute/chargeback letters

• Contracts, org charts, staff overlap evidence

• Screenshots of admin/onboarding consoles and PCI attestations

Where to Send Information

Scam-Or Project invites acquirer staff, PayFac/risk teams, casino affiliates, and affected users to share evidence via our whistleblower section.