Laravel Fortnox Laravel Package

Product Decisions This Supports

• Fortnox integration roadmap: Supports prioritizing or scoping a Fortnox OAuth/API integration for Laravel-based products, especially where customers need accounting, invoicing, or token-refresh workflows.
• Build vs. buy: Gives the team a viable “use a maintained Socialite driver” option instead of building and owning Fortnox OAuth driver logic in-house.
• Platform support planning: The 0.2.0 release requires Laravel 12 or 13 and drops Laravel 11, so adoption should be tied to an explicit Laravel upgrade decision.
• Reliability investment: The Laravel 13 driver-resolution fix protects token refresh and downstream API calls, making this package more credible for production auth flows.
• Feature vs. dependency trade-off: The typed FortnoxSocialiteProvider::resolve() accessor reduces integration ambiguity, but the package remains a narrow third-party dependency that should be tracked for maintenance risk.

When to Consider This Package

• Consider it when the product is on Laravel 12 or 13 and needs a Socialite-based Fortnox OAuth driver.
• Consider it when the team wants faster delivery of Fortnox authentication and token refresh without maintaining custom Socialite plumbing.
• Consider it when the integration is specifically Fortnox and the team is comfortable relying on a small, focused package.
• Look elsewhere or defer adoption if the product still runs Laravel 11 or earlier, unless a platform upgrade is already planned.
• Look elsewhere if the requirement is a broader accounting integration layer, a full Fortnox SDK abstraction, non-Laravel/PHP support, or a vendor strategy that avoids small third-party packages.
• Treat the Laravel 11 support drop as a release-planning dependency, not just a package upgrade.

How to Pitch It (Stakeholders)

Executive summary: This package can accelerate a Fortnox integration by providing the OAuth/Socialite driver and token-refresh path instead of requiring custom auth work. The latest release fixes a Laravel 13-specific failure that previously broke driver resolution and every Fortnox API call, which materially improves production readiness. The trade-off is that 0.2.0 requires Laravel 12 or 13 and drops Laravel 11, so adoption should be sequenced with the platform upgrade and tracked as a focused third-party dependency.

Engineering summary: Use this package for Fortnox Socialite authentication on Laravel 12/13. The 0.2.0 fix addresses Laravel 13’s extend() rebinding behavior, and the new typed resolve() accessor improves driver access. Confirm the app is off Laravel 11 before adopting, and keep the package scoped to the auth/API-call path rather than treating it as a full Fortnox integration platform.