dev3 ·
Which settings do I need to change in DEV3 Vendora (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#multi-vendor#marketplace#ecommerce#vendor-payouts
0
DEV3 Developer Forum
How do I configure payments, email and cron for DEV3 Vendora?
Ask a question
Every post is reviewed first. Usually reviewed within 24 hours.
1 reply
dev3 · Accepted answer
Payments
The default gateway is Simulated: checkout shows a test card page with Pay and Decline buttons and charges nothing. To take real payments, open Settings → Payments, choose Stripe, PayPal or Razorpay, set the store currency and keys (they are stored encrypted), and register the webhook https://your-domain/dev3/webhooks/payments/<gateway> in the gateway's dashboard. Test with sandbox or test-mode keys first: the PayPal and Razorpay drivers have not been run against live accounts.
Stripe Connect payouts (optional)
To pay vendors with Stripe transfers, enter your platform's Stripe secret key in Settings → Payments (transfers come from your Stripe balance in the store currency). Vendors choose Stripe Connect in their shop's payout settings and enter their acct_… account id. When an admin marks such a payout paid without a reference, Vendora sends the transfer and stores its id. The transfer has not been run against a live Stripe account, so try it in test mode first. Bank and PayPal payouts are recorded only: you send the money yourself and enter the reference.
Cron and queue
Add one cron entry that runs Laravel's scheduler every minute:
* * * * * cd /path/to/vendora && php artisan schedule:run >> /dev/null 2>&1In cPanel choose Once per minute and use the full PHP path if needed. System → System health shows when the scheduler last ran. Vendor earnings clear by date when the hold period ends, so no job is needed for that; the scheduler records its heartbeat and, only when DEMO_MODE=true, runs the nightly demo reset.
The queue is sync by default (jobs run inside the request; nothing to set up). For busy stores, set QUEUE_CONNECTION=database and run php artisan queue:work under Supervisor so order, shipping and payout emails go out in the background.
Until you set up mail, outgoing email is written to the log. Open Settings → Mail, choose SMTP and enter the host, port (587 for TLS or 465 for SSL), username, password and from address. Order, shipping, refund, payout and shop-approval emails all use it. In demo mode mail always goes to the log.
Two-factor authentication
Every account can add a second sign-in step under its profile (avatar menu → Profile): an authenticator app (TOTP) with 8 single-use recovery codes, or a 6-digit code by email (needs working mail). To make it compulsory for marketplace staff in /admin, turn on Settings → Security → Require 2FA for staff; it stays optional for vendors and customers. A super admin can clear a user's 2FA with Reset 2FA on the user's row, and if you lock yourself out, run:
php artisan dev3:2fa-reset you@example.comSecrets and recovery codes are encrypted with APP_KEY, so keep that key when you move servers. In demo mode the one-click logins never ask for a code.
0