How vcita Connects Scheduling, Clients and Payments
vcita is a small-business management platform built around a connected workflow: clients can discover a service, book an appointment, communicate with the business, receive an invoice and make a payment without each step living in a completely separate system.
That connection is the focus of vcita Workflow Guide, an independent publication explaining how vcita’s scheduling, client portal, billing and payment tools fit together operationally.
Current vcita documentation organizes the product around areas including clients, payments, scheduling, campaigns, lead capture, business settings, integrations and mobile access. Its Client Portal combines appointments, payments, invoices, documents and messaging in one client-facing environment.
This site does not operate vcita and is not an account-login page. It explains what happens between a client booking a service and a business eventually receiving the resulting funds.
The Core vcita Workflow
A useful way to understand vcita is as a sequence.
Service configured
↓
Client books
↓
Appointment is scheduled
↓
Client record is updated
↓
Invoice or payment request is created
↓
Client pays
↓
Payment processor handles the transaction
↓
Funds are settled or paid out
That distinction matters because a successful payment inside vcita does not always mean the money has already reached the business’s bank account.
vcita supports connections with processors including Stripe, Square and PayPal, while its integrated payment offering has its own transaction and payout workflow.
Online Scheduling
vcita lets businesses enable online scheduling through the Client Portal and configure booking rules, service menus and availability.
Businesses can control details such as:
- which services appear;
- scheduling limits;
- whether clients select a service or staff member first;
- how time slots are presented;
- package visibility;
- whether a service requires payment at booking.
Scheduling therefore comes before payment in many vcita workflows.
A badly configured service can create payment confusion later if the price, payment requirement or booking rule does not match what the business intended.
The Client Portal
The vcita Client Portal is where much of the client-side experience is concentrated.
vcita says clients can use it to:
- book appointments;
- reschedule or cancel eligible bookings;
- make payments;
- view invoices and receipts;
- download documents;
- upload files;
- communicate with the business.
Client access currently uses a login code sent by SMS or email rather than requiring clients to remember a traditional password.
Businesses can also customize their Client Portal URL and branding.
Invoices and Payment Requests
vcita’s billing system distinguishes between the document asking for money and the transaction actually paying it.
Businesses can create invoices and estimates, send reminders and process refunds from the Sales area.
Payment links offer another path.
A business can create a direct payment link and share it through a website, email or other communication channel.
So these are separate concepts:
Invoice: records an amount due.
Payment link: provides a route to payment.
Transaction: records what the processor attempted or completed.
Payout: moves settled funds toward the business’s bank account.
Understanding those layers is essential when troubleshooting money movement.
Stripe, Square and PayPal
vcita supports multiple external payment processors.
Its current payment setup documentation lists Stripe, Square and PayPal and notes that the processor’s own pricing and settlement rules apply.
For example, vcita currently describes typical timing as:
- Stripe: commonly 1–2 business days for bank deposits;
- Square: generally next-business-day processing for qualifying transactions made before midnight;
- PayPal: standard or instant transfer options according to PayPal’s rules.
Those are processor-level payout mechanics.
Changing the processor or payout bank therefore is not necessarily the same operation as changing an invoice setting inside vcita.
Payments by vcita and Payouts
vcita also documents an integrated payments environment in which businesses can inspect transaction and payout status.
Transaction states include concepts such as:
- Approved;
- Captured;
- Failed;
- Settled.
Payout states include:
- Requested;
- Processing;
- Processed;
- Failed;
- Denied;
- Returned.
That distinction is useful when a customer has paid but the business does not yet see the funds in its bank account.
A transaction can complete before the associated payout completes.
ACH Bank Payments
For U.S. businesses, vcita also supports ACH under qualifying payment-provider configurations.
vcita says bank payments require Stripe or Payments by vcita and warns that ACH can remain pending for several business days before settlement and deposit.
ACH should therefore not be troubleshot like an instant card transaction.
The slower processing timeline is part of the payment method.
Recurring and Automated Billing
Businesses with ongoing clients can use several automation models.
vcita supports automated billing that can:
- create draft invoices;
- automatically send invoices;
- automatically send payment links.
It also supports recurring and scheduled card payments, including repeated charges and future one-time charges.
Those are related but different tools.
Automated invoicing creates or sends requests for payment.
Recurring payment arrangements can actually schedule charges.
Packages
vcita packages connect advance purchases with future appointments.
A business can bundle services, allow clients to purchase package credits and later apply those credits when booking qualifying appointments.
Packages therefore sit between billing and scheduling.
They are not merely discounts.
Website Widgets and Direct Links
vcita can extend its workflow outside the Client Portal.
Current documentation describes:
- scheduling widgets;
- contact forms;
- pop-ups;
- sidebars;
- direct booking links;
- payment links.
A business can therefore place vcita actions directly into an existing website instead of requiring visitors to begin from a vcita-hosted page.
Start With the Problem You Are Solving
Need clients to book online?
Read the vcita online scheduling guide.
Need a client-facing account area?
Read the vcita Client Portal guide.
Need to invoice and collect payment?
Read the invoice-to-payment workflow.
Customer paid but money is not in the bank?
Read the transactions-and-payouts guide.
Need to understand Stripe, Square or PayPal?
Read the payment-processor comparison.
Need U.S. bank payments?
Read the ACH workflow.
Need subscription-like billing?
Read the recurring and automated billing guide.
Need clients to prepay for multiple services?
Read the packages guide.
Independent Publication
vcita Workflow Guide is an independent editorial resource.
It is not operated by vcita and does not process payments, modify bank accounts, access client records or recover vcita accounts.
Never submit a vcita password, payment-provider credentials, bank login, card number or MFA code to an independent informational website.