> ## Documentation Index
> Fetch the complete documentation index at: https://docs.northfond.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# PRODUCT

# Product

## Register

brand

## Users

Backend engineers and product teams integrating stablecoin collection and local payouts into business software. They need exact contracts, safe sandbox workflows, and unambiguous production-readiness boundaries.

## Product Purpose

Help an approved business move from an API key to a verified NorthFond transaction with minimal guesswork. The documentation must explain the provider-neutral model, make the first request executable, and remain the trustworthy source for schemas, payment states, and operational behavior.

## Brand Personality

Calm, precise, and operational. NorthFond speaks like reliable financial infrastructure, not a speculative crypto product.

## Anti-references

Generic blue developer portals, neon crypto styling, vague feature marketing, undocumented examples, decorative dashboards, copied competitor language, and references that hide request or response contracts.

## Design Principles

1. Make the first successful request obvious.
2. Show exact contracts and examples instead of describing them abstractly.
3. State sandbox, live, chain, and route limitations beside the relevant action.
4. Keep provider complexity behind NorthFond's normalized resources.
5. Treat trust, security, retries, and reconciliation as core product content.

## Accessibility & Inclusion

Target WCAG 2.1 AA. Use descriptive links, a logical heading order, visible non-color status language, copyable examples, and concise prose that remains clear to developers working in a second language.