Send Again
Close
X
Login
Already have an account with us Login to your account
X
Sign Up
Create an account with Webkul Store
Please Login to Write Your Review
X
- Description
- Reviews
- FAQ
- Customers ()
- Specifications
- Cloud Hosting
- Changelog
Laravel Marketplace Stripe Payment Gateway: The extension integrates Stripe Connect into Bagisto Laravel eCommerce Marketplace allowing vendors to accept online card payments from their customers. The payment gateway supports the split payment facility which automatically distributes the funds to multiple sellers.
Please Note - To use this extension, you must purchase and install Laravel Multi Vendor Marketplace, first.
Highlighted Features
Split Payment
Split the customer's payment among the sellers and the admin.
Stripe Connect API
Using the Stripe Connect the seller can connect the own stripe account with the admin’s Stripe account.
Revoke Stripe Account
The seller can revoke stripe account for the eCommerce store at any time.
Supported Card Type
Accept all the cards that the Stripe supports.
Stripe Plugin Partner
Stripe is a simple and powerful way to accept payments online. Millions of businesses—ranging from startups to Fortune 500 companies—rely on Stripe’s software tools to accept payments securely and expand globally.
Webkul is proud to be associated with Stripe in developing customized payment gateway solutions for e-commerce stores, marketplaces, and mobile apps.
- Stripe is available to businesses in over 35 countries.
- Accept all major debit & credit cards, wallets, local payment methods.
- Supports processing payments in 135+ currencies
- Stripe meets the most stringent industry standards for security. Stripe is also audited by a PCI-certified auditor and is certified to PCI Service Provider Level 1.
Why Need Stripe Payment Gateway for Laravel eCommerce Marketplace?
Basically, the Laravel marketplace payment gateway used where an admin needs to split the payment automatically among seller and admin. No doubt stripe is the easiest and most scalable payment gateway of the modern time. To avoid malicious activities and fraud we are providing a secure and safe payment for Laravel multi-vendor marketplace sites.
Stripe Transaction Environment
After the installation of the Laravel Marketplace Stripe Payment Gateway, admin can connect their store with a stripe payment gateway. Admin can manage module configuration and enable the various features.
- The admin can set that the stripe fee will be paid by the customer or the seller.
- The admin can enable or disable the module for testing.
- The admin can set the payment method title which will be displayed on the front end.
- The admin can enable or disable this module.
Seller - Stripe Connect
After the admin has connected the store with stripe payment then the seller has to connect with the payment method by configuring the payment method from their account. The seller can easily connect with a stripe account using stripe connect.
- The seller can accept the payments for all the products after connecting the own stripe account.
- The seller can revoke the stripe account access.
- The seller can view the transaction detail from the seller panel.
Stripe Checkout Process
At the time of checkout, the customer can select the payment method as Stripe, to pay with stripe. The customers have to enter their credit card details to complete the order.
- Customers can save the card detail for future payment.
- After selecting the address, shipping method, the customers can pay via saved cards.
- After successful payment, they will get order id.
Customer Order Detail
After placing the order, the customer can view the order status from the order section. Customers can check order status processing, pending, and completed from the order section.
- Customers will get order notification main on their email id.
- The Customer can view order information.
- Customers can view invoice detail.
- View the selected payment method to place the order.
Seller Order History
After placing the order by customers, the seller can manage the order placed via the Stripe payment method. The seller can view order detail in the order section and the seller can check transaction details for that order detail.
- The seller can view all orders pay via stripe.
- The vendor can create an invoice for that order.
- The seller can ship the product.
Support
For any issue related to this module, please create a support ticket here at - https://webkul.uvdesk.com/en/customer/create-ticket/ or send an email to [email protected]
You may also check our quality Bagisto Extensions.
Specifications
Product Version2.4.9
Released6 years ago
CategoryBagisto Laravel, Marketplace, Payment,
Last UpdatedAugust 20, 2026 (12 days ago)
License Single application
Supported VersionsBagisto 2.4.x
Write a review
Frequently Asked Questions
Which card types are supported by this module?
Accept all the cards that stripe supports.
Does the payment get transferred automatically to the vendor and admin Account?
Yes, the customer’s payment automatically splits between the seller and the admin.
Who will pay a Stripe commission fee?
Admin can set from the configuration stripe fee pay by seller or customer.
What is the Stripe transaction fee?
The Stripe transaction fee is 2.9% + 30 Cents for every purchase.
What amount will the seller receive?
Seller will receive all the amount of the product after deducting the commission fee by admin.
Specification
Detailed technical features and requirements to help you understand the module’s capabilities and ensure smooth integration with your system.
Cloud Hosting
Detailed technical features and requirements to help you understand the module’s capabilities and ensure smooth integration with your system.
Move to Cloud Today
We’re partnered with top-tier, trusted providers!
Default Configuration Details of Server
1 GB
RAM 1 Core
Processor 30 GB
Hard Disk
RAM 1 Core
Processor 30 GB
Hard Disk
1 GB RAM & 1 Core Processor
Database
Database
Want to know more how exactly we are going to power up your eCommerce Website with Cloud to fasten up your store
* Server Configuration may vary as per application requirements.
Change Logs
- + Feature Add (+)
- - Feature Remove (-)
- ! Bug Fixed (!)
- * Modification (*)
Version 2.4.9
- + Compatible with Bagisto v2.4.9 and Marketplace v2.4.9.
- ! Fixed a boot-time crash by deferring conditional menu, ACL, and asset registration until the application has booted.
- ! Fixed the admin Stripe payment requests page redirecting to the dashboard by applying the web middleware group to the admin routes.
- ! Fixed seller payout amounts to match the core marketplace calculation for both automatic and admin queued payouts.
- ! Fixed Stripe transfer amounts for zero-decimal currencies and ensured the transfer currency is sent in lowercase.
- ! Fixed duplicate Stripe connection rows on reconnect using updateOrCreate with a unique index on marketplace_seller_id.
- ! Fixed Stripe account revocation to retain the local connection and display the actual Stripe error when deauthorization fails.
- + Added OAuth state parameter validation for Stripe Connect authorization to prevent CSRF attacks.
- + Changed the single seller payout action from GET to POST with CSRF protection.
- + Added client_id validation to keep Stripe Connect routes, menus, ACL, assets, and payout features inactive when it is not configured.
- + Added an Allowed Seller Countries setting populated from Stripe supported transfer countries.
- + Prevented sellers from connecting Stripe accounts from countries that are not allowed.
- - Removed the old non-functional Region setting.
- + Stripe payment requests are now created only for sellers connected to Stripe, while other sellers continue using the standard marketplace payout flow.
- + Prevented sellers from revoking their Stripe account while payouts are pending.
- + Locked the seller country during Stripe onboarding using the Stripe account country prefill.
- * Reorganised Stripe payment requests under Marketplace → Sales to match the core marketplace structure.
- + Added a Stripe Connect onboarding banner to the marketplace-stripe:install command.
- * Improved the Vite build with flexible application-root resolution and a BAGISTO_ROOT override.
- + Added a publishables npm script to build and sync compiled assets into the publishable/build directory.
- + Added the Romanian (ro) locale and synchronized all 24 locales.
- * Updated labels to Stripe Payment Requests and Connect With Stripe.
Version 2.4.8
- Renamed
stripe_payment_manageoption values from ambiguousadmin/sellerto clearmanual/autopayacross all 23 locale files. - Updated the field title to "Payout Mode".
- The "Manual Payout" option keeps admin in control of payouts.
- The "Auto Payout" option triggers automatic Stripe transfers to connected accounts on invoice.
- Fixed 500 error on seller sales/orders datagrid caused by incorrect route names (
seller.transactions.view→seller.sales.transactions.view,seller.payment.request→seller.sales.payment.request).
Version 2.4.6
- Compatible with Bagisto v2.4.6 and Marketplace v2.4.6.
- Moved the seller Stripe Connect onboarding out of the storefront (
marketplace/stripe/connect) into the seller settings panel (seller/settings/stripe). - Renamed all seller routes to the
seller.settings.stripe.*namespace and updated the breadcrumbs, seller menu, and views accordingly. - Seller payouts are now processed through a dedicated queued job (
ProcessStripePayout) with one Stripe transfer per job. - Added an idempotency guard to prevent double payouts on retried or duplicated jobs.
- Added a "Pay" mass action on the admin Stripe payment requests datagrid so multiple seller payouts can be queued and settled at once.
- Already-paid rows are skipped during mass payout processing.
- Added a payout summary showing payable orders, unpaid total, total commission, and unpaid sellers on the admin Stripe payment requests page.
- Seller transaction comments now include Stripe transfer details such as transfer ID, destination connected account, balance transaction, and transferred amount.
- Stripe OAuth onboarding failures now display Stripe's actual error message instead of a generic message.
- Redesigned the seller Stripe Connect page with dark-mode support.
- Registered dedicated admin and seller styles through Bagisto Vite.
- Upgraded the build tooling to Vite 6 and laravel-vite-plugin 1.x with ESM (
.mjs) configuration. - Stripe Connect header styles are now injected only when both the Stripe payment method and marketplace are active.
- Guarded the listener against a missing
core_configtable during installation.
Version 2.4.4
- + Compatible with Bagisto v2.4.4 and Marketplace v2.4.4.
- + Checkout payment is now handled by the Bagisto Stripe payment gateway (Webkul\Stripe). This package now manages only the marketplace split payment (Stripe Connect) on top of it.
- + Seller transfers and payment requests are now created automatically once the order's invoice is generated.
- + Seller related Stripe settings (Client Id, Payment Manage by, Region) are now merged into the core Stripe payment method configuration.
- + Renamed the translation/view namespace from stripe:: to stripe_connect::.
- - Removed the in-package checkout flow, saved card checkout, payment intent webhook and refund override, as these are handled by the core Stripe payment package.
- - Removed the customer/seller Stripe application fee configuration.
Version 2.3.9
- + Managed for Marketplace Updates.
- + Updated for Stripe 19.1.0.
Version 2.3.0
- + Compatible with Bagisto v2.3.0
Version 2.0.0
- + Compatible with Bagisto v2.0.0
- * Stripe payment module should be disabled if status is off
Version 1.5.1
- + Compatibility issue fixed with Bagisto v1.5.1
Version 1.3.3 (26 Nov, 2021)
- + Compatibility issue fixed with Bagisto v1.3.3
Version 1.3.0 (17 May, 2021)
- + Compatible with Bagisto v1.3.0, v1.3.1, v1.3.2
- * Description field should not be mandatory
- * All required fields should be disabled if status is off
