- Is fp/klarna-invoice an official Laravel package?
- No. It is an unofficial Composer wrapper around Klarna's legacy Invoice service, intended for use with Payum/KlarnaInvoice. It does not provide a Laravel service provider, facade, publishable config, or framework-native integration.
- How do I install fp/klarna-invoice with Composer in a Laravel app?
- Install it via Composer in a disposable branch and expect to relax PHP, Laravel, Payum, and Guzzle constraints. The package has not released since 2015, so modern compatibility is uncertain. Prefer a private fork or pinned commit if you must maintain an existing flow.
- Does fp/klarna-invoice support Laravel 9, 10, or 11 and PHP 8?
- There is no documented support for modern Laravel or PHP 8+. Compatibility must be validated with a spike covering autoloading, namespaces, HTTP client versions, Payum versions, TLS, and sandbox transactions. Expect friction and plan for constraint relaxation or patching.
- What Klarna API version does fp/klarna-invoice target?
- The repository is a legacy Klarna Invoice wrapper, but the exact API version and contract are not established by the package metadata. Confirm the targeted endpoints, request and response formats, and deprecation status against Klarna's current documentation before relying on it. Do not assume capture, refund, tax, or order-line behavior from the package alone.
- Can I use fp/klarna-invoice with Payum/KlarnaInvoice?
- Yes, that is the stated intended use: it is an unofficial Composer wrapper used with Payum/KlarnaInvoice. This adds another legacy dependency and version-compatibility risk. Keep Payum classes behind an application-owned adapter rather than exposing them to controllers or domain services.
- Does fp/klarna-invoice support capture, refund, partial refund, cancel, and credit?
- The package is a wrapper, so support depends on the underlying Klarna Invoice API and Payum bridge behavior. You must verify capture, refund, partial refund, cancel, credit, invoice status, tax and order-line handling, and idempotency against Klarna's current contract. Add contract tests for success, failure, timeout, duplicate submit, and reconciliation scenarios.
- Is fp/klarna-invoice maintained or abandoned?
- It is effectively abandoned for new development: last release 2015-09-03, 4 stars, 0 dependents, and a low ecosystem score of 0.31. There are no meaningful tests or support guarantees described. Treat maintenance as low-to-negative and budget for a private fork.
- What are the best alternatives to fp/klarna-invoice for Laravel?
- For new work, evaluate Klarna Payments, Klarna Checkout, or an official Klarna SDK instead of this legacy Invoice wrapper. If you need a Laravel-native integration, prefer a maintained package or build an application-owned adapter around current Klarna APIs. Use fp/klarna-invoice only to maintain an existing Invoice flow.
- How should I handle Klarna callbacks, webhooks, and payment status reconciliation with this package?
- Do not assume webhook support from the package; verify whether callbacks are available or whether status reconciliation is polling-only. Implement idempotency, logging, error mapping, and reconciliation in your own application layer. Keep credentials in Laravel config or secrets rather than package globals.
- Can I use fp/klarna-invoice in production for a new Laravel application?
- It is not recommended for greenfield Laravel work due to abandoned maintenance, legacy Klarna Invoice deprecation risk, unclear licensing for an unofficial fork, and absent tests or support. If unavoidable for legacy support, fork or vendor it, pin a commit, add compatibility and sandbox contract tests, feature-flag rollout, and plan migration to Klarna Payments, Klarna Checkout, or an official SDK.