Liontech Php Sdk Laravel Package

Product Decisions This Supports

• Payment Gateway Integration: Accelerates development of a LionTech/FusionPayments payment solution by providing a type-safe, domain-oriented PHP SDK (vs. raw API calls or manual JSON handling).
• Roadmap Prioritization:
  • Build vs. Buy: Avoids reinventing the wheel for payment workflows (orders, refunds, webhooks, etc.) while maintaining flexibility for custom logic.
  • Laravel-Specific Needs: Justifies the nokimaro/liontech-laravel wrapper for seamless integration with Laravel’s ecosystem (facades, config, service providers).
• Use Cases:
  • E-commerce Platforms: Streamline checkout flows with 3DS support, encrypted card data, and webhook-driven order fulfillment.
  • Subscription Billing: Leverage payouts/transfers and tokenized payment methods for recurring revenue models.
  • Marketplaces: Handle multi-merchant payouts and dispute management via refunds/balances.
  • PCI Compliance: Offload card encryption and webhook signature verification to the SDK, reducing scope for custom security logic.
• Tech Stack Alignment:
  • PHP 8.3+: Enables modern features (enums, readonly classes) for maintainable, scalable code.
  • PSR Standards: Ensures compatibility with Laravel’s HTTP clients (Guzzle) and DI containers.
• Risk Mitigation:
  • Token Refresh: Automates OAuth2 token management, reducing downtime from expired credentials.
  • Error Handling: Typed exceptions (e.g., TokenExpiredException) simplify retry logic and observability.

When to Consider This Package

• Adopt When:

  • Your product requires FusionPayments/LionTech integration and PHP is the primary backend language.
  • You need type safety and domain-specific abstractions (e.g., Money, Currency, PaymentData) to reduce bugs in payment logic.
  • Your team prioritizes maintainability over raw API flexibility (e.g., prefer liontech->payments()->create() over manual curl/Guzzle calls).
  • You’re building a Laravel application and want native integration (facades, config, service providers).
  • Security/compliance is critical (e.g., PCI DSS), and you want to delegate card encryption and webhook verification to a vetted library.
  • You need webhook-driven workflows (e.g., async order fulfillment) with built-in signature validation.

• Look Elsewhere When:

  • You’re using Node.js/Python/Java, where official or more mature SDKs may exist.
  • Your team prefers low-level control over payment requests (e.g., custom serialization, non-PSR HTTP clients).
  • You’re integrating with multiple payment gateways and need a unified abstraction layer (consider a custom service or a multi-gateway SDK like Omnipay).
  • The low GitHub stars (0) or community maintenance raise concerns about long-term support (mitigate by evaluating the maintainer’s responsiveness or forking).
  • You require advanced features not covered (e.g., custom reporting, multi-currency conversions) that would need extension.
  • Your PHP version is <8.3, as the SDK leverages modern PHP features.

How to Pitch It (Stakeholders)

For Executives:

*"This SDK lets us integrate FusionPayments into our PHP/Laravel stack faster and more securely than building from scratch. It handles:

• PCI-compliant card encryption (no custom crypto logic).
• Webhook verification to prevent fraudulent payment callbacks.
• Type-safe payment flows (e.g., orders, refunds, payouts) to reduce bugs in checkout.
• Automatic token refresh to avoid downtime from expired API keys.

By adopting this, we avoid reinventing payment infrastructure while maintaining flexibility for custom business logic. The Laravel wrapper further reduces integration effort by 30%+."*

For Engineering:

*"This is a batteries-included PHP SDK for FusionPayments that:

• Saves dev time: Domain-specific classes (Money, PaymentData) and methods (createOrder(), verifyWebhook()) replace manual API calls.
• Improves reliability: Built-in retry logic for rate limits, token refresh, and typed exceptions for error handling.
• Enforces security: Webhook signatures and card encryption are handled by the SDK, reducing our PCI scope.
• Works with Laravel: The nokimaro/liontech-laravel package adds facades, config, and service providers for seamless adoption.

Tradeoffs:

• Tight coupling to FusionPayments (but we’re all-in on this gateway).
• PHP 8.3+ required (aligns with our roadmap).

Next steps:

1. Evaluate the Laravel wrapper for our stack.
2. Test webhook handling and card encryption in staging.
3. Compare performance vs. raw Guzzle calls (likely negligible overhead)."*