Omnipay3 Yandexkassa Laravel Package

Product Decisions This Supports

• Expanding Payment Gateway Options: Enables support for Yandex.Kassa (Yandex Checkout) as a payment method, broadening regional coverage for Russian-speaking markets (e.g., Russia, CIS countries).
• Laravel 5.6+ Compatibility: Aligns with legacy Laravel projects still on L5.6+ (e.g., enterprise systems, older SaaS platforms) that cannot upgrade to newer Laravel versions due to dependency constraints.
• Omnipay Integration: Leverages the Omnipay ecosystem (a PHP payment abstraction library) to standardize payment flows, reducing custom gateway development effort.
• Roadmap for Localization: Supports future plans to add multi-currency, localized checkout flows, or compliance with Russian payment regulations (e.g., 152-FZ).
• Build vs. Buy: Avoids reinventing the wheel for Yandex.Kassa integration, saving 3–6 months of dev time while maintaining security/compliance.
• Use Cases:
  • E-commerce platforms targeting Russia/CIS.
  • Subscription services (SaaS) with Russian user bases.
  • Marketplaces or platforms requiring Yandex.Kassa’s fraud protection or installment plans.

When to Consider This Package

• Adopt if:

  • Your primary audience is in Russia/CIS and Yandex.Kassa is a required or preferred payment method (e.g., high trust, local tax compliance).
  • You’re using Laravel 5.6+ and cannot upgrade due to legacy dependencies (e.g., custom packages, plugins).
  • You need Omnipay’s abstraction to unify multiple payment gateways (e.g., Stripe + Yandex.Kassa) under a single codebase.
  • Your team lacks Yandex.Kassa API expertise and wants a battle-tested (though unstarred) solution.

• Look elsewhere if:

  • You’re on Laravel 8+ (use the official Omnipay Yandex.Kassa driver instead).
  • Your project requires active maintenance (this package is abandoned; fork or maintain it yourself).
  • You need advanced features (e.g., Yandex.Kassa’s 3D Secure 2.0, recurring payments, or custom checkout UI)—this may require extensions.
  • Your stack is not PHP/Laravel (e.g., Node.js, Python, or a headless CMS like Shopify).
  • Security/compliance risks are a concern (unmaintained packages may have unpatched vulnerabilities; audit the codebase).

How to Pitch It (Stakeholders)

For Executives/Business Leaders:

*"This package lets us add Yandex.Kassa—Russia’s dominant payment gateway—to our platform with minimal dev effort. For our Russian/CIS users, this means:

• Higher conversion rates: Yandex.Kassa is trusted like PayPal in the U.S., with built-in fraud tools.
• Regulatory compliance: Avoids fines or blocks from Russian payment processors.
• Cost savings: No need to build a custom integration (estimates: $50K–$100K in dev time). Downside: It’s a legacy Laravel package with no active updates, so we’d need to fork and maintain it or budget for a custom solution if we upgrade Laravel later."*

For Engineering/Tech Leads:

*"This is a lightweight Omnipay driver for Yandex.Kassa, compatible with Laravel 5.6+. Here’s the tradeoff: ✅ Pros:

• Omnipay integration: Reuses our existing payment logic (e.g., Omnipay\Common\CreditCard flows).
• Quick to implement: ~1–2 dev days to test and integrate (vs. weeks for a custom solution).
• Supports core flows: Authorizations, captures, refunds, and voids (check the Omnipay docs for gaps).

⚠️ Cons:

• Unmaintained: Last commit is [X date]; we’d need to fork and monitor for security updates.
• Laravel 5.6 lock-in: If we upgrade, we’ll need to migrate to the official Omnipay driver.
• Limited features: No guarantees on Yandex.Kassa’s newer APIs (e.g., installment plans, subscription management).

Recommendation: Use this for MVP or legacy projects, but budget for a custom solution if we need long-term support or advanced features."*

Action Items:

1. Audit the codebase for security risks (e.g., deprecated dependencies).
2. Test with Yandex.Kassa’s sandbox before production.
3. Document the fork/maintenance plan if adopted.