Weave Code
Stripe Laravel Package
omnipay/stripe
Omnipay Stripe is a Stripe payment gateway driver for the Omnipay PHP library. It lets you create charges, manage customers and cards, issue refunds, and handle tokens through a consistent Omnipay API, with support for standard Stripe test and live workflows.
Stripe driver for the Omnipay PHP payment processing library
Frequently asked questions about Stripe
- What is omnipay/stripe used for in Laravel?
- It is the official Stripe driver for the Omnipay payment library, giving PHP and Laravel applications a consistent gateway API for Stripe charges, authorizations, captures, refunds, voids, customers, and tokens. In Laravel it is usually wrapped in an internal payment service rather than used directly in controllers. It is not a Laravel-native billing package like Cashier.
- How do I install omnipay/stripe in a Laravel app?
- Install it with Composer and configure an Omnipay gateway using your Stripe secret key and test or live mode settings. In Laravel, bind the gateway through the service container or a small payment service, then call purchase, authorize, capture, or refund from that service. Pin the package version and validate Composer constraints against your Laravel, PHP, and Symfony versions before deployment.
- Does omnipay/stripe support Payment Intents and SCA/3D Secure?
- The package description lists support for Stripe Charges, Payment Intents, and SCA/3D Secure flows. Because Stripe payment flows evolve, confirm the exact request classes and API version in the package release you install. Run a staging proof of concept that covers authentication-required payments and failure handling before relying on it in production.
- Is omnipay/stripe compatible with Laravel 11 and PHP 8?
- The provided context does not publish a Laravel 11 or PHP 8 support matrix for omnipay/stripe. Because the package is framework-agnostic and last released in 2022, you must validate Composer constraints against your Laravel, PHP, and Symfony versions. Pin the version and run composer why-not plus a full test suite on the production runtime image.
- How do I handle Stripe webhooks with omnipay/stripe?
- You should build a Laravel webhook endpoint that receives Stripe events and verifies the Stripe signature before processing them. Omnipay Stripe can be extended for custom Stripe requests, but webhook signature verification and event idempotency must be implemented and tested in your application. Include webhook receipt and failure cases in the integration proof of concept.
- Does omnipay/stripe handle authorize, capture, refund, and void?
- Yes. The driver exposes Omnipay's authorize, capture, purchase, refund, and void operations, which map to Stripe payment flows. You should still contract-test each operation against Stripe test mode, including partial refunds and failure responses if your business requires them. Keep these calls behind an internal payment interface so the gateway can be replaced.
- Is omnipay/stripe actively maintained and safe for production?
- The last release date in the provided context is 2022-03-22, with modest stars and an unknown repository, so maintainer and lifecycle risk should be reviewed. That does not make it unusable, but Stripe APIs and payment flows change continuously. Treat it as a conditional fit and budget for a maintained fork or migration path if the driver stalls.
- Should I use omnipay/stripe or stripe/stripe-php in Laravel?
- Use omnipay/stripe when you already standardize on Omnipay or need a multi-gateway abstraction across payment providers. For a greenfield Laravel application, stripe/stripe-php directly, or Laravel Cashier for subscriptions, is usually the lower-risk architecture. If you choose Omnipay, isolate it behind your own PaymentGateway interface to reduce lock-in.
- How do I test omnipay/stripe payments before going live?
- Use Stripe test mode keys and test cards in a staging proof of concept. Cover purchase, authorize and capture, refund, void, SCA/3DS, Payment Intents, webhook signature verification, idempotency behavior, and error mapping. Do not migrate raw card data, and keep Stripe customer and payment method identifiers stable during parallel runs.
- Does omnipay/stripe support idempotency keys, partial refunds, and subscriptions?
- The provided context confirms authorize, capture, purchase, refund, void, token storage, and customer management, but it does not guarantee idempotency keys, partial refunds, or subscriptions. Those features depend on the package version and Stripe API coverage and must be validated in your proof of concept. For subscription billing in Laravel, evaluate Laravel Cashier or direct Stripe SDK integration instead.
Weaver
How can I help you explore Laravel packages today?