1. Purpose and Scope
This Risk Assessment Framework ("Framework") establishes how NezenX identifies, assesses, monitors, and mitigates risks across its operations. The Framework provides a structured methodology for evaluating risks at the client, transaction, geographic, and enterprise levels.
This Framework supports and is informed by the AML/KYC/KYB Policy, the Sanctions and OFAC Compliance Policy, and the Terms of Service. Where those policies establish specific risk-based controls (such as Enhanced Due Diligence triggers or geographic risk tiers), this Framework provides the overarching methodology.
This Framework applies to all NezenX operations, personnel, and business relationships.
Current state: NezenX's risk assessment processes are currently performed through manual review and judgment by the operations team and senior management. NezenX is working toward implementing structured risk scoring tools and automated monitoring. This Framework describes both current practices and intended standards as the program matures.
2. Risk Categories
NezenX assesses risk across the following categories:
2.1. Client and Counterparty Risk
The risk that a User or its associated parties (Beneficial Owners, Authorized Users) may use the Platform for money laundering, terrorist financing, fraud, sanctions evasion, or other illicit purposes.
Risk factors assessed:
- jurisdiction of incorporation and operation;
- ownership structure complexity and transparency;
- nature of business and consistency with Platform use case;
- expected transaction volume relative to business size;
- source of funds (USDT origin and history);
- adverse media, negative information, or law enforcement connections;
- PEP (Politically Exposed Person) status of Beneficial Owners;
- responsiveness and cooperation during onboarding and ongoing verification.
2.2. Geographic Risk
The risk associated with the jurisdictions in which Users are incorporated, operate, or transact. Geographic risk is assessed using the tiered framework established in the Sanctions and OFAC Compliance Policy Section 7:
Prohibited
OFAC comprehensively sanctioned (Cuba, Iran, DPRK, Syria, Crimea/Donetsk/Luhansk)
Services blocked
High Risk
FATF High-Risk + sectoral sanctions jurisdictions
EDD required, senior management approval
Elevated
FATF Increased Monitoring list
Standard + additional documentation
Standard
All other jurisdictions
Standard onboarding
Tier | Examples | Treatment |
|---|---|---|
Prohibited | OFAC comprehensively sanctioned (Cuba, Iran, DPRK, Syria, Crimea/Donetsk/Luhansk) | Services blocked |
High Risk | FATF High-Risk + sectoral sanctions jurisdictions | EDD required, senior management approval |
Elevated | FATF Increased Monitoring list | Standard + additional documentation |
Standard | All other jurisdictions | Standard onboarding |
2.3. Product and Service Risk
The risk inherent in the specific products and services NezenX offers:
- USDT funding — cryptocurrency deposits carry higher risk of anonymity, cross-border movement, and potential sanctions evasion compared to traditional banking channels;
- Virtual Cards for advertising — digital advertising spend is generally lower risk (identifiable merchants, recurring patterns), but card misuse for non-advertising purposes increases risk;
- Multi-card issuance — Users with large numbers of Virtual Cards may present higher risk of card testing, velocity abuse, or unauthorized third-party usage;
- Credit product model — the credit-based card product creates refund and chargeback complexity that may be exploited.
2.4. Transaction Risk
The risk that individual transactions or transaction patterns indicate financial crime, fraud, or policy violation:
- transaction volume inconsistent with stated business profile;
- rapid deposit-and-spend cycles (potential layering);
- deposits structured below reporting thresholds (potential structuring);
- transactions at prohibited or inconsistent MCCs;
- deposits from multiple unrelated wallet addresses;
- excessive chargeback or decline rates.
Transaction risk indicators are detailed in the AML/KYC/KYB Policy Section 6 (Transaction Review) and Section 14 (Red Flags).
2.5. Regulatory and Compliance Risk
The risk arising from non-compliance with applicable laws and regulations:
- FinCEN MSB registration and BSA/AML program requirements;
- state money transmitter licensing obligations;
- GENIUS Act requirements for stablecoin-related businesses;
- PDPA (Singapore) data protection obligations;
- card network rules and Card Issuing Partner requirements;
- sanctions and export control regulations.
NezenX's current compliance gaps are tracked in internal documentation and are being addressed through the compliance program build-out.
2.6. Operational Risk
The risk of loss or disruption from inadequate or failed internal processes, people, or systems:
- Technology risk — Platform downtime, security vulnerabilities, data breaches, API failures;
- People risk — key person dependency, insufficient training, human error in manual processes;
- Process risk — gaps in onboarding procedures, treasury operations, reconciliation;
- Third-party risk — dependency on third-party service providers, including Card Issuing Partners, cloud infrastructure, and communication tools.
2.7. Financial Risk
The risk of financial loss to NezenX or its Users:
- Revenue concentration — revenue concentration in partnership arrangements, which may be affected by changes in partner terms or market conditions;
- Funding arrangement complexity — funding arrangement complexity between operational entities, which creates reconciliation requirements and financial exposure;
- USDT volatility — while USDT is pegged 1:1 to USD, de-peg events could create losses;
- Client concentration — excessive revenue dependency on a small number of high-volume clients.
3. Risk Scoring Methodology
NezenX assesses risk using a simplified scoring approach across two dimensions:
Likelihood — the probability that the risk will materialize:
1
Low
Unlikely to occur under normal circumstances
2
Medium
May occur occasionally or under certain conditions
3
High
Likely to occur regularly or has already occurred
Score | Level | Description |
|---|---|---|
1 | Low | Unlikely to occur under normal circumstances |
2 | Medium | May occur occasionally or under certain conditions |
3 | High | Likely to occur regularly or has already occurred |
Impact — the severity of consequences if the risk materializes:
1
Low
Minor operational disruption, no regulatory or financial consequence
2
Medium
Significant operational impact, potential regulatory inquiry, moderate financial loss
3
High
Severe business disruption, regulatory enforcement, significant financial loss, or criminal liability
Score | Level | Description |
|---|---|---|
1 | Low | Minor operational disruption, no regulatory or financial consequence |
2 | Medium | Significant operational impact, potential regulatory inquiry, moderate financial loss |
3 | High | Severe business disruption, regulatory enforcement, significant financial loss, or criminal liability |
Risk rating is determined by multiplying Likelihood × Impact:
Low
1-2
Accept and monitor. Review annually.
Medium
3-4
Mitigate with controls. Review quarterly.
High
6-9
Immediate action required. Escalate to senior management. Review monthly or as needed.
Rating | Score | Response |
|---|---|---|
Low | 1-2 | Accept and monitor. Review annually. |
Medium | 3-4 | Mitigate with controls. Review quarterly. |
High | 6-9 | Immediate action required. Escalate to senior management. Review monthly or as needed. |
At the current stage of operations, risk scoring is applied qualitatively by the operations team and senior management during onboarding review and periodic assessment. As the compliance program matures, NezenX intends to implement structured scoring tools that assign quantitative risk scores to each client and transaction.
4. Client Risk Assessment
4.1. At onboarding
Every new User undergoes a risk assessment during the onboarding process. The assessment considers all client risk factors listed in Section 2.1 and the geographic risk tier (Section 2.2) to determine the overall client risk rating.
4.2. Risk-based onboarding
Low
Standard KYB verification (AML Policy Section 3.2)
Operations team
Medium
Standard KYB + additional documentation (source of funds, business justification)
Operations team with senior management review
High
Enhanced Due Diligence (AML Policy Section 4)
Senior management approval required
Client Risk Rating | Onboarding Requirements | Approval Authority |
|---|---|---|
Low | Standard KYB verification (AML Policy Section 3.2) | Operations team |
Medium | Standard KYB + additional documentation (source of funds, business justification) | Operations team with senior management review |
High | Enhanced Due Diligence (AML Policy Section 4) | Senior management approval required |
4.3. Ongoing risk reassessment
Client risk ratings are reassessed:
- when material changes to client information are reported or identified (e.g., ownership change, jurisdiction change);
- when transaction patterns deviate significantly from the client's established profile;
- when adverse media or negative information about the client is identified;
- when sanctions lists are updated and the client's profile may be affected;
- at minimum, on an annual basis as part of periodic account review.
4.4. Risk rating changes
If a reassessment results in a higher risk rating, NezenX will apply the controls appropriate to the new rating. If concerns cannot be resolved through Enhanced Due Diligence, NezenX may terminate the business relationship.
5. Enterprise Risk Assessment
NezenX conducts an enterprise-level risk assessment covering all risk categories in Section 2 on an annual basis (or more frequently if material changes occur).
The enterprise risk assessment evaluates:
- changes in the regulatory environment (new laws, enforcement actions, guidance);
- changes in the business model, product offerings, or client base;
- emerging risks in the cryptocurrency and fintech sectors;
- effectiveness of existing controls and policies;
- findings from internal reviews, external audits (when conducted), and incident reports;
- changes in the threat landscape (new fraud typologies, sanctions developments, technology vulnerabilities).
The enterprise risk assessment is conducted by senior management (or the Compliance Officer when appointed) and documented in an internal risk assessment report.
Current practice. The enterprise risk assessment is currently performed informally through ongoing monitoring of regulatory developments, industry events, and operational experience. NezenX is working toward formalizing this into a structured annual review process.
6. Risk Mitigation and Controls
For each identified risk, NezenX applies one or more of the following mitigation strategies:
- Avoid — decline the business relationship, exit the jurisdiction, or discontinue the product feature that creates the risk;
- Mitigate — implement controls to reduce the likelihood or impact (e.g., EDD, transaction limits, screening, monitoring);
- Transfer — shift the risk to a third party through contractual arrangements (e.g., Card Issuing Partner liability, insurance);
- Accept — acknowledge the risk where it falls within NezenX's risk appetite and the cost of mitigation exceeds the expected loss. Accepted risks are documented and monitored.
Existing controls by risk category:
Client/Counterparty
KYB verification, manual SDN screening, EDD for high-risk clients
Geographic
Prohibited jurisdiction list, risk tier framework (P8 Section 7)
Product/Service
USDT network restrictions, deposit review, card spend controls
Transaction
Manual transaction review, red flags awareness, MCC restrictions
Regulatory
Policy rebuild program (in progress), compliance consulting outreach, legal counsel search
Operational
Daily balance monitoring, dual verification for treasury ops, Telegram group oversight
Financial
Cashback rate monitoring, daily reconciliation (in progress), funding arrangement monitoring
Risk Category | Current Controls |
|---|---|
Client/Counterparty | KYB verification, manual SDN screening, EDD for high-risk clients |
Geographic | Prohibited jurisdiction list, risk tier framework (P8 Section 7) |
Product/Service | USDT network restrictions, deposit review, card spend controls |
Transaction | Manual transaction review, red flags awareness, MCC restrictions |
Regulatory | Policy rebuild program (in progress), compliance consulting outreach, legal counsel search |
Operational | Daily balance monitoring, dual verification for treasury ops, Telegram group oversight |
Financial | Cashback rate monitoring, daily reconciliation (in progress), funding arrangement monitoring |
7. Risk Appetite
NezenX has zero tolerance for:
- knowingly facilitating money laundering, terrorist financing, or sanctions evasion;
- providing Services to persons or entities on applicable sanctions lists;
- processing transactions that NezenX knows to involve proceeds of crime;
- deliberately misleading regulators, Card Issuing Partners, or card networks.
NezenX has low tolerance for:
- clients that refuse to cooperate with verification or compliance requests;
- transaction patterns that exhibit clear indicators of structuring, layering, or fraud;
- operations in jurisdictions designated as high-risk by FATF or OFAC.
NezenX accepts managed risk in:
- onboarding clients that fund exclusively via USDT, subject to appropriate verification;
- operating during the compliance program build-out period, with active steps to close gaps;
- relying on manual processes while automated tools are evaluated and implemented.
8. Reporting and Escalation
Risk-related matters are escalated as follows:
Routine onboarding risk assessment
Operations team reviews and approves
Medium-risk client or unusual activity
Operations team escalates to senior management
High-risk client, sanctions concern, or suspicious activity
Immediate escalation to senior management (or Compliance Officer when appointed)
Regulatory inquiry or enforcement action
Senior management + legal counsel (when engaged)
Data breach or security incident
Per the Incident Response Policy
Matter | Escalation Path |
|---|---|
Routine onboarding risk assessment | Operations team reviews and approves |
Medium-risk client or unusual activity | Operations team escalates to senior management |
High-risk client, sanctions concern, or suspicious activity | Immediate escalation to senior management (or Compliance Officer when appointed) |
Regulatory inquiry or enforcement action | Senior management + legal counsel (when engaged) |
Data breach or security incident | Per the Incident Response Policy |
Senior management reviews risk-related escalations and documents decisions and rationale.
9. Record Keeping
NezenX maintains records of risk assessments, including:
- client risk assessments conducted at onboarding and during periodic reviews;
- enterprise risk assessment reports;
- escalation decisions and rationale;
- risk mitigation actions taken;
- changes to risk ratings and the reasons for such changes.
Risk assessment records are retained in accordance with the Data Retention Policy (minimum five (5) years).
10. Review and Updates
This Framework is reviewed at least annually and updated to reflect changes in NezenX's business model, risk profile, regulatory environment, or operational capabilities.
Material changes will be communicated to affected personnel and, where relevant, to Users through Policy updates.
11. Amendments
NezenX may update this Framework at any time. Material changes will be communicated to Users via email and/or Platform notification at least thirty (30) days prior to the effective date.
Continued use of the Platform after the effective date of an amendment constitutes acceptance of the updated Framework.
12. Contact
For questions about this Framework:
- General complaints: [email protected]
- Formal complaints: [email protected]
- Escalation: [email protected] (subject line: "Complaint Escalation — [Reference Number]")