Weave Code
Braintree Bundle Laravel Package
shwrm/braintree-bundle
This package provides a Braintree integration for PHP applications, making it easier to configure credentials and access Braintree payment services. Use it to streamline payment processing setup and reduce boilerplate when working with Braintree.
Symfony 2 Bundle for Braintree's PHP client library
Frequently asked questions about Braintree Bundle
- Is shwrm/braintree-bundle compatible with Laravel?
- No. It is a Symfony 2 bundle in the CometCult\BraintreeBundle namespace, registered through AppKernel::registerBundles(), and it relies on Symfony's DependencyInjection extension and prepend conventions. Laravel uses Illuminate\Support\ServiceProvider and its own container with no bundle loader, so there is no supported registration path. Do not add it as a Laravel dependency.
- Can I install shwrm/braintree-bundle in a Laravel 11 app?
- It will not work in a modern Laravel application. The bundle's era-appropriate Composer constraints target PHP 5.6 to 7.x and will hard-block composer update on Laravel 10, 11, or 12 running PHP 8.2+. Even if forced in, there are no Illuminate service provider bindings, so the Braintree gateway is never registered.
- What does shwrm/braintree-bundle actually provide under the hood?
- It delivers a configuration array plus a Symfony DIC service definition around the official braintree/braintree_php SDK. That is roughly 100 to 150 lines to reproduce idiomatically in Laravel as a config file, a service provider, and an injected gateway class. There is no Laravel-specific functionality to salvage.
- How do I integrate Braintree payments into Laravel without this package?
- Depend on braintree/braintree_php at a currently supported major and bind Braintree\Gateway as a singleton in a small service provider. Publish a config/braintree.php that reads merchant ID, public key, private key, and environment from env vars. Wrap the gateway in a domain-level PaymentGateway interface for charge, vault, refund, client token, and webhook verify so controllers never touch vendor types, and fake that interface in tests.
- Is shwrm/braintree-bundle safe to use in production for card payments?
- No. The repository has zero stars, zero dependents, and a single maintainer, so there are no downstream users providing implicit test coverage or issue triage. It also pins a legacy Braintree wrapper that predates SCA/3DS2, client token changes, and current webhook signature handling. A pinned abandoned wrapper in a cardholder-data-adjacent path is a compliance and security liability.
- Does shwrm/braintree-bundle support Laravel Cashier or subscriptions?
- No. The bundle has no Laravel integration and no documented subscription or plan-management layer; its scope is basic gateway wiring for one-off charges and vaulting. If subscriptions are in scope, evaluate a maintained first-party billing abstraction rather than inheriting a second abandoned dependency. Verify the current maintenance status of any Laravel Cashier Braintree variant before committing.
- What are the alternatives to shwrm/braintree-bundle for Laravel?
- The production dependency should be the official braintree/braintree_php SDK behind an internal adapter registered by a Laravel service provider. That keeps the vendor swappable and avoids dead Symfony 2 abstractions in your codebase. If your requirements are flexible, evaluate payment providers on SDK maintenance cadence and PCI posture before choosing a gateway.
- How should I verify Braintree webhooks in Laravel?
- Add a webhook controller that calls Webhook::parse() to verify the signature before any state change, then record the Braintree notification ID in an idempotency table to prevent duplicate processing. Do not rely on this bundle for webhook handling; its Symfony 2-era structure is not a Laravel pattern, and SDK drift means signature behavior may be stale. Keep verification in your own adapter layer so the logic is testable.
- How much work is it to replace shwrm/braintree-bundle with a native Laravel integration?
- Expect roughly 100 to 150 lines: a published config file, a service provider binding Braintree\Gateway as a singleton, and a thin domain interface around charge, vault, refund, client token, and webhook verify. That is less effort than building a shim between Symfony 2's container and Laravel's, and it leaves no legacy abstractions behind. Budget extra time for webhook idempotency and tests.
- What PHP and Laravel versions do I need for Braintree today?
- Current Laravel 10, 11, and 12 on PHP 8.2+ require the modern braintree/braintree_php SDK with ext-curl and ext-openssl enabled. The legacy constraints in shwrm/braintree-bundle will not satisfy those requirements. Check the official SDK's release notes for the exact supported versions before pinning.
Weaver
How can I help you explore Laravel packages today?