# Solutions/Key Features

<figure><img src="/files/dUdz8gJEniPde8Rxynsz" alt=""><figcaption></figcaption></figure>

**Numpay is engineered to tackle the pain points of traditional money transfer systems.** By streamlining processes and using advanced technology, each feature is designed to deliver a distinct benefit to our users. Explore the key features below in the order they will be rolled out according to our roadmap.

## 1. Instant Transfers

Transfers are executed via atomic smart contract calls on Layer 2 networks (Arbitrum, Optimism) with block finality times of 1–2 seconds. For cross-chain cases, Numpay uses bridge protocols with optimistic verification and relayer incentives to maintain sub-5-second settlement.

**Implementation:**

* Transactions are signed client-side and broadcast via meta-transaction relayers.
* Settlement occurs once included in a confirmed L2 block.
* For chains with finality >5 seconds, optimistic pre-crediting is applied.

**Impact:**

* 99% of transfers settle in under 3 seconds.
* Suitable for emergency disbursements, micro-payments, and just-in-time B2B transactions.

| Platform           | Average Settlement Time | Availability |
| ------------------ | ----------------------- | ------------ |
| Numpay L2 Transfer | 1–3 seconds             | 24/7         |
| Traditional Bank   | 1–5 business days       | Limited      |
| Remittance Service | 30 min–24 hours         | Limited      |

## 2. No Bank Details Needed

**Process Flow:**

1. The identifier is verified off-chain by a verifier node.
2. A signed attestation is generated using ECDSA over secp256k1.
3. Smart contracts resolve the identifier → address mapping using this attestation.
4. Payment is routed directly to the mapped address.

**Security:**

* Identifiers are AES-256 encrypted before leaving the user device.
* Mappings are stored off-chain with hash commitments stored on-chain for integrity.

**Impact:**

* Removes IBAN/SWIFT friction entirely.
* Extends access to unbanked/underbanked users who only have a phone.

## 3. Zero Fees

Protocol-level transfers are fee-free for both sender and receiver. Numpay covers gas via sponsored transaction relayers (EIP-2771).

**Implementation:**

* Relayers are funded via staking pools and yield from protocol treasury assets.
* Gas abstraction allows transfers without holding native chain tokens.
* Fee burn rate is zero at the protocol level; off-ramps may still charge fiat conversion fees.

**Impact:**

* True 1:1 value transfer, no deductions.
* Predictable cost structure for high-frequency microtransactions.

| Platform           | Sender Fee | Receiver Fee | Hidden Costs |
| ------------------ | ---------- | ------------ | ------------ |
| Numpay             | $0         | $0           | None         |
| Bank Wire Transfer | $20–$50    | $0–$15       | FX Spread    |
| Money Transfer App | 2–5%       | 0–3%         | FX Spread    |

## 4. Blockchain-Powered Security

Security is derived from the underlying L1/L2 blockchain consensus plus additional Numpay-specific safeguards.

**Security Layers:**

* Immutable transaction history on-chain.
* Formal verification of all core contracts (no reentrancy, overflow).
* Multi-sig governance for contract upgrades.
* End-to-end encryption for identifier mapping data.

**Comparative Advantage:**\
Unlike centralized remittance services that can retroactively reverse or modify ledger entries, Numpay transactions are irreversible once finalized, ensuring integrity.

| Threat Vector     | Traditional Services | Numpay Mitigation |
| ----------------- | -------------------- | ----------------- |
| Data Breach       | High risk            | No central DB     |
| Transaction Fraud | Medium risk          | Immutable ledger  |
| Insider Tampering | Possible             | Multi-sig control |

## 5. User-Friendly Experience

Abstraction layers hide blockchain complexity while preserving cryptographic security.

**Features:**

* Progressive web app (PWA) interface compatible with low-end devices.
* SMS/Email onboarding without explicit wallet setup.
* Automatic wallet creation and key management via smart contract wallets (ERC-4337 account abstraction).

**Impact:**

* No need to understand public/private keys.
* UX tested to maintain <15-second completion time for first-time transactions.

## 6. AI Transaction Summary

**What It Is:**\
Automated monthly transaction summaries generated by Numpay’s AI engine.

**Capabilities:**

* Categorizes transactions by recipient, amount, and purpose.
* Flags unusual activity based on user spending patterns.
* Generates downloadable CSV or API-accessible reports.

**Use Case:**\
Ideal for freelancers, small businesses, and DAO treasuries that require automated reconciliation and compliance-ready reporting.

## 7. Global Reach

Interoperable smart contracts and identifier resolution are chain-agnostic, allowing cross-chain and cross-border operation.

**Capabilities:**

* Native support for Ethereum, Arbitrum, and Optimism at launch.
* Phase 2 expansion to Polygon, BNB Chain, and Base.
* Inter-chain transfers via trust-minimized bridges with bonded relayers.

**Impact:**

* Operates 24/7, regardless of banking hours or local holidays.
* Supports high-throughput scenarios (>1,000 tx/sec across networks).

| Phase | Supported Networks           | TPS Capability |
| ----- | ---------------------------- | -------------- |
| 1     | Ethereum, Arbitrum, Optimism | 1,000+         |
| 2     | Polygon, BNB Chain, Base     | 5,000+         |
| 3     | Solana, Avalanche            | 10,000+        |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://numpay.gitbook.io/numpay/about-numpay/solutions-key-features.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.