Weave Code
Juno Sdk Php Laravel Laravel Package
jetimob/juno-sdk-php-laravel
Laravel integration for the Juno payment gateway, wrapping the Juno PHP SDK with a service provider, configuration, and facades to simplify creating charges, issuing boletos, processing credit card payments, and handling webhooks in Laravel applications.
Laravel SDK for Juno API
Frequently asked questions about Juno Sdk Php Laravel
- How do I install jetimob/juno-sdk-php-laravel in a Laravel application?
- Install it with Composer as jetimob/juno-sdk-php-laravel, then publish the package configuration and add your Juno credentials to the environment file. The package registers a service provider and facade so the Juno client can be resolved from Laravel's container. Check composer.json first, because the 2021-era constraints may prevent installation on newer Laravel and PHP versions.
- Which Laravel and PHP versions does this Juno SDK support?
- The package was written in 2021, and its Composer constraints likely pin illuminate/support to Laravel 6 through 8, guzzlehttp/guzzle to ^6 or ^7, and possibly PHP to 7.4. Because the repository is archived, no one is widening those constraints. Treat composer.json as the source of truth before planning an upgrade.
- Is jetimob/juno-sdk-php-laravel still maintained?
- No. The repository is archived, so it receives no dependency bumps, security patches, or updates for changes to the Juno API. With very low adoption, there is also little community triage or independent review. The license appears to be MIT, which generally permits a fork, but confirm the LICENSE file before relying on that.
- What Juno payment features does this Laravel package cover?
- It is described as wrapping the Juno PHP SDK to simplify creating charges, issuing boletos, processing credit card payments, and handling webhooks. Whether it covers Pix, digital account, transfers, or newer Juno product surfaces is not clear from the package description alone. Read the source and the underlying SDK to confirm the exact API version and endpoints.
- Can I use this package with Laravel 10 or Laravel 11?
- Probably not without changes. On Laravel 10 or 11 with PHP 8.2 or 8.3, Composer dependency resolution is likely to fail because of the old illuminate/support and Guzzle constraints. Adoption there is a fork-and-maintain decision: widen the constraints, then verify the underlying client does not rely on removed PHP 8 behavior.
- Does this SDK handle Juno OAuth2 token caching and refresh?
- That is unknown from the package overview and must be verified in the source and in jetimob/juno-sdk-php. A client frozen in 2021 has no mechanism to track Juno's later OAuth2 and token-handling changes. If it re-authenticates on every call or cannot refresh tokens safely, that is a production concern rather than a minor inefficiency.
- Does it verify inbound Juno webhook signatures?
- The available evaluation could not confirm whether webhook authenticity is validated. Hidden surface area like this is exactly why you should read the source before relying on it. If signature verification is missing, you must add it in your application or a fork before exposing a webhook endpoint.
- Is it safe to use this archived Juno SDK for credit card payments in production?
- Technical risk is high because the package is archived, receives no security patches, and sits in the payment path where the blast radius is largest. Confirm whether it stays inside Juno's tokenization flow or ever touches raw card data, and review its transitive dependency CVE exposure. For PCI-adjacent work, an unmaintained SDK is a liability unless you fork it and take ownership.
- What are the alternatives to jetimob/juno-sdk-php-laravel?
- Options, from least to most ownership, are using the underlying jetimob/juno-sdk-php directly if it is still maintained, building a thin in-house adapter over Juno's HTTP API using Laravel's Http client, or forking and republishing this package internally. A focused adapter for authentication, token caching, a couple of product endpoints, and webhooks is often only a few hundred lines. That can be cheaper than owning a stale fork and gives you control over retries, idempotency, and observability.
- Is there a test suite, and how should I validate the package against the Juno sandbox?
- It is not clear from the package overview that a meaningful test suite exists, and with such low adoption there is little evidence of independent verification. Plan to test authentication, charge creation, boleto issuance, card payment, and webhook handling against Juno's sandbox before production. Also check whether the underlying client supports retries, idempotency keys, and token refresh, since missing behavior there is a production incident class.
Weaver
How can I help you explore Laravel packages today?