Liontech Laravel Laravel Package

Product Decisions This Supports

• Payment Integration Roadmap: Accelerates adoption of FusionPayments (formerly LionTech) as a primary or secondary payment gateway for e-commerce, SaaS, or subscription-based platforms. Enables seamless PCI-compliant card processing, refunds, and payouts without building custom SDK integrations.
• Build vs. Buy: Buy—avoids reinventing the wheel for a niche but critical feature (payment processing). The package abstracts away low-level API calls, token management, and security (e.g., webhook verification, RSA encryption), reducing technical debt.
• Multi-Tenant SaaS: Supports tenant-isolated payment processing via direct client instantiation (bypassing the singleton container). Critical for platforms like marketplaces or white-label solutions where each tenant may have distinct merchant accounts.
• Compliance & Security: Addresses PCI DSS requirements by handling card encryption (RSA) and webhook signature verification out-of-the-box. Reduces audit risk by leveraging a maintained, type-safe SDK.
• Developer Experience: Enables rapid iteration for payment flows (e.g., subscriptions, one-time purchases) with Laravel’s dependency injection and facades. Example use cases:
  • Checkout: Create orders/payments with LionTech::orders()->create().
  • Webhooks: Validate and route events (e.g., payment.succeeded) via WebhookSignatureVerifier.
  • Refunds/Payouts: Integrate with existing financial workflows (e.g., LionTech::refunds()->create()).
• Sandbox Testing: Simplifies pre-production validation with environment-based sandbox mode, reducing friction for QA/testing teams.
• Cost Optimization: Lowers development costs by eliminating custom API client maintenance (e.g., retries, rate limiting, OAuth token refresh).

When to Consider This Package

• Adopt if:

  • Your product requires PCI-compliant payment processing and FusionPayments is a strategic partner/gateway.
  • You’re using Laravel 11–13 and need a maintained, type-safe integration (vs. raw API calls).
  • You prioritize multi-tenancy or multi-merchant support (e.g., marketplaces, platforms).
  • Your team lacks bandwidth to build/maintain a custom payment SDK or prefer off-the-shelf solutions.
  • You need webhook security (signature verification) and card encryption without manual RSA key management.
  • Your roadmap includes subscriptions, refunds, or payouts—the package covers these use cases natively.

• Look elsewhere if:

  • You’re locked into another payment gateway (e.g., Stripe, PayPal) with existing Laravel packages (e.g., laravel-stripe).
  • Your stack uses PHP <8.3 or Laravel <11 (package has strict version requirements).
  • You need official support from FusionPayments (this is an unofficial community package).
  • Your use case requires advanced customization (e.g., modifying SDK behavior) that the facade/container pattern restricts.
  • You’re in a highly regulated industry (e.g., fintech) where vendor lock-in or unofficial packages introduce unacceptable risk—validate FusionPayments’ compliance separately.
  • You prefer serverless/headless architectures (package is Laravel-specific; consider the underlying nokimaro/liontech-php-sdk for non-Laravel projects).

How to Pitch It (Stakeholders)

For Executives (Business/Strategy)

"This Laravel package lets us integrate FusionPayments—our chosen payment gateway—without building a custom SDK from scratch. It handles PCI-compliant card encryption, webhook security, and multi-merchant support out of the box, reducing development time by 60–80% while lowering audit risk. For platforms like [Product Name], this enables faster time-to-market for subscriptions, refunds, and payouts, and supports our multi-tenant roadmap. The package is MIT-licensed, actively maintained, and aligns with our tech stack (Laravel 13, PHP 8.3+)."

Key Outcomes:

• Faster launches: Ship payment flows in weeks, not months.
• Lower costs: No ongoing maintenance for a custom integration.
• Scalability: Built for high-volume transactions with built-in retries/rate limiting.
• Compliance: Reduces PCI scope by offloading encryption/tokenization to the SDK.

For Engineering (Technical)

*"This package wraps FusionPayments’ PHP SDK with Laravel-native features: auto-discovery, facades, dependency injection, and config helpers. It’s type-safe, well-tested (100% coverage), and handles edge cases like:

• Token refresh: Automatic OAuth handling via the underlying SDK.
• Webhook security: Built-in signature verification with WebhookSignatureVerifier.
• Card encryption: RSA encryption via CardEncryptor (PCI-compliant).
• Multi-tenancy: Support for per-tenant credentials via direct client instantiation.

Why use it?

• Zero setup: Auto-registers with Laravel’s service provider.
• Consistent API: Facade (LionTech::orders()->create()) or DI (PaymentsClient $payments).
• Future-proof: Backed by the upstream nokimaro/liontech-php-sdk (v1.1.3+).
• Debugging: Clear error handling and config validation.

Trade-offs:

• Unofficial (but actively maintained by the community).
• Laravel-only (use the SDK directly for non-Laravel projects).

Recommendation: Adopt for core payment flows; pair with feature flags for gradual rollout."*

Critical for:

• Payment controllers (e.g., CheckoutController, SubscriptionController).
• Webhook endpoints (e.g., /fusionpayments/webhook).
• Multi-tenant architectures (e.g., TenantService::getClient()).