Our analysis indicates a tight operational link between the high-risk payment gateways BazPay (bazpay.com) and Zinzipay (zinzipay.com). User journeys from casino checkout flows hit app.zinzipay.com and, in cases we observed, hand off to bazpay.com/app.bazpay.com. Traffic intelligence also shows strong cross-referrals between the two domains. We seek insider information on whether both gateways are controlled by the same principals and used for offshore gambling processing.
What We Found
- Checkout pairing & redirects. Both brands expose nearly identical “Checkout / processing your transaction” app endpoints (app.zinzipay.com and app.bazpay.com), consistent with shared or tightly integrated payment flows.
- Cross-domain signals. Similarweb indicates heavy referral dependence for zinzipay.com and for app.zinzipay.com, consistent with a hub that feeds/receives traffic from closely connected services. (Exact shares vary over time.)
- Corporate footprint (BazPay). The BazPay site lists NEWERA PAYMENT TECHNOLOGIES LTD (UK, 14154791) and provides policies (Privacy/PCI-DSS pages). Companies House shows Oleh YUNAK (b. 03/2000, Ukrainian) as director and person of significant control (≥75%).
- Market positioning. A BazPay LinkedIn profile states cooperation with high-risk companies—aligned with gambling merchant processing.
Why It Matters
If BazPay and Zinzipay are under common control, a single PayFac stack may be routing gambling card payments across brands. Given prior allegations around Zinzipay (fake descriptors/MCC masking), any shared control heightens transaction-laundering risk and potential card-scheme violations (MCC 7995 requirements). This has implications for acquirers, issuers, and AML oversight.
Questions for Insiders & Industry
- Control/Ownership: Do BazPay and Zinzipay share infrastructure, staff, or beneficial owners?
- Oleh Yunak: Background, prior roles, other companies, and connections to gambling/PayFac operations.
- Acquiring/BIN sponsors: Which banks/PSPs underwrite these flows?
- Merchant onboarding/KYC: How are casino merchants vetted?
- MCC usage: Are gambling deposits consistently coded 7995, or routed via third-party descriptors?
- Traffic hand-offs: Do merchant checkout URLs systematically redirect app.zinzipay.com ↔ bazpay.com? Provide examples.
- PCI-DSS & compliance: Is the listed PCI program genuine and current? Provide AoC/ROC details.
- Jurisdictions & licenses: Any PI/EMI authorizations or registrations for BazPay/Zinzipay entities?
How to Share
FinTelegram invites acquiring-bank staff, PayFac operators, risk teams, casino affiliates, and players to submit artifacts: checkout URLs, redirects/headers, merchant descriptors, MCC logs, contracts, org charts, or screenshots. Information can be shared via our whistleblower hub, Whistle42.com.
This RFI follows our Zinzipay inquiry and focuses on the apparent BazPay–Zinzipay linkage. If you have information connecting the two gateways—or clarifying that they are independent—please contact us.
