What is required to accept client payments?
Connect your own Stripe account and complete its verification. Invoicing in a currency does not automatically make that currency payable online.
Historical recording: the walkthrough below shows the former Moolamochi-managed onboarding screen. Every plan now connects its own Stripe account; the written steps describe the current flow.
Watch the walkthrough
Who acts: Workspace Owner; operator configures missing provider credentials
Go straight to the steps
Playback and accessibility
Use Play or Pause, move back or forward 10 seconds, or restart from the title screen. Tab to a button, then press Enter or Space. Action captions are included in the video, and the complete written steps follow below.
Download the action captionsGo straight to the written stepsFollow the steps.
Open How clients pay and connect Stripe
The Owner opens Payment settings and chooses Connect your Stripe account. Every plan uses this route: authorize an existing Stripe account or create one in Stripe’s flow. A pasted payment link is not a substitute.
Open payment settingsInspect missing provider and payout evidence
The recording scrolls to the native no-verified-payout-events state. If Stripe is not configured, contact the operator before connecting or collecting. Secure test credentials, platform Connect access, its OAuth client ID and registered callback are prerequisites. Unavailable is not simulated success.
Ask about provider setupReview a restricted account’s consequences
The restricted-account demonstration lists incomplete requirements and disabled charges and payouts. The recording opens Disconnect new collection to inspect its consequences, without confirming. It does not perform Stripe onboarding. When configured, supply required identity and payout information in your Stripe Dashboard.
Cancel the review and check capabilities
Choose Keep connected to cancel the local disconnect review; the restricted requirements remain. In production, complete the provider requirements and refresh verified status before offering checkout. Unsupported currencies and methods remain unavailable even if invoicing in that currency is possible.
What changes when you finish
Only a verified eligible account enables new payment attempts. Test onboarding does not establish live readiness or prove a real bank settlement.
Every plan connects its own Stripe account
The workspace owner opens Payment settings and connects through Stripe’s official authorization, using an existing Stripe account or creating one in that step. Moolamochi reads the account’s capabilities before enabling online collection. Countries, currencies and payment methods follow what that Stripe account supports; an unsupported combination shows an unavailable payment route rather than an unverified Pay button.
Requirements and disconnection
Anything Stripe still needs, such as identity or business details, is resolved in your Stripe Dashboard; refresh the payment status afterwards. Disconnection blocks new attempts; existing attempts, charges, refunds and disputes keep their original account context.
Check readiness before inviting a client to pay
Payment settings shows whether your Stripe connection is ready. Complete any outstanding requirements in Stripe and refresh the status. A test payment does not move real money or confirm that your live account can accept payments. Contact support if the connection remains unavailable.
Primary-source references
External providers maintain their own requirements; consult the linked documentation for their current details.