Payum Payzen Laravel Package

Product Decisions This Supports

• Expanding payment options: Integrate PayZen (Systempay, Scellius, etc.) as a new payment gateway to support European markets, particularly France, where PayZen is widely used.
• Roadmap alignment: Accelerate time-to-market for a new payment method without building a custom solution from scratch, leveraging Payum’s extensible architecture.
• Build vs. buy: Opt for a pre-built, MIT-licensed package to avoid reinventing payment gateway logic while maintaining flexibility for customization (e.g., adding ConvertPaymentAction).
• Use cases:
  • E-commerce platforms targeting France/Benelux.
  • Subscription-based services needing PCI-compliant payment processing.
  • Multi-currency support for international merchants.
  • Compliance with PSD2/SPS requirements via PayZen’s strong authentication.

When to Consider This Package

• Adopt if:

  • Your tech stack already uses Payum (PHP payment abstraction library) or you’re open to adopting it for consistency.
  • You need PayZen-specific integrations (e.g., Systempay, Scellius, CLIC&PAY) without vendor lock-in.
  • Your team prefers PHP/Laravel and wants to avoid JavaScript-heavy solutions (e.g., Stripe.js).
  • You require SHA-256 or SHA-1 hash support for legacy systems or compliance.
  • Budget and timeline favor open-source adoption over proprietary gateways (e.g., Adyen, Stripe).

• Look elsewhere if:

  • You’re not using Payum—integration effort may outweigh benefits (requires wrapping Payum in your stack).
  • You need active maintenance (last release: 2021; consider forking or supplementing with community support).
  • Your primary market uses non-PayZen gateways (e.g., iDEAL in Netherlands, Bancontact in Belgium).
  • You require advanced features (e.g., 3D Secure 2.0, real-time fraud tools) not covered by this package.
  • Your team lacks PHP/Laravel expertise for troubleshooting or customization.

How to Pitch It (Stakeholders)

For Executives: "This package lets us add PayZen (Systempay) as a payment method with minimal dev effort, tapping into France’s $50B+ e-commerce market. By leveraging Payum—a battle-tested payment abstraction layer—we avoid building a custom solution while keeping costs low (MIT license). It’s a quick win for expansion, with room to customize later. Risk is mitigated by PayZen’s strong authentication and PCI compliance."

For Engineering: *"PayumPayzen is a lightweight, Payum-compatible gateway for PayZen’s APIs. It handles:

• Configuration: Site ID, certificates, and endpoints (Systempay/Scellius) via a simple factory.
• Hashing: Supports SHA-256 (default) or SHA-1 for legacy systems.
• Extensibility: Plug into Payum’s workflow (e.g., add custom ConvertPaymentAction for order mapping). Tradeoff: Last updated in 2021, but the core logic is stable. We’d need to:

1. Adopt Payum if not already using it.
2. Test edge cases (e.g., refunds, voids) against PayZen’s API.
3. Monitor for updates or fork if needed. Proposal: Pilot with a single market (e.g., France) before scaling."*