Connect Laravel Package

Product Decisions This Supports

• Migration from deprecated Square Connect SDK to modern Square PHP SDK: This package is deprecated and replaced by square/square. A PM should prioritize migrating legacy systems using this SDK to avoid security risks, lack of updates, and compatibility issues.
• Payment processing & refunds: The package supports core Square APIs (e.g., payments, refunds, OAuth), enabling PMs to build or enhance:
  • Marketplace/aggregator platforms (e.g., multi-vendor checkout flows).
  • Subscription services (recurring payments + refunds).
  • POS integrations (in-store/online hybrid systems).
• Build vs. Buy: Buy for payment infrastructure (unless custom fraud detection or compliance logic is required). The modern square/square SDK is actively maintained, reducing technical debt.
• Roadmap alignment: If your product relies on Square’s ecosystem (e.g., Square Terminal, Loyalty API), this migration ensures future compatibility with Square’s roadmap.

When to Consider This Package

• Never use this package directly—it is archived and unsupported (EOL since 2020). Instead:
  • Use square/square for new projects or migrations.
  • Evaluate alternatives if:
    • Your team lacks PHP/Laravel expertise (consider Square’s Node.js or Python SDKs).
    • You need multi-currency support (Square’s SDK handles this natively).
    • Your compliance requirements demand audit logs (Square provides built-in tracking).
  • Look elsewhere if:
    • You need real-time fraud tools (integrate with Stripe Radar or Signifyd).
    • Your stack is non-PHP (e.g., Ruby, JavaScript).

How to Pitch It (Stakeholders)

For Executives:

*"Square’s modern PHP SDK (square/square) replaces this deprecated package, offering:

• Security: Actively maintained with bug fixes and compliance updates.
• Scalability: Supports high-volume transactions (ideal for marketplaces or SaaS platforms).
• Cost Efficiency: No per-transaction fees beyond Square’s standard rates.
• Risk Reduction: Avoids technical debt from unsupported libraries. Recommendation: Migrate legacy systems using this package to the new SDK to align with Square’s roadmap and reduce operational risk."*

For Engineering:

*"Key advantages of migrating to square/square:

1. Simplified API: Method chaining (e.g., $api_client->getPaymentsApi()->createPayment()) reduces boilerplate.
2. Modern OAuth: Built-in token renewal/revocation (no custom logic needed).
3. Refunds & Payments: Unified API for both (e.g., CreatePaymentRequest objects).
4. Error Handling: Structured responses ($response->isError()) improve debugging. Action Items:

• Audit all square/connect usages in the codebase.
• Update composer.json to require square/square:^5.0.
• Replace SquareConnect\* imports with Square\* and update client initialization. Timeline: 2–4 weeks for full migration (prioritize high-traffic payment flows first)."*