vcita is most useful when it is understood as a connected workflow rather than a collection of unrelated tools.
A client can schedule an appointment, appear in the business’s client records, receive communications, access the Client Portal, review an invoice and make a payment through connected payment infrastructure.
The platform’s current Help Center separates these capabilities into areas such as scheduling, clients, payments and business tools, while the Client Portal presents several of them together to the client.
Step 1: Define the Service
Before clients can book, the business creates or configures the services it offers.
vcita’s service menu can control:
- service name and description;
- pricing;
- payment timing;
- staff availability;
- booking presentation.
For paid services, businesses can decide whether payment is collected during booking or later.
This setting matters downstream.
A service configured for later payment should not be expected to behave like a prepaid appointment.
Step 2: Make the Service Bookable
Businesses can enable online scheduling through their Client Portal and establish booking rules and limits.
Clients can then select the relevant service and available time according to those rules.
The booking event becomes part of the client’s relationship with the business.
Step 3: Maintain the Client Record
vcita’s client-management area keeps client information and activity together.
Current documentation describes a client conversation view containing interactions such as:
- notes;
- bookings;
- payments;
- documents.
That makes the client record the connecting layer between scheduling and billing.
Step 4: Invoice or Request Payment
The business can issue an invoice when money is due.
vcita also allows direct payment links, which can be shared independently of a full invoice.
These are related but distinct tools.
An invoice creates a billing document.
A payment link creates a payment path.
Step 5: The Client Pays
Clients can pay through the Client Portal by selecting an unpaid item and proceeding to payment.
At this stage, the configured payment provider becomes important.
vcita can connect businesses with processors such as:
- Stripe;
- Square;
- PayPal.
Some accounts may also use vcita’s integrated payments offering.
Step 6: Transaction Processing
The processor evaluates and processes the transaction.
This is where payment status becomes important.
In vcita’s integrated transaction reporting, a transaction may move through states such as approved, captured and settled.
A client seeing a successful checkout does not necessarily mean the associated payout has already reached the business’s bank.
Step 7: Payout
After settlement, funds enter the payout layer.
For vcita’s integrated payments environment, payout statuses can include:
- Requested;
- Processing;
- Processed;
- Failed;
- Denied;
- Returned.
This is the stage most relevant when the question is:
“Where is the money going?”
rather than:
“Did the customer successfully pay?”
Why This System Map Matters
Many support problems are really classification problems.
Client cannot find an available appointment
Scheduling issue.
Invoice shows wrong amount
Billing issue.
Payment attempt failed
Transaction/processor issue.
Payment succeeded but bank deposit is missing
Settlement or payout issue.
Client cannot see invoices or bookings
Client Portal/access issue.
Treating all five as “vcita payment problems” makes troubleshooting slower.
Processor Boundaries
When Stripe, Square or PayPal is connected, some important payment behavior is controlled outside vcita.
vcita currently tells users to review the processor’s own pricing and terms and provides general payout timing information for each provider.
Therefore, a business changing its payout bank may need to work through the connected provider rather than simply editing an invoice configuration.
Client Portal as the Customer Layer
The Client Portal is where the connected architecture becomes visible to customers.
Clients can use it to:
- book;
- pay;
- download financial documents;
- send files;
- contact the business.
For that reason, changes to the business’s scheduling and billing configuration can affect what clients see there.
The Simplest Mental Model
Think of vcita in four layers:
Client interaction
Booking, messaging, portal.
Business administration
Client records, services, invoices.
Payment transaction
Stripe, Square, PayPal or integrated processing.
Payout
Movement of settled funds to the designated bank destination.
Once those layers are separated, most vcita workflows become much easier to understand.
Internal Link Suggestions:
/vcita-client-portal//vcita-invoices-payments//vcita-payment-processors//vcita-transactions-payouts/