Eligibility

A practical summary of who KRYPVAULT plans to onboard first, what is likely to remain out of scope, and how partner policy controls the final customer promise.

A more visual way to explain who fits the launch and who does not

Eligibility is where provider conversations often harden. This page is designed to make that part easier to scan by separating customer logic, exclusions, and approval controls into a format that feels closer to an internal review deck than a plain memo.

KYC / KYB

Entry always depends on full onboarding and screening

Partner Policy

Provider rules stay above internal commercial preference

Phased Rollout

Country and feature access stay conditional by programme

Eligibility and onboarding review

Eligibility and exclusions

This page is intended for provider, compliance, and onboarding review. It describes KRYPVAULT's current target-customer logic in a realistic way, but every final decision remains subordinate to partner licences, programme rules, and legal review.

Who KRYPVAULT intends to serve first

  • Selected low-risk individuals with legitimate cross-border income, operating needs, or supplier payment requirements
  • Selected low-risk businesses with clear ownership, documentation-ready activity, and understandable money flows
  • Customers in jurisdictions where partner programmes, legal analysis, and operational support all align
  • Use cases that fit straightforward multi-currency accounts, FX conversion, cards, invoicing, and payment workflows

Typical in-scope examples

  • Consultants, agencies, software firms, trading businesses, and service-led SMEs with transparent source-of-funds profiles
  • Founders and operators who need supported currencies and payment tools for legitimate business activity
  • Customers who can complete KYC, KYB, AML, sanctions, and source-of-funds review without unresolved red flags
  • Businesses able to evidence suppliers, customers, invoices, ownership, and intended use of the account

What remains out of scope at launch

  • Sanctioned parties, hidden beneficial ownership, false identity attempts, or customers with unresolved AML concerns
  • Adult, gambling, narcotics, weapons, deceptive marketing, or other clearly prohibited sectors
  • Unlicensed financial services, third-party funds movement, nested payment models, or other activities outside partner rules
  • High-risk, opaque, or cash-intensive sectors unless a provider explicitly supports them and legal review is satisfied

Control framework

Eligibility is not a marketing promise. It is a controlled onboarding hypothesis that must stay aligned with partner appetite, country support, programme rules, and transaction-risk reality.

Approval conditions

  • Every onboarding decision remains subject to partner policy, issuer rules, legal review, and jurisdictional availability
  • Passing KRYPVAULT's commercial screening does not override provider acceptance or compliance review
  • Account details, IBANs, cards, and wallet features can only be activated where the relevant programme supports them
  • Feature access may differ by customer type, country, product module, and transaction behaviour

Ongoing monitoring

  • Customers remain subject to transaction monitoring, sanctions screening, review triggers, and periodic refresh requirements
  • Unexpected use patterns, unsupported industries, or adverse findings can lead to rejection, restriction, or exit
  • Country rollout will be phased and can change if provider support or legal comfort changes
  • KRYPVAULT's operating model is designed to protect both approved customers and authorised partners over time

Important note for providers

KRYPVAULT's commercial intention is to onboard customers that can be served cleanly, documented properly, and supported without straining partner compliance, operational, or reputational thresholds.

If a partner's programme, issuer, or legal advice does not support a country, customer type, or feature, KRYPVAULT will keep that case out of scope rather than force an exception.