Use case intake
Confirm paying entity, recipient types, business purpose, expected countries, currencies, volume, and reporting needs.
Onboarding & KYB Flow
A clear business review path before payment access expands.
OrbitLink Pay should make customer onboarding predictable without implying automatic approval. The KYB flow explains what businesses need to provide, how review states work, and which boundaries may affect access.
KYB/KYC review, sanctions screening, risk rating, transaction monitoring, and partner requirements may apply before any payment workflow is enabled or expanded.
Onboarding caseKYB review
ReviewBusiness profileSubmittedEntity details received
OwnershipPendingBeneficial owner review
Use caseReviewPayment purpose check
ActivationTBDSubject to approval
Company recordsSubmittedRegistration evidence
Controller IDRequiredAuthorized user check
Sanctions screenReviewRisk workflow
Payment accessPendingApproval required
Review flow
Separate customer onboarding from payment activation.
This helps customers understand that submitting information is the start of review, not a guarantee of access, settlement timing, or supported payment coverage.
Business profile
Collect company details, registration information, operating address, website, ownership structure, and authorized representatives.
KYB/KYC review
Review business documents, beneficial owners, controllers, sanctions exposure, adverse media signals, and risk profile.
Payment workflow review
Evaluate intended payment flows, counterparties, purpose of payments, supporting documents, and monitoring requirements.
Activation decision
Approve, request more information, restrict, reject, or keep the case under review based on compliance and partner requirements.
Ongoing monitoring
Refresh documents, monitor transaction activity, review exceptions, and reassess risk throughout the customer relationship.
Information requirements
Make required information clear before the customer starts.
A clear checklist reduces back-and-forth, improves conversion quality, and gives compliance teams better information for review.
Company profile
Legal name, registration number, registered address, operating address, business activity, website, and expected payment use case.
Ownership and control
Beneficial owners, control persons, authorized users, ownership percentages, and supporting identity documents where required.
Payment purpose
Recipient types, countries, currencies, estimated volume, payment reasons, invoice or contract context, and source-of-funds information.
Supporting documents
Business registration documents, ownership records, tax or address evidence, contracts, invoices, and additional risk review materials.
Compliance screening
Sanctions, watchlist, politically exposed person, adverse media, fraud, AML, and internal risk checks may apply.
Ongoing review
Customer information and transaction activity may be refreshed or reviewed periodically based on risk, volume, or partner requirements.
Review statuses
Status labels should tell customers what happens next.
These labels can later map to product UI, support workflows, backend states, and customer notifications.
Customer or sales team is preparing the onboarding request.
Business profile and initial documents have been submitted for review.
Compliance, risk, and operations checks are in progress.
Additional documents, ownership details, or payment-purpose information is required.
The customer has passed the applicable review for the approved workflow.
Access is limited by risk, region, use case, partner, or compliance requirements.
The use case or customer profile cannot be supported under current requirements.
Periodic review or updated documentation is required before access continues or expands.
Risk controls
Approval should be risk-based and scoped to actual readiness.
For payment businesses, onboarding is not only a registration form. It is a control layer that protects customers, banking partners, and the platform.
KYB/KYC review should be completed before payment workflow access expands.
Final workflow behavior should be aligned with compliance policy, partner requirements, and backend implementation.
Risk rating should consider industry, ownership, geography, counterparties, volume, and payment purpose.
Final workflow behavior should be aligned with compliance policy, partner requirements, and backend implementation.
Approval does not guarantee every future payment instruction will be accepted or completed.
Final workflow behavior should be aligned with compliance policy, partner requirements, and backend implementation.
Supported regions, rails, limits, timelines, and product scope remain subject to partner and compliance review.
Final workflow behavior should be aligned with compliance policy, partner requirements, and backend implementation.
Not suitable without review
Make unsupported or high-risk cases explicit early.
Clear boundaries reduce sales ambiguity and help the team avoid committing to unsupported regions, rails, custody models, or prohibited activities.
Countries, currencies, rails, or counterparties that have not been confirmed by compliance and partners.
Missing ownership details, unclear payment purpose, inconsistent business records, or unresolved risk questions.
Use cases that violate applicable law, sanctions, AML requirements, partner rules, or internal policies.
Requests that require escrow, deposit-taking, FDIC-protected custody, or bank services that are not formally available.
Review readiness
Start onboarding reviewStart onboarding with business context, not only documents.
The most useful first submission includes who is paying, who is receiving funds, why payments are made, expected activity, and the documents needed to support review.