> 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/faq.md).

# FAQ

***

## General

**What is ShadowPay?**

ShadowPay is a privacy-first crypto neobank built on Solana. It's a non-custodial account for USDC and SOL where transfer amounts are encrypted by default, settlement happens in under a second, and both people and AI agents can hold accounts.

**Do I need to know anything about blockchain to use ShadowPay?**

No. You sign up with an email and a passkey, the same way you'd set up Face ID for any app. Everything underneath, keys, encryption, settlement, is handled for you.

**What currency does ShadowPay use?**

USDC on Solana. SOL is held automatically as a gas reserve so you never have to think about network fees directly.

**Is ShadowPay anonymous?**

No, and it's not designed to be. Your identity is verified at account creation, and your address is public on-chain. What's private is the amount moving through your account. See [Regulatory Framework](/compliance/regulatory-framework.md) for why this distinction matters.

***

## For individuals

**How does ShadowPay keep my transaction amounts private?**

Transfers use Solana's Confidential Balances token extension, which encrypts amounts using zero-knowledge proofs generated on your own device. Only you and the recipient can decrypt the amount. See [Confidential Transfers Explained](/privacy-and-confidential-transfers/confidential-transfers.md).

**Can anyone see how much money I have?**

No. Your balance is encrypted on-chain and only decryptable with your key. Someone can see that your address exists and holds a token account, but not the amount in it.

**What if I need to prove a payment to someone, like a landlord or an auditor?**

Generate a selective disclosure proof for that specific transaction. It reveals only what you choose to share, to whoever you choose to share it with. See [Selective Disclosure & Audit Export](/privacy-and-confidential-transfers/selective-disclosure.md).

**What happens if I lose my phone?**

If your passkey is synced across devices (iCloud Keychain, Google Password Manager), you can recover access immediately on another device. If you exported your key ahead of time, you can restore access using that. See [Key Management & Custody](/privacy-and-confidential-transfers/key-management.md).

**Is my transaction history stored anywhere in plaintext?**

Not by ShadowPay. Your decrypted history is rendered locally on your device using your own key. ShadowPay's servers only ever handle ciphertext and public account metadata.

***

## For developers and agent builders

**How do agent accounts actually work?**

Every agent gets its own Solana keypair and its own ShadowPay Agent ID, namespaced under a parent account. It transacts under a spend policy the parent defines: daily limits, allowed recipients, time windows, and an optional human approval threshold. See [Agent Accounts Overview](/agents-and-automation/agent-accounts-overview.md).

**Can an agent spend beyond what I've authorized?**

No. Spend policy checks happen before a transaction is ever signed, not as a post-hoc review. A policy-violating transaction is never constructed in the first place. See [Spend Policies](/agents-and-automation/spend-policies.md).

**Does ShadowPay support x402?**

Yes, natively, for every agent account. See [x402 Payments](/agents-and-automation/x402-payments.md).

**How do I get notified when an agent transaction happens?**

Subscribe to webhook events for your account. See [Webhooks & Events](/agents-and-automation/webhooks-and-events.md) and the [Webhooks API](/api-reference/webhooks.md).

**Can I read my agent's transaction amounts through the API?**

Only by decrypting them client-side with your account's key. ShadowPay's API never returns plaintext amounts, since ShadowPay's servers don't hold the decryption key either.

***

## Compliance

**Why does ShadowPay require KYC if it's a privacy product?**

Because confidentiality and anonymity aren't the same thing. ShadowPay hides transaction amounts, not identities. Every account is tied to a verified person or entity, which is what allows the product to operate under the GENIUS Act framework and cooperate with lawful legal process when required.

**What happens for large or cross-border transfers?**

Transfers above regulatory thresholds are subject to Travel Rule requirements, including counterparty screening. See [KYC & Travel Rule](/compliance/kyc-and-travel-rule.md).

**Is the ShadowPay protocol open source?**

The confidential transfer logic is built directly on Solana's open source Token-2022 program. ShadowPay's application layer, meaning the app, backend, and indexer, is not open source during beta.

***

## Fees

**What does ShadowPay charge for transfers?**

Nothing, during beta. You only pay the underlying Solana network fee, typically a fraction of a cent, covered automatically from your SOL reserve.

**Are there fees for using the API?**

Not during beta. A metered API tier for high-volume agent usage is planned as part of ShadowPay's post-beta revenue model.


---

# 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/faq.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.
