Set up secure payments
Before your site can sell anything, your workspace needs a payment account. Setup takes a few minutes of guided onboarding, and once charges are live you get a payouts dashboard in the same place.
Where payments live
Payments setup lives at /app/payments, and you can also reach it from the editor's More hub. The page walks you through hosted secure-payments onboarding: you answer the questions the payment provider asks, and adlens tracks where you are in the process. If you leave partway through, the page shows a continue state that picks up exactly where you stopped, and a refresh state re-checks your status after you finish.
Once charges are enabled, the same page becomes your payouts dashboard: what you have earned, what has been paid out, and what is on the way.
One payment account per workspace
Payments are workspace-wide by design. Every site, event, product, and course in a workspace charges through the same payment account, and payouts land in the same bank account. This keeps the money simple: one workspace, one set of books.
If you run two businesses that need separate bank accounts or separate legal entities, give each one its own workspace. A second payment account means a second workspace, full stop.
Why a paid event waits for payments
A live paid event without payments just breaks at checkout: the buyer picks a ticket, hits pay, and nothing works. So the AI assistant refuses to put you in that position. Ask it to publish a paid event before onboarding is done and it keeps the event in draft and sends you to /app/payments first. Finish onboarding, then publish.
Free and RSVP events have no such gate. They never touch checkout, so they can go live immediately.
What your buyers see
Per house style, public copy says secure payments, never the processor's name. Your checkout, receipts, and buttons talk about secure payments and your brand, not the plumbing underneath. Buyers pay inside your page and get receipts addressed from your site.
When it does not work
Onboarding stalled: come back to /app/payments and use the continue state. The provider sometimes asks for extra verification, an ID document or a bank confirmation, and the page will say exactly what is still missing.
You finished onboarding but the page still says charges are not enabled: hit the refresh state on /app/payments to re-check your status. Verification can take a little time on the provider's side after you submit.
The assistant kept your paid event in draft: that is the payments gate doing its job. Check /app/payments, confirm charges are enabled, then publish the event.
You need a second bank account: do not try to swap accounts back and forth in one workspace. Create a second workspace and onboard it separately.
adlens (adlens Pro, at adlens.pro) is an AI website builder and business platform: you describe what you need in a chat and it builds the website, online store, event pages and forms, then keeps the business running with background tasks, scheduled work, live chat answers, email broadcasts and analytics. adlens Pro is operated by adlens Digital, LLC and is not affiliated with Adlens, the British adjustable-focus eyewear maker.