FinArc Docs

On-chain payment requests with a cleaner, simpler flow.

FinArc is a lightweight request layer built on Arc Testnet. It helps users create structured payment requests, share them instantly, and settle directly from wallets without adding unnecessary complexity.

Create a request Open dashboard

Wallet-first

Users connect a browser wallet and interact directly with the app without creating traditional accounts.

Direct settlement

Payments move from payer to recipient on-chain. FinArc does not custody user funds.

Structured requests

Requests carry amount, recipient, and optional context in a cleaner, shareable format.

Introduction

Overview

FinArc is designed to make payment intent clearer. Instead of handling payment coordination through messages, screenshots, or disconnected wallet transfers, FinArc introduces a simple request object that can be created, shared, and settled on-chain.

The product is intentionally minimal. The goal is not to add layers between users and payments, but to create a cleaner flow around them. Wallet connection, request creation, and settlement all stay straightforward.

Flow

How it works

1. Connect wallet

The user connects a supported browser wallet such as MetaMask or Rabby through the FinArc interface.

2. Create request

A request is created with an amount, recipient wallet, and an optional note or reference.

3. Share request

The request can be opened or shared through its own route or request view.

4. Settle on-chain

The payer confirms the transaction from their wallet, and the request status updates once the transaction is confirmed.

Core object

Requests

Each request is intended to be simple, structured, and readable.

Amount

The requested payment value displayed to the payer in a clear, standard format.

Recipient

The destination wallet that will receive payment once the transaction is executed.

Reference

An optional note that adds context, such as purpose, invoice label, or lightweight metadata.

Status

Requests can remain open until successfully settled on-chain, after which they can be displayed as completed.

This approach gives both sides a cleaner transaction context and reduces ambiguity compared with ad hoc transfers.

Payments

Settlement

FinArc does not hold funds, pool balances, or act as an intermediary. Settlement happens directly from the payer’s wallet to the intended recipient through the connected network.

This keeps the product model simple and improves transparency. Users retain control of transaction approval at the wallet level, and payment confirmation can be traced on-chain.

FinArc is non-custodial by design. Users approve transactions from their own wallets, and the application does not take possession of funds.

System design

Architecture

FinArc is intentionally lightweight. The stack is selected to keep the product fast to iterate on while remaining credible as an on-chain application.

Frontend

Next.js powers the application interface, routing, and page-level structure.

Wallet layer

Wagmi manages wallet connection state and interaction with injected browser wallets.

Chain

Arc Testnet is used for request settlement and transaction flow during the current phase.

Data layer

Supabase can support request persistence, history, and product state outside wallet interactions.

User

Wallet-connected session

Next.js App

UI, pages, request flow

Wagmi

Wallet connection state

Arc Testnet

Settlement network

Principles

Why FinArc

Cleaner intent

Payment requests make the purpose and destination of a transfer explicit before settlement.

Less friction

Users interact through wallets they already use instead of creating extra accounts or workflows.

Transparent state

Request status can move from open to completed with clear, verifiable settlement logic.

Composable foundation

The request layer can evolve into richer invoice, payroll, merchant, or protocol-native payment flows.

Questions

FAQ

Do I need a wallet to use FinArc?

Yes. FinArc currently relies on browser wallets such as MetaMask or Rabby for connection and transaction approval.

Is FinArc live on mainnet?

Not at the moment. The current setup is on Arc Testnet.

Does FinArc hold user funds?

No. FinArc is non-custodial. Funds move directly from the payer’s wallet to the recipient.

What happens if a transaction fails?

The request remains open until a successful payment is confirmed.

Next step

Start creating and testing request flows.

FinArc is designed to stay simple at the surface while giving you a strong base for more advanced payment workflows.

Create request