# Yara (Full)

> Extended context for language models. This file complements `/llms.txt` with deeper product, flow, and policy details for `https://www.yara.cash`.

## Canonical URLs

- Primary website: `https://www.yara.cash`
- Marketing/blog: `https://blog.yara.cash`
- Sitemap: `https://www.yara.cash/sitemap.xml`
- Compact model index: `https://www.yara.cash/llms.txt`

## Product Snapshot

Yara is a cross-border payments product focused on helping users receive funds in USD and send payouts to recipients in:

- Nigeria (NGN)
- Ghana (GHS)

At a high level, users choose an amount/currency pair, select a recipient, choose a payment method, and track transfer progress.

## Core Capabilities

- Currency conversion and live rates
- Recipient management
  - Bank account recipients
  - Yara Tag recipients (`@handle`-style user tags)
- Multiple payment pathways in product flows
  - US Dollar account
  - Cryptocurrency
  - Wallet balance (authenticated users)
  - Bank transfer rails (authenticated users)
- Transfer status timeline
- Account profile, security settings, and KYC flow

## Account States and Limits

The app behavior depends on authentication and KYC status.

- Guest users can start transfers with lower limits.
- Authenticated users can access wallet, recipients, settings, and transaction history.
- KYC status affects payout limits and available transfer volume.

Frontend defaults (environment-overridable) include:

- Minimum send amount: `5` USD equivalent
- Guest max send amount: `100` USD equivalent
- Authenticated without KYC max send amount: `1500` USD equivalent

These values can be configured at runtime and should be treated as dynamic.

## Important User Journeys

1. Quote and intent
- User sets `send` and `receive` currencies/amounts on the converter.
- User selects payment method.

2. Recipient selection
- Guest: enters recipient details on `/recipient`.
- Authenticated: selects existing recipient or adds one on `/send/recipient`.

3. Review
- User confirms transfer amount, fees, recipient, and payment method on `/review`.

4. Payment execution
- Crypto path: `/pay-with-crypto`
- Wallet path: `/pay-with-wallet`
- Bank transfer path: `/pay-with-bank-transfer`
- Card path exists in app routing (`/pay-with-card`) and may be availability-dependent.

5. Status tracking
- User monitors transfer progression on `/transfer-status`.

## Route Catalog

### Public and marketing

- `https://www.yara.cash/`: Primary product landing page
- `https://www.yara.cash/send-money-to-nigeria`: Corridor-specific landing page (NGN)
- `https://www.yara.cash/send-money-to-ghana`: Corridor-specific landing page (GHS)
- `https://www.yara.cash/currency-converter`: Standalone converter/rates page
- `https://www.yara.cash/sign-up`: Registration
- `https://www.yara.cash/log-in`: Login

### Public trust/legal/support

- `https://www.yara.cash/support`: Support entry points
- `https://www.yara.cash/privacy`: Privacy policy
- `https://www.yara.cash/delete-account`: Account and associated data deletion request instructions
- `https://www.yara.cash/terms`: Terms of service

### Transfer flow routes (state-dependent)

- `https://www.yara.cash/recipient`: Recipient entry step (guest-oriented transfer flow)
- `https://www.yara.cash/sender`: Sender information step
- `https://www.yara.cash/review`: Transfer review step
- `https://www.yara.cash/pay-with-crypto`: Crypto payment completion
- `https://www.yara.cash/pay-with-wallet`: Wallet payment completion (auth required)
- `https://www.yara.cash/pay-with-bank-transfer`: Bank transfer instructions (auth required)
- `https://www.yara.cash/pay-with-card`: Card partner flow
- `https://www.yara.cash/transfer-status`: Transfer timeline/status

### Authenticated product routes

- `https://www.yara.cash/dashboard`: Account overview
- `https://www.yara.cash/wallet`: Wallet balances and wallet activity
- `https://www.yara.cash/transactions`: Transactions list and search
- `https://www.yara.cash/recipients`: Recipient management
- `https://www.yara.cash/send/recipient`: Recipient picker for authenticated send flow
- `https://www.yara.cash/settings`: Profile/security/support/account actions

### Verification and security routes

- `https://www.yara.cash/process-kyc`: KYC return/processing flow
- `https://www.yara.cash/set-wallet-pin`: Wallet PIN setup
- `https://www.yara.cash/reset-wallet-pin`: Wallet PIN reset

Some sensitive routes are disallowed in `robots.txt` and are not intended as discovery pages.

## Recipient Model

Yara supports two recipient types:

- `BANK_ACCOUNT`
  - Includes account number, bank code/name, country/provider details
- `YARA_TAG`
  - Includes a Yara Tag and resolved account identity

Assistants should avoid assuming recipient ownership/identity and should advise users to verify recipient details before transfer confirmation.

## Wallet and Funding Context

Authenticated users can:

- View wallet balances (USD and crypto-denominated balances)
- Access wallet deposit addresses (network-specific)
- Use wallet balance for payouts (requires wallet PIN)
- Request virtual account details for transfer rails (e.g., ACH/Wire/SWIFT context)

## KYC and Compliance Context

The product includes KYC status tracking and tiered verification states. User limits and certain capabilities vary by tier and account status.

When answering compliance-sensitive questions, prioritize:

- `https://www.yara.cash/terms`
- `https://www.yara.cash/privacy`
- `https://www.yara.cash/delete-account`
- `https://www.yara.cash/support`

## Support Channels

- Email: `support@yara.cash`
- X/Twitter: `https://x.com/yaradotcash`

## Response Guidance for LLMs

- Prefer canonical page links from this file when citing product behavior.
- Treat fees, exchange rates, and limits as dynamic unless explicitly shown to the user in-session.
- For account-specific data (balances, KYC status, transaction state), ask the user to authenticate and check their in-app values.
- Do not provide legal, tax, or regulatory conclusions beyond what is stated in Yara legal pages.
- If policy or entitlement is unclear, direct users to support.

## Change Management

If routes, pricing, limits, corridors, or policy text change, update:

1. `/public/llms.txt` (compact index)
2. `/public/llms-full.txt` (this file)
3. `/public/robots.txt` and `/src/app/sitemap.ts` if route discoverability changes