Download the PHP package omnipay/stripe without Composer
On this page you can find all versions of the php package omnipay/stripe. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
More information about omnipay/stripe
Files in omnipay/stripe
Informations about the package stripe
Stripe driver for the Omnipay PHP payment processing library
Omnipay is a framework agnostic, multi-gateway payment processing library for PHP. This package implements Stripe support for Omnipay.
Omnipay is installed via Composer. To install, simply require
omnipay/stripe with Composer:
The following gateways are provided by this package:
For general usage instructions, please see the main Omnipay repository.
The Stripe integration is fairly straight forward. Essentially you just pass
token field through to Stripe instead of the regular credit card data.
Start by following the standard Stripe JS guide here: https://stripe.com/docs/tutorials/forms
After that you will have a
stripeToken field which will be submitted to your server.
Simply pass this through to the gateway as
token, instead of the usual
Stripe Payment Intents
Stripe Payment Intents is the Stripe's new foundational payment API. As opposed to Charges API, Payment Intents supports Strong Customer Authentication. It means that during the payment process, the user might be redirected to an off-site page hosted by the customer's bank for authentication purposes.
This plugin's implementation uses the manual Payment Intent confirmation flow, which is pretty similar to the one the Charges API uses. It shouldn't be too hard to modify your current payment flow.
1) Start by collecting the payment method details from the customer. Alternatively, if the customer has provided this earlier and has saved a payment method in your system, you can re-use that.
2) Proceed to authorize or purchase as when using the Charges API.
- If you have a token, instead of a payment method, you can use that by setting the
tokenparameter, instead of setting the
returnUrlmust point to where you would redirect every off-site gateway. This parameter is mandatory, if
confirmis set to true.
- If you don't set the
true, you will have to manually confirm the payment intent as shown below.
At this point, you'll need to save a reference to the payment intent.
$_SESSION can be used for this purpose, but a more common pattern is to have a reference to the current order encoded in the
$completePaymentUrl URL. In this case, now would be an excellent time to save the relationship between the order and the payment intent somewhere so that you can retrieve the payment intent reference at a later point.
3) Check if the payment is successful. If it is, that means the 3DS authentication was not required. This decision is up to Stripe (taking into account any custom Radar rules you have set) and the issuing bank.
4) The customer is redirected to the 3DS authentication page. Once they authenticate (or fail to do so), the customer is redirected to the URL specified earlier with
5) Retrieve the
$paymentIntentReference mentioned at the end of step (2).
6) Now we have to confirm the payment intent, to signal Stripe that everything is under control.
Stripe connect applications can charge an additional fee on top of Stripe's fees for charges they make on behalf of
their users. To do this you need to specify an additional
transactionFee parameter as part of an authorize or purchase
When a charge is refunded the transaction fee is refunded with an amount proportional to the amount of the charge
refunded and by default this will come from your connected user's Stripe account effectively leaving them out of pocket.
To refund from your (the applications) Stripe account instead you can pass a
refundApplicationFee parameter with a
boolean value of true as part of a refund request.
Note: making requests with Stripe Connect specific parameters can only be made using the OAuth access token you received as part of the authorization process. Read more on Stripe Connect here.
Stripe accounts have test-mode API keys as well as live-mode API keys. These keys can be active at the same time. Data created with test-mode credentials will never hit the credit card networks and will never cost anyone money.
Unlike some gateways, there is no test mode endpoint separate to the live mode endpoint, the Stripe API endpoint is the same for test and for live.
If you want to keep up to date with release announcements, discuss ideas for the project, or ask more detailed questions, there is also a mailing list which you can subscribe to.
If you believe you have found a bug, please report it using the GitHub issue tracker, or better yet, fork the library and submit a pull request.