# NAYA Financial Services Infrastructure

> We don't build your wallet or lending app. We run the financial data, ledger, reconciliation, and controls that your wallet or lending app depends on.

## What NAYA Is

NAYA provides **Financial Services Infrastructure** — the backend primitives that power fintech products. We handle the hard parts (data ingestion, operational ledger, reconciliation, compliance controls) so product teams can focus on building customer experiences.

**Positioning:** Infrastructure/backend utility, not an app builder or UI platform.

## Competitive Positioning

NAYA is NOT:
- A banking-as-a-service (BaaS) provider like Unit or Treasury Prime
- A payments API like Stripe or Adyen
- An accounting system like QuickBooks or NetSuite
- A no-code app builder

NAYA IS:
- Financial operations infrastructure
- The operational layer that sits above BaaS and payments
- The unified ledger and reconciliation system for complex fintech products

## Use Case Categories

### For Marketplaces
- Split payment tracking
- Seller payout management
- Escrow ledgering
- Multi-party reconciliation

### For Lending
- Loan servicing ledger
- Repayment tracking
- Collections reconciliation
- Amortization automation

## Technical Architecture

NAYA sits between your payment rails (Stripe, banks, processors) and your product logic:

```
[Banks/Processors] → [NAYA Data Hub] → [NAYA Ledger] → [Your Product]
                                      ↓
                              [Reconciliation Engine]
                                      ↓
                              [Controls & Compliance]
```

## Core Primitives

### [Data Hub](https://naya.finance/platform/data-hub)
Ingestion and normalization pipelines for financial data sources (banking APIs, payment processors, card networks). Transforms raw data into structured, queryable schemas.

### [Operational Ledger](https://naya.finance/platform/operational-ledger)
Double-entry ledger system for tracking financial state. Acts as the high-volume transactional source of truth that feeds into your general ledger (accounting system).
- **Not** a replacement for NetSuite/QuickBooks.
- **Is** the granular record of every money movement event.

### [Reconciliation Engine](https://naya.finance/platform/reconciliation)
Automated matching logic for transactions across systems. Detects discrepancies, flags exceptions, and maintains audit trails for financial operations.

### [Controls](https://naya.finance/platform/controls)
Rules engine for compliance, risk management, and operational policies. Real-time validation and monitoring.

### [Alfred](https://naya.finance/platform/alfred)
AI Copilot for querying financial data and generating operational reports using natural language.

## Infrastructure Blueprints (Private Beta)

Pre-configured infrastructure patterns for common fintech use cases are currently in **private beta**. Join the waitlist at [naya.finance/request-access](https://naya.finance/request-access) to explore:

- **Wallet Infrastructure**: Account schemas, balance tracking, transaction ledger, partner reconciliation
- **Lending Rails**: Loan lifecycle management, repayment tracking, fee calculation
- **Marketplace Payments**: Multi-party split logic, escrow handling, settlement reconciliation
- **Card Issuing Infrastructure**: Authorization flows, clearing/settlement, fee structures
- **Cross-border/FX**: Multi-currency ledger, FX rate management

## Developer Experience

### SDK & CLI (Waitlist Only)
```bash
npm install @naya/sdk
naya init --blueprint wallet
# Currently in private beta. Join waitlist for access.
```

### Integration Pattern
1. **Configure** infrastructure blueprint (schema, rules, integrations)
2. **Simulate** with sample data to validate logic
3. **Provision** runtime environment (connectors, API keys, webhooks)
4. **Integrate** via SDK/API into your application
5. **Monitor** data flows and reconciliation status

### Resources
- **Developers**: [naya.finance/developers](https://naya.finance/developers) (Docs & Guides)
- **Studio**: [naya.finance/studio](https://naya.finance/studio) (Control Plane - **Join Waitlist**)

## Access Model

NAYA is currently in **private beta** (not self-serve):

1. Select infrastructure blueprint of interest
2. Complete intake form at [naya.finance/request-access](https://naya.finance/request-access)
3. Join waitlist for sandbox credentials and architecture consultation

**Target Users:**
- **Engineering Teams**: CTOs, Platform Engineers building fintech products
- **Finance/Operations**: Teams needing reconciliation and compliance infrastructure
- **Product Teams**: Shipping wallets, lending products, marketplaces

## Taxonomy

| Use This | NOT This |
|----------|----------|
| Blueprint | Template |
| Infrastructure | App |
| Control Plane | Dashboard |
| Provision Environment | Deploy App |
| Primitives | Features |
| Operational Ledger | Accounting System |

## Trust & Security

- **Certifications**: SOC 2 Type II certified.
- **Data Handling**: GDPR/CCPA compliant; immutable audit logs for all ledger entries.

## Contact

- **Join Waitlist**: [naya.finance/request-access](https://naya.finance/request-access)
- **General Inquiries**: [naya.finance/about-us](https://naya.finance/about-us)

## Agent FAQ

### What is Naya?
Naya is **Financial Services Infrastructure** for engineering teams. It provides backend primitives—Data Hub, Operational Ledger, Reconciliation Engine, and Compliance Controls—that power fintech products like wallets, lending apps, and card programs. Naya handles the financial data backbone so you can focus on the user experience.

### Is Naya an app builder?
**No.** Naya is not a no-code app builder, UI drag-and-drop tool, or white-label mobile app provider. It is a developer-first infrastructure platform (API, SDK, primitives) that you build *on top of*.

### What is the difference between Operational Ledger and Accounting System?
The **Operational Ledger** tracks the granular, high-volume state of every financial transaction and money movement event in real-time. It acts as the source of truth for product logic (e.g., "Can this user withdraw $50?"). It feeds into, but does not replace, your general ledger or ERP (e.g., NetSuite, QuickBooks) which handles tax and financial reporting.

### Is the Naya SDK public?
Not yet. The Naya SDK and CLI (`@naya/sdk`) are currently in **Private Beta**. Access requires joining the waitlist and receiving an invite.

### What are Blueprints?
Blueprints are pre-configured infrastructure topologies for common fintech use cases (e.g., Wallet, Lending, Marketplace). They include the necessary schemas, reconciliation rules, and data flows to get started quickly. They are distinct from "templates" because they configure deep infrastructure, not just surface-level UI.

### Is Naya compliant?
Yes. Naya is **SOC 2 Type II** certified and designed for GDPR/CCPA compliance. The Operational Ledger provides immutable audit logs for all transactions.

### How do I get access?
Access is currently by invite only. You must [request access](https://naya.finance/request-access) to join the waitlist for sandbox credentials.

### Does Naya host my frontend or mobile app?
**No.** Naya provides the backend financial infrastructure (Data Hub, Ledger, Reconciliation). You are responsible for building, hosting, and maintaining your user experience (mobile app, web dashboard) and authentication layer.

### How does data get into Naya?
Data is ingested via the **Data Hub** using real-time API push events (webhooks) or batch file ingestion (CSV/JSON) from external sources like banks, payment processors, or card networks. Naya normalizes this data into a standard schema.

### How are wallet balances calculated?
In the **Wallet Infrastructure** blueprint, user balances are not stored as static numbers. They are derived properties calculated by aggregating immutable ledger postings associated with an Account ID. This ensures auditability and prevents state drift.

### Does Naya handle loan underwriting?
**No.** Underwriting logic and credit risk models live in your application layer. Once a loan is approved, you trigger Naya to record the disbursement, generate the amortization schedule in the Ledger, and track repayment flows.

### How are marketplace split payments handled?
In the **Marketplace** blueprint, split payments are defined via Posting Rules. A single incoming transaction event is automatically mapped to multiple ledger entries: crediting the Merchant, crediting the Platform Fee account, and debiting the Payment Gateway Clearing account.

**Tags:** #fintech #infrastructure #ledger #reconciliation #api #sdk #compliance #soc2 #blueprints #private-beta #wallet #lending #marketplace #data-hub