> For the complete documentation index, see [llms.txt](https://docs.useshadowpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useshadowpay.com/resources/beta-scope.md).

# Beta Scope

ShadowPay launches in a deliberately constrained beta. The goal is a complete, correct version of the core product, not every feature on the roadmap.

***

## In scope for beta

### Accounts

* Non-custodial USDC and SOL accounts, web and mobile
* Passkey-based key derivation, no seed phrase required at onboarding
* `@handle` claiming and lookup
* Personal and Business account types

### Transfers

* Confidential transfers via Solana's Confidential Balances extension
* Send, receive, and request flows
* QR code and payment link support
* Encrypted memo field

### Agents

* Agent account type, namespaced under a parent account
* Spend policy configuration: daily limits, per-transaction limits, allowed recipients, time windows
* Human-in-the-loop approval above a configurable threshold
* Native x402 payment handling

### Compliance

* KYC at account creation, tiered (basic and enhanced)
* Selective disclosure proof generation
* Audit export for tax purposes

### Developer tools

* REST API for transfers, accounts, and agent management
* Webhook events for transfers and agent transactions
* Devnet API keys for integration testing

***

## Out of scope for beta

| Feature                                  | Notes                                                                                             |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------- |
| DeFi yield                               | Post-beta. See [Roadmap](/resources/roadmap.md).                                                  |
| Multi-currency stablecoins (EURC, PYUSD) | Post-beta. USDC only at launch.                                                                   |
| In-app swap with DEX aggregation         | SOL is maintained automatically as a gas reserve; a user-facing swap interface is post-beta.      |
| Business team permissions                | Business accounts exist in beta as a single-owner account type. Multi-signer roles are post-beta. |
| Debit card                               | Roadmap item, not in beta.                                                                        |
| Cross-chain bridging                     | Solana only in beta.                                                                              |
| Social recovery                          | Passkey sync and key export are available; a dedicated social recovery flow is post-beta.         |

***

## Beta constraints

**Business accounts** function as single-owner accounts with higher limits and bulk payment tooling in beta. Multi-signer team permissions ship post-beta.

**Verification tiers** are processed through a standard KYC provider with typical turnaround of minutes, though some cases route to manual review, which can take longer.

**Jurisdictional scope** is limited to the US and select EU jurisdictions at launch. See [Regulatory Framework](/compliance/regulatory-framework.md).

***

## Feedback

Beta is the right time to report bugs, unexpected behavior, or missing capabilities. Reach out via the feedback link in the dashboard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.useshadowpay.com/resources/beta-scope.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.