For banks, NBFCs, fintechs and processors

One engine. Every decision you have to defend.

Fraud, credit, underwriting, disputes, AML and agent payments: with Nyx, decide each one in the moment and keep the evidence to defend it later.

Why these belong together
One data modelYour data defined once, used by every decision.
One decision pathFeatures, model, policy, verdict: one call, whether the question is fraud, credit or eligibility.
One evidence recordAn examiner reads a credit decision the way they read a fraud one.
Dated obligations

The deadlines putting decisions on the clock.

Nyx deploys in any regime. Each one is mapped with the first partner there.

IN
India

RBI Authentication Directions 2025: risk-based authentication for cross-border CNP from 1 Oct 2026. DPIP live 1 Sep 2026, Phase 2 scoring before completion. RBI Outsourcing Directions, Nov 2025. DPDP obligations from 13 May 2027.

AE
UAE

CBUAE Notice 3057, fines since 31 Mar 2026. CBUAE AI guidance of 11 Feb 2026: model inventory, bias testing, third-party review.

SA
Saudi Arabia

SAMA Counter-Fraud Framework, in force since 13 Apr 2026.

EU
European Union

Verification of Payee (IPR). PSD3/PSR liability shift from 2028.

UK
United Kingdom

APP-fraud reimbursement, in force since 7 Oct 2024.

SG
Singapore

MAS Shared Responsibility Framework.

AU
Australia

Scams Prevention Act 2025.

US
United States

No federal mandate yet; liability pressure building.

The decision domains

What each pack decides.

Every pack answers one question, on your data, in your deployment. The status says how much is already built, so you can tell what a first pilot would involve.

PILOT READY

Fraud management

Approve, review or decline a transaction or account action, inside the authorization path.

IN BUILD

Agent trust

Is this agent what it claims, who delegated to it, and is the purchase inside the mandate’s scope, caps and expiry? For your own customer’s agent, or the merchants a PSP serves.

PARTNER-LED

Credit risk

Extend, limit, price or decline exposure, with the policy that bound it and reasons a customer can be given.

Primitives exist · scoped with the first partnerScope the credit-risk pack →
PARTNER-LED

Underwriting

Accept, refer or decline against written policy, with the clauses and evidence bound to the outcome rather than reconstructed later.

Primitives exist · scoped with the first partnerScope the underwriting pack →
PARTNER-LED

Disputes and chargebacks

Accept, represent or write off a claim inside network deadlines, where assembling the evidence is most of the work.

Primitives exist · scoped with the first partnerScope the disputes pack →
PARTNER-LED

AML, KYC and monitoring

Onboard, clear, escalate or file, with a trail an examiner can follow without asking anyone to explain it.

Primitives exist · scoped with the first partnerScope the AML and KYC pack →
PILOT READY

Built, and can go into a pilot on your data.

IN BUILD

Being written now with design partners. Agent trust, the evidence record and the evidence pack sit here.

OPEN TO DESIGN PARTNERS

Entities, features and policies being defined; the first partner shapes them. The PSP trust endpoint sits here.

PARTNER-LED

Engine primitives in place; the pack is scoped with the institution that needs it first. Credit risk, underwriting, disputes and AML sit here.

Nothing here is a shipped production result; Nyx is pre-launch.

Not on the list

Bring us the decision you actually need to make.

Tell us which decision →

If a decision has data behind it, a policy around it and an auditor after it, it maps onto the same primitives.

Collections and recoveriesMerchant onboarding riskAcquiring and portfolio riskLimit and exposure managementPayment screeningScam and mule detectionEligibility and pricingTrust and safety

Candidates, not shipped packs. We will tell you which parts exist, which we would build with you, and how long a first pilot would take.

Questions

Which pack, and how far along.

What the labels mean and where to start.

Which pack should we start with?

Fraud management, in most cases, because it is the pack that is built and the fastest route into a first pilot. Any pack can be the entry point; the replay that starts an engagement runs on whichever decision you need.

What is a domain pack?

A versioned configuration declaring the canonical entities, mappings, features, models, policies, outcome taxonomies, prompts and decision actions one decision domain needs. Nothing domain-specific is welded into the engine, so adding a decision domain is a configuration exercise rather than a second procurement.

What do the status labels mean?

Pilot ready means built and ready to run on your data. In build means being written now. Open to design partners means the pack is built with whoever needs it first. Partner-led means the primitives are in place and the pack is scoped with the first partner. Direction means stated intent: not built, not in a pilot, not on a price list.

Who runs it day to day?

Your own teams. Fraud strategy, fraud operations and financial crime for the fraud pack; credit and risk teams for credit risk and underwriting. The same Command Center, Daily Brief and Workbench serve all of them.

Our decision is not on the list. Now what?

Adjacent decisions map onto the same primitives and are scoped on request: collections and recoveries, merchant onboarding risk, acquiring and portfolio risk, limit and exposure management, payment screening, eligibility and pricing. They are candidates, not shipped packs.

Start where it hurts

Start with the decision that hurts most.

Tell us the decision, the volume and the deployment you need. We will tell you what a first pilot looks like, and what we would have to build to get there.

HELLO@NAXVERSE.AI · FOUNDER-LED, PROCUREMENT-READY · DUE-DILIGENCE PACK ON REQUEST