- Can I install lemonway/sdk-bundle in a Laravel application?
- No, not in any supported way. lemonway/sdk-bundle is a Symfony bundle built around a Bundle subclass, a DependencyInjection extension, a Configuration tree, and services.yaml loading. Laravel has no bundle registry, no Symfony config-tree semantics, and no service-tag compiler pass pipeline, so the package cannot be activated as a Laravel package. For Laravel you would need to discard the bundle and wrap the Lemon Way SDK or REST API behind your own service provider, config file, and facade.
- Which Laravel versions does lemonway/sdk-bundle support?
- None directly, because it is a Symfony bundle rather than a Laravel package. It does not declare Laravel service providers, Laravel version constraints, or Laravel-specific configuration publishing. Treat any assumption of Laravel compatibility as unsupported and plan a custom integration if you need Lemon Way inside a Laravel application.
- What operations does lemonway/sdk-bundle support for wallets, payments, and payouts?
- The described scope includes wallet creation, credit and debit operations, payment operations, and payout or transfer support for marketplace flows. It also covers configuration for merchant credentials and sandbox versus production endpoints. The exact capability depends on the wrapped Lemon Way SDK version and whether it targets the legacy XML v1 API or REST v2, so confirm that before estimating work.
- How do I configure Lemonway merchant credentials in Laravel?
- You cannot reuse the bundle's Symfony configuration tree in Laravel. The practical approach is a config/lemonway.php file containing merchant ID, key, secret, endpoint, and sandbox or production switching, loaded through a Laravel service provider. Keep those values in environment variables and resolve them through config so credentials stay out of business logic.
- How does lemonway/sdk-bundle handle errors and exceptions?
- The overview says exception handling is mapped to Laravel-friendly errors, but the code is Symfony-oriented and will not plug into Laravel's exception handler natively. In a Laravel build you should wrap calls behind your own PaymentProvider interface and translate vendor failures into domain exceptions. Log failures with PII redaction and include idempotency keys where money movement is involved.
- How should I test a Lemon Way integration in Laravel?
- Do not rely on the bundle for testing support, because there is no test suite evidence or Laravel test harness described. Test against Lemon Way's sandbox using your own typed client wrapper and fake the provider interface in unit tests. Cover wallet creation, payment initiation, payout, error mapping, webhook verification, and idempotent retries with deterministic fixtures.
- Is lemonway/sdk-bundle safe to use in production for payments?
- The technical risk is high: zero stars, zero dependents, a personal Bitbucket namespace, no CI or test suite evidence, no security disclosure channel, and no Packagist trust signal. In a payments path involving SEPA transfers, card acquiring, wallet balances, KYC documents, or PSD2 and SCA, that provenance is disqualifying. Use it as a design reference rather than a runtime dependency and complete your own compliance review.
- Is lemonway/sdk-bundle actively maintained and properly licensed?
- There is no evidence of active maintenance, CI status, release history, or a security disclosure process in the provided context. The license is described as ambiguous or absent, and the maintainer's relationship to Lemon Way is unknown. Ask whether the maintainer is official, a partner, or an individual before relying on it for any payment workflow.
- How do I install lemonway/sdk-bundle with Composer?
- Installation likely requires a raw VCS repository entry pointing at the Bitbucket repository because there is no Packagist trust signal described. That can require Bitbucket credentials in CI, which adds operational and security burden. Check the pinned SDK version, PHP constraint, license, and Guzzle major before attempting an install, especially if your Laravel app requires Guzzle 7.
- What are the best alternatives to lemonway/sdk-bundle for Laravel?
- The viable options are wrapping the official Lemon Way PHP SDK behind a Laravel service provider, config file, and facade, or writing a thin REST client against Lemon Way's documented API. The second is often preferable if the SDK is stale or pinned to old Symfony and Guzzle constraints. Keep the client behind your own PaymentProvider interface so you preserve multi-PSP optionality and can add retries, timeouts, and structured logging through Laravel's HTTP client.