Business profile
Show company information, ownership review, authorized users, missing documents, and KYB refresh requirements.
Dashboard / Client Portal Preview
A client portal concept for payment status, review tasks, and reports.
The portal preview shows how business customers could track KYB status, payment instructions, compliance requests, reporting exports, and support cases after the backend and permission model are confirmed.
This is a product preview only. Displayed balances, payment activity, reports, review states, and permissions are illustrative and must be connected to approved backend logic.
Client portalAcme Global Trading LLC
PreviewKYB statusReviewAdditional information may be required
Payment instructions12Illustrative sample only
Pending actions4Documents, approvals, or review replies
Reports3Available for download preview
KYB refreshinformation_requiredBeneficial owner address evidence requested
Supplier payoutpending_reviewPayment purpose and invoice context under review
Contractor batchapprovedDual approval completed
Reconciliation exportavailableJune operating report ready
Support requestopenCustomer support reviewing document upload issue
Portal modules
Make the customer workspace operational, not just informational.
The portal should help businesses understand what needs action, what is under review, what has changed, and what can be exported for finance or audit workflows.
Payment instructions
Track draft, pending review, approved, processing, failed, rejected, and completed payment instructions.
Review center
Surface compliance requests, risk alerts, payment-purpose questions, and transaction-monitoring exceptions.
Reports
Prepare reconciliation exports, payment records, audit trails, review notes, and operational summaries.
Team access
Preview maker-checker workflows, user roles, approval ownership, and permission boundaries.
Support cases
Route account questions, document requests, payment exceptions, complaints, and service feedback.
Action center
Customers should see what is actionable, not only what is pending.
A useful portal turns review states into clear next steps: upload a document, answer a payment-purpose question, approve a batch, download a report, or contact support.
Document request
Show required document, reason, due context, and upload action.
Payment review
Explain whether the case needs customer action, analyst review, or partner processing.
Approval queue
Separate maker, checker, and admin responsibilities before instructions proceed.
Report available
Notify finance teams when reconciliation or audit exports are ready.
Roles and permissions
Portal access should reflect financial workflow responsibility.
Role design matters in payment products because accidental access, single-person approval, and unclear accountability can create operational and compliance risk.
Manage business profile, users, approvals, and support escalation.
Create payment instructions, view reporting, and prepare reconciliation exports.
Review payment instructions, approve batches, and respond to exception requests.
Read-only access for records, status tracking, and internal audit support.
Portal guardrails
Keep the preview credible without implying production readiness.
Until backend, authentication, reporting, banking, and support workflows are confirmed, the dashboard should be treated as a UX/product direction, not a live client portal.
Portal balances, payment amounts, and activity counts are preview data only.
Final portal behavior should align with backend implementation, compliance policy, and customer agreements.
Dashboard access should require approved onboarding, role permissions, MFA, and audit logging.
Final portal behavior should align with backend implementation, compliance policy, and customer agreements.
Payment status does not guarantee final settlement, delivery, or acceptance by partners.
Final portal behavior should align with backend implementation, compliance policy, and customer agreements.
Customer actions should be logged for compliance, support, dispute handling, and internal audit.
Final portal behavior should align with backend implementation, compliance policy, and customer agreements.
Product next step
Discuss portal scopeUse this portal preview to define the first authenticated product scope.
The next implementation decision is which modules become MVP: KYB status, payment instructions, document requests, reports, team roles, or support cases.