Business onboarding
Collect company profiles, ownership details, expected activity, and supporting documents before any payment workflow is enabled.
Platform
A compliance-first platform for USD cross-border payment operations.
Structure USD payment operations around onboarding, compliance review, transaction monitoring, and audit-ready reporting while banking and custody arrangements continue through formal review.
MSB registration is a compliance foundation, not a banking charter. OrbitLink Pay is not a bank, and this page avoids unsupported custody, coverage, fee, or settlement claims.
Operations consoleUSD payment review
SandboxPending reviews18KYB and transaction checks
Payment instructions$428.6KAwaiting approval
Risk flags6Require analyst review
Vendor payoutReviewKYB refresh
Contractor batchApprovedDual approval
Supplier wireExceptionPurpose mismatch
Platform capabilities
Clear product primitives without overstating what is live.
The page should give customers and reviewers a concrete product model while leaving room for confirmed partner, backend, and legal details to be added later.
USD payment workflows
Design payment instructions, approval steps, and operational status tracking without promising unconfirmed coverage or settlement timing.
Compliance review
Route customers and transactions through AML, KYC, KYB, sanctions screening, and risk review checkpoints.
Transaction monitoring
Surface risk flags, pending reviews, failed instructions, and exception states for operations and compliance teams.
Reporting exports
Prepare reconciliation-ready records, audit trails, review notes, and operational exports for finance workflows.
Integration-ready architecture
Keep the product model ready for future APIs, webhooks, and partner integrations after backend scope is confirmed.
How it works
Make the operational path easy to understand before funds move.
A payment platform page should show the sequence of onboarding, review, payment instruction, monitoring, and reporting. This reduces ambiguity for clients, banks, and internal teams.
Business profile submitted
Company, ownership, expected payment activity, and use case information are collected for review.
KYB/KYC and risk review
Identity, business, sanctions, and transaction-risk checks are evaluated before access expands.
Payment instruction created
Users prepare USD payment instructions with approval, recipient, and purpose details.
Status and reporting tracked
Operations teams monitor pending reviews, failed instructions, audit logs, and reconciliation exports.
Compliance controls
Trust comes from controls, disclosure, and review workflows.
This section is intentionally conservative. It describes expected control layers without claiming final certifications, banking coverage, or custody mechanics that are still under review.
FinCEN and FINTRAC MSB registration disclosure with conservative wording
Final wording should be matched to actual policies, evidence, partner agreements, and legal review before production launch.
Not-a-bank boundary and banking relationship status clearly separated
Final wording should be matched to actual policies, evidence, partner agreements, and legal review before production launch.
Role-based permissions and maker-checker approval flows
Final wording should be matched to actual policies, evidence, partner agreements, and legal review before production launch.
KYC/KYB, risk rating, sanctions screening, transaction monitoring, and exception review
Final wording should be matched to actual policies, evidence, partner agreements, and legal review before production launch.
Internal compliance audits, team training, and audit logs for customer, payment, and review actions
Final wording should be matched to actual policies, evidence, partner agreements, and legal review before production launch.
Integration-ready
Dashboard-first now, API-ready as backend scope matures.
Mature payment products usually need dashboards, exports, APIs, and webhooks. OrbitLink Pay can present the architecture now while waiting to publish concrete API specifications after backend work begins.
POST /payment-instructions
GET /reviews/pending
WEBHOOK payment.review_required
EXPORT reconciliation.csv
Product boundaries
What the page should not overclaim yet.
These boundary cards make the product page safer for review while formal materials are still being checked by legal and partner teams.
Do not name a bank or imply custody is complete until agreements are formally executed.
Avoid country lists until business, compliance, and partner coverage are validated.
Avoid fixed pricing, instant settlement, or guaranteed delivery language.
Describe APIs and webhooks as integration-ready architecture until backend is implemented.
Platform review next step