A client portal is not only about receiving orders. A business also needs a clean way to request money, confirm payment, and deliver final files without manual confusion.
KorpKit connects orders, invoices, payments, and final delivery so the business can see what has been requested, what is unpaid, what is paid, and what can be released.
This reduces the need for manual payment screenshots, repeated reminders, and messy file delivery conversations.
An invoice is the payment request sent to a client. It can include the order amount, invoice details, payment status, and payment action.
Admins can use invoices to charge clients after a quote is approved, after an order is priced, before work starts, or before final files are released depending on the tenant workflow.
Invoices help the business keep accounting and client communication organized inside the portal.
A payment link gives the client a direct way to pay an invoice. The client opens the invoice or payment page and pays through the enabled payment method.
Available payment methods depend on tenant settings, connected gateways, country support, and package rules.
Payment links are useful because clients do not need long instructions. They click, review the amount, and pay.
Some businesses use manual payment methods such as account transfer. In that case, the client may pay outside the card processor and the admin may manually confirm or mark the invoice paid.
Manual payment is useful in regions where card processors are not always the best option, but it needs careful admin review.
The business should avoid releasing final files until the manual payment is confirmed.
AutoPay means the system can charge a saved payment method automatically when a payment condition is met. This is an advanced workflow and should be package-controlled.
Saved-card style flows reduce friction for repeat clients because they do not need to manually pay every invoice.
Because automatic charging affects client money, it should be clear, permission-based, and limited to packages and gateways that support it properly.
Partial payment means the client can pay part of the invoice first and the remaining amount later. This is useful for advance payment, milestone payment, or split payment workflows.
For example, a business may request 50% before starting and 50% before final files are released.
Partial payments should clearly show paid amount, remaining amount, and what the client must pay before the next workflow step.
Final-file unlock rules connect payment status to delivery. If the invoice is unpaid, the final files can remain locked. Once payment is complete, the client can download the final files.
This protects the business from delivering completed work before receiving the required payment.
Unlock rules are especially important for digital service businesses where files are the final product.
Orders create work. Invoices request payment. Payment links help clients pay. AutoPay can automate repeat payments. Partial payments support split payments. Unlock rules protect final files.
The tenant package decides how advanced the payment workflow can be.
A good payment setup makes the portal easier for clients and safer for the business.
Start free, set up your services, and give clients a cleaner way to order, pay, upload files, and track work.
