What ShyPay is, where you would sit in it, and what data you would and would not send us.
This page is written for provider and business-verification reviewers. It states the use case, the users, the geography, the flows, and the integration surface, without overclaiming anything. ShyPay, LLC is pre-launch: no integration is live, and no partnership is being asserted.
A self-custody dollar wallet for everyday payments.
ShyPay is a mobile application that lets a person buy USDC on Solana into a wallet they control, send it to other people, pay merchants that accept it, and sell it back to dollars in their bank account. The product thesis is privacy at the merchant level — no card network assembling a spending profile — with full identity verification kept at the points where money enters and leaves the system.
ShyPay, LLC is non-custodial software. It never holds customer funds, keys, or fiat currency, and it does not claim any financial services licence. It will not make the service available to sanctioned persons or jurisdictions, and will screen wallet addresses against sanctions lists. The compliance page sets that out in detail.
Target users
Individual consumers making ordinary retail and peer-to-peer payments. Not institutions, not traders, not businesses transacting on behalf of third parties.
Geography
The United States is the planned launch market. This is a plan and not a live service; availability will follow what the ramp provider supports.
Asset and network
USDC on Solana only. ShyPay does not issue an asset, does not run an exchange, and does not offer trading, yield, lending, or staking.
Where the fiat is, and where it is not.
Fiat exists only at the two ends, and both ends belong to the regulated ramp provider, which contracts with the user directly.
The four expected flows.
Described in the order a user would meet them. Each is covered step by step on the how it works page.
Cash in
The user buys USDC through the ramp provider's widget or SDK, with delivery to their own Solana address. The provider verifies identity, quotes, takes payment from the user's bank or card, and settles the asset. ShyPay never receives the fiat.
Peer-to-peer send and request
A direct USDC transfer on Solana, approved by the user and signed with the 2-of-2 split key. A request is an invitation that moves nothing until the recipient approves it. No ShyPay account sits in the middle, and the Solana network fee is paid from the user's own wallet.
In-store payment
A merchant's system issues a signed payment request. The wallet verifies the issuer signature, validity window, single use, exact asset and recipient on-device, then the user approves and signs. Settlement is a peer-to-peer transfer.
Cash out
The user sells USDC through the ramp provider, which quotes the payout, applies its checks, and pays the bank account verified with it. Again ShyPay is not a party to the fiat leg.
How ShyPay intends to use each provider.
ShyPay is being built to use Dynamic for wallet key management and Ramp Network for buying and selling USDC; these integrations are in development and are subject to those providers’ approval and terms. Nothing is live, no agreement is asserted, and no logos are used. These descriptions are our intended architecture, offered so a reviewer can assess it.
Ramp Network
Fiat on-ramp and off-ramp via the provider's widget or SDK: buy and sell of USDC on Solana, delivered to and taken from the user's own self-custody address. The provider would perform identity verification, sanctions screening and transaction monitoring, and would contract with the user for that service.
Dynamic (dynamic.xyz)
Embedded wallet infrastructure that would hold one share of a 2-of-2 split signing key in secure hardware, with the other share on the user's device. Both shares are needed for every signature, so neither the provider nor ShyPay can sign alone. It would also provide recovery and private key export. ShyPay holds no key share at any time.
Solana and USDC
Solana is the settlement network. USDC is issued by Circle. ShyPay issues nothing, redeems nothing, and backs nothing.
ProxyPay
The merchant point-of-sale integration. ShyPay and ProxyPay are separate companies under common ownership, and that relationship is disclosed to our providers and partners. They are built to run on separate systems, and ShyPay does not receive merchant records or what you bought. The relationship is disclosed to providers.
What ShyPay would and would not receive.
Stated as the design intent, so a reviewer can check it against what an integration would actually expose.
ShyPay would receive
- The user's own public wallet address, in order to display their balance
- That a funding or payout session was opened, and its status as reported back
- A display name the user chooses, and a contact address for support and security notices
- Diagnostic records needed to operate the application and investigate abuse
ShyPay would not receive
- Identity documents, verification results, or KYC case files
- Bank credentials, account numbers, or card numbers
- Any share of a signing key, a private key, or recovery material
- Merchant line items, receipts, category codes, or loyalty identifiers
- Contacts, location history, or advertising identifiers