Laravel Marketplace Stripe Payment Gateway

PROJECT_URL/marketplace/stripe/connect/retrieve/token

Set up webhooks in Stripe:

• Test Mode: https://dashboard.stripe.com/test/workbench/webhooks
• Live Mode: https://dashboard.stripe.com/workbench/webhooks

• Add a new destination

• Select events:
  • • payment_intent.canceled
  • • payment_intent.succeeded

• Select Webhook endpoint

Set the webhook URL as:

https://your_domain/api/stripe/webhook/payment-intent

Copy the signing secret and set it in:

Admin → Configuration → Sales → Payment Methods → Payment Intent Webhook Secret

To get the API Keys you can use Stripe website. First you’ll need to Sign in to the stripe account.

Go to https://dashboard.stripe.com/login then enter your login details.

Step 1:- From the left sidebar, click on Developers >> API Keys to get your Publishable Key and Secret Key. You can toggle between Test Mode and Live Mode as required.

Step 2:- Copy the Publishable Key (pk_test / pk_live) and Secret Key (sk_test / sk_live) from the API Keys section.

Step 3:- Now click on Settings >> Connect >> Settings. Here you will find your Client ID.

Step 4:- In the same Connect Settings page, scroll to the Redirect URLs section and add your redirect URL like https://example.com/marketplace/stripe/connect/retrieve/token. Make sure the URL matches exactly.

Step 5:- Ensure that OAuth for Standard Accounts is enabled in the Connect settings if you are using Stripe Connect.

StripeConnect Bagisto Configuration

The module inherits the standard Stripe gateway section from the admin package (Status, Title, Description, Logo, API keys, Sandbox toggle, Sort order) and appends the three marketplace payout fields onto it. The image below shows the whole Stripe block as rendered in our running demo.

Client ID

This text field holds the Client ID of your Stripe Connect platform (ca_...). It is not channel based, so one value applies to the whole store. Both the admin payout routes and the seller onboarding route depend on it. When the field is empty, the seller panel shows “Client ID not set by admin” instead of the Connect button.

Payout Mode

The Payout Mode select toggles between Manual Payout and Auto Payout. In manual mode the invoice listener creates a payment request per connected seller and the admin settles it from the payment request screen. In contrast, autopay removes the admin’s clicking entirely — the transfer fires the instant the invoice saves and the request flips to paid. Manual is the default.

Allowed Seller Countries

The multiselect uses Stripe’s CountrySpec data to list every country the platform can transfer to. Choose the countries whose sellers may connect — the connect button hides for sellers outside the list and shows a “not supported in your country” note. Leaving the field empty allows all transfer-enabled countries.

Step-by-Step Configuration Walkthrough

1. First, log in to the admin panel and open Sales → Payment Methods.
2. Next, mark the Stripe method as Active and fill in its Title, Description, and logo.
3. Then, toggle the Sandbox switch and paste the matching test or live Secret Key and Publishable Key.
4. Afterwards, paste your Stripe Connect platform Client ID into Client Id.
5. Next, choose Manual Payout or Auto Payout from the Payout Mode dropdown.
6. Then, pick the Allowed Seller Countries or leave the field empty for unrestricted access.
7. Finally, save the form and confirm the new fields appear at the bottom of the Stripe block.

Stripe Connect Admin View

The module adds a Marketplace → Sales → Stripe Payment Requests screen. With that in mind, here is how the settlement desk looks in our demo: four statistics cards — Payable Orders, Unpaid, Total Commission, and Unpaid Sellers — lead the page, and a datagrid follows with every request joined to the order, marketplace order, transaction, and seller record. Each row shows order ID, date, order status, customer name and email, gross amount, seller total invoiced, seller, shop, and the amount already paid.

Stripe Payment Requests

Step-by-Step Guide

1. First, expand Marketplace → Sales in the admin sidebar and open Stripe Payment Requests.
2. Next, read the stats cards to gauge how many payouts are waiting and how much commission the settlement already earned.
3. Then, scan the grid rows — paid requests show the Already Paid label, unpaid ones show a Pay button.
4. After that, track an order to its detail page with the view icon when you need the original invoice.
5. Finally, filter or sort by date, status, customer, seller, or shop to narrow the backlog.

Paying a Single Request

The Pay action on an unpaid row runs the payout synchronously, so the admin receives immediate feedback. The payout job verifies the request still shows To Pay, finds the matching marketplace order, then creates a real Stripe Transfer to the seller’s connected account and records the seller transaction in the same pass. Consequently, the transaction row appears only after the transfer completes. The screenshot below shows the green “Payment transfer successfully” toast right after settling the request for order SC100002.

Step-by-Step Guide

1. First, open Stripe Payment Requests and find the row whose status still shows To Pay.
2. Next, click Pay on that row.
3. Then, wait for the Stripe transfer to complete against the seller’s linked account.
4. Finally, confirm the success toast and the Already Paid label on the row, plus the transaction recorded on the order page.

Mass Payout

Instead of paying row by row, select several unpaid requests and hit the Pay mass action. The mass pay endpoint queues one ProcessStripePayout job per unpaid request, and a response previews the number of queued transfers before the queue worker starts.

Step-by-Step Guide

1. First, tick the checkboxes of every unpaid payment request you want to settle.
2. Next, click the Pay button from the mass actions toolbar.
3. Then, confirm the message that reports how many transfers were queued.
4. Finally, let the queue worker run the one-transfer-per-job scripts, then refresh the grid to see the paid labels.

Stripe Connect Seller View

Connecting a Stripe Account

Sellers reach their onboarding surface from Settings → Stripe Connect inside the seller panel. Similarly, control stays entirely on the seller: a Connect With Stripe button opens the Stripe Connect hosted authorization, the callback exchanges the code for an access token, and the module stores the publishable key plus the connected account ID. The screenshot below is the fresh, not-yet-connected screen of a demo seller.

Step-by-Step Guide

1. First, sign in to the seller panel and open Settings → Stripe Connect.
2. Next, make sure the admin enabled Stripe and set a client ID; otherwise the notice explains why the button is missing.
3. Then, click Connect With Stripe and complete the Stripe-hosted onboarding for your account.
4. Afterwards, return to the panel — the callback stored your access token and account ID, and the screen flips to the connected state.
5. Finally, go back to selling; the platform now captures your payout share from Stripe orders automatically.

Connected Account & Revoking Access

Once connected, the same screen exchanges the Connect button for a Revoke Your Stripe Accounts Access button plus a storefront-style confirmation. Meanwhile, the guarded revoke flow protects both sides: sellers with pending payout requests cannot revoke — the button disables and the helper message explains that the control stays locked while payment requests are pending, so the platform can still settle owed money.

Step-by-Step Guide

1. First, reopen Settings → Stripe Connect to review the connected state.
2. Next, check the revoke button — a disabled one plus a pending-payout message means the platform still owes you money.
3. Then, click Revoke Your Stripe Accounts Access when no requests are pending.
4. Finally, confirm the confirmation prompt, then watch the deauthorization call remove the stored seller token.

Payout Status in the Seller Orders Grid

Stripe orders behave differently from normal marketplace orders on the seller side. Therefore, the seller grid communicates settlement state clearly: a completed Stripe order whose transfer has not yet settled shows its payout as Requested, and the seller cannot press any “request payment” action because the admin already claims that transfer on the seller’s behalf. The screenshot below shows the seller order grid with the two awaiting rows flagged Requested.

Step-by-Step Guide

1. First, open Orders in the seller panel.
2. Next, look for the rows carrying the Requested payout label — those are completed Stripe orders awaiting settlement.
3. Then, check whether the Request Payment action is missing for those rows; the module suppressed it on purpose.
4. Finally, wait for the admin to settle the request, after which the order shows as paid.

Conclusion

Ultimately, StripeConnect Bagisto turns a single Stripe account into a full split-payout engine. Sellers connect once through hosted onboarding, orders feed payout requests automatically, and the admin settles them with real transfers — one at a time or in bulk — while an idempotency guard keeps every payout unique. The seller grid keeps everyone informed with the Requested status, and country controls make the feature safe to roll out across regions. If you are growing a marketplace on Bagisto and want payouts to feel native, this module is the missing link between checkout and seller trust.

Hope it will be helpful for you or if you have any issue feel free to raise a ticket at https://bagisto.uvdesk.com/en/