Designed-In Controls
Controls are being designed as part of the core transaction path, so screening and policy checks are structural rather than optional add-ons.
PLATFORM
06 / Build & Trust
Compliance & Risk
Controls designed into the operating model from day one. Railix Inc. is a FinCEN-registered Money Services Business (see section 05); aside from that registration, nothing below represents any license, certification, audit, or supervision. Everything else describes how Railix is designing for compliance and risk.
Foundational Layer
01 / Architecture
How We Are Designing Compliance As Architecture
We are designing controls at the protocol layer rather than bolting them on after the fact. The intent is that compliance is a property of how the system works, not a checklist applied at the edges.
Evidence By Default
The system is being designed so that every material action produces evidence automatically, rather than requiring evidence to be assembled after the fact.
Escalation Paths
We are designing explicit escalation paths so that holds, reviews, and exceptions route to human decision-makers with full context.
02 / Identity
How We Are Designing For Identity & Counterparty Risk
The following describe intended approaches to identity and counterparty risk. They are design directions under construction, not services that are operational, approved, or certified today.
- Customer Identity Verification Design
- A design approach for verifying individual customer identity as part of onboarding and ongoing review.
- Business (KYB) Verification Design
- A design approach for verifying business entities, including registration and structure data.
- Beneficial Ownership Data Model
- A data model designed to capture and maintain beneficial ownership information where applicable.
- Risk Profiling & Scoring Approach
- An approach for profiling and scoring risk to inform review intensity and control decisions.
- Ongoing Review Cadence Intent
- An intended cadence for periodic re-review so risk assessments are refreshed rather than static.
03 / Monitoring
How We Are Designing Screening & Monitoring
Screening and monitoring are being designed as an explicit, auditable pipeline. The steps below describe intended control design and do not represent capabilities that are live or independently validated.
- 01
Pre-Transaction Screening
Instructions are designed to be screened before value moves, so risk decisions happen ahead of settlement.
- 02
Sanctions & Watchlist Checks (Design)
A design for evaluating parties against sanctions and watchlist signals as part of screening.
- 03
Behavioral Monitoring
An intended capability to monitor patterns over time and surface behavior that warrants attention.
- 04
Alert Generation
A design for generating structured alerts when screening or monitoring criteria are met.
- 05
Human Review
Alerts are designed to route to human reviewers with the context needed to make a decision.
- 06
Documented Disposition
Each review is designed to conclude with a recorded disposition and rationale.
False positives are an expected part of any screening design. The intent is to tune thresholds over time and to preserve a complete audit trail of every alert, review, and disposition for later reconstruction.
04 / Recordkeeping
How We Are Designing For Recordkeeping & Audit Readiness
We are designing the platform so that audit readiness is a byproduct of normal operation. The following are design intentions, not attained audit outcomes or approvals.
Immutable Event History
An append-only event history is being designed so records cannot be silently altered after the fact.
Point-In-Time Reconstruction
The intent is to reconstruct system and account state as of any historical moment for review.
Structured Case Records
Reviews and exceptions are designed to produce structured case records rather than free-form notes.
Reporting-Ready Data Model
A data model designed so reporting can be produced from primary records rather than reconstructed manually.
Policy & Procedure Documentation
An intent to maintain versioned policy and procedure documentation alongside the controls they describe.
05 / Regulatory
Regulatory Posture
Railix Inc. is registered with the Financial Crimes Enforcement Network (FinCEN) as a Money Services Business. FinCEN registration is a federal reporting and recordkeeping obligation under the Bank Secrecy Act. It is not a license, endorsement, or approval by FinCEN or any other government agency, and it does not itself authorize money transmission. Railix Inc. is organized in Montana, which does not maintain a money transmitter licensing regime; the staged rollout is designed so that any state-level authorizations required for a given product and jurisdiction are secured before that product is offered there. The BSA/AML program components below are labelled by build status — some are built, others are still in build. No independent review of the program has occurred.
FinCEN MSB Registration Number — 31000321940589
- Built
AML Policy
A written BSA/AML policy governing the program and its controls.
- Built
Designated Compliance Officer
A named individual accountable for the BSA/AML program.
- In Build
KYC / KYB
Identity verification for individual customers and business entities as part of onboarding and review.
- In Build
Sanctions & Watchlist Screening
Evaluation of parties against sanctions and watchlist signals within the screening pipeline.
- In Build
Transaction Monitoring
Monitoring of activity over time to surface patterns that warrant review.
- In Build
SAR / CTR Readiness
Design work toward the ability to produce required reports from primary records.
- In Build
Recordkeeping
An append-only record model designed for retention and point-in-time reconstruction.
- In Build
Independent Review
An independent review of the program is planned; none has been performed to date.
- In Build
Training
A recurring BSA/AML training program for relevant personnel.
A Compliance Model Under Construction
Railix is pre-launch. Aside from the FinCEN MSB registration noted above, these describe a compliance operating model under construction and do not represent a license, approval, certification, or completed independent review.