01 / RECEIVING

Create a request.

Connect Phantom and sign the message to verify your receiving wallet. Set the USDC amount and add a note if you need one. Your request gets its own link and expires after 24 hours.

The amount and receiving address stay fixed. Anyone with the link can read both, along with your note. Use a dedicated receiving wallet if you want to keep your trading address out of the request.

02 / PAYING

Review before you pay.

Open a request link and check the recipient, amount and expiry. Private checkout uses an existing Privacy Cash USDC balance. Unlocking that balance signs a message; it does not send money.

The quote shows the amount the recipient will receive, the protocol fee and the total private balance used. Payment requires a separate submission step.

03 / PRIVACY

Know what stays visible.

Privacy Cash aims to separate a withdrawal from its funding source. The recipient, amount and timing remain visible on Solana. Timing and amounts can still reveal connections.

Ghost and network providers can see request metadata. A dedicated receiving wallet limits what your link reveals; transferring directly between your wallets can connect them again.

Your spending keys and decrypted private notes stay in your browser. Ghost never asks for your seed phrase. Wallet sign-in verifies control of an address; it does not verify a real-world identity.

04 / COSTS

The quote comes first.

Ghost adds no payment fee in the current configuration. Privacy Cash charges its own protocol fee. Checkout retrieves the current fee and shows the full amount used before submission.

The current route uses USDC already deposited in Privacy Cash. Funding that balance is a separate action with its own costs. The amount on a request is the amount the recipient should receive.

05 / CONFIRMATION

Pending means pending.

A request is marked paid only after its recipient transfer is finalized and verified on Solana. Creating a request or submitting a proof is not payment confirmation.

If a response is lost, use Check payment status. The original payment stays saved. Keep the request link and this browser’s site data until the outcome is confirmed. A timeout is not a reason to create another payment.

Once a transfer completes on-chain, Ghost cannot reverse it.

06 / THE COMMUNITY COIN

Where $GHOST fits.

$GHOST is the community coin planned around the Ghost product. Payments use USDC, and using the app does not require owning the coin.

The first planned holder benefits are premium payment pages and invoice tools: page customization, reusable templates and organized payment records. These features are in development; the qualifying balance and access rules are not set yet. The token has not launched. Its verified mint and trading link will appear on the token page. Holding does not give a claim on customer payments or a guaranteed return.

07 / THE X ROADMAP

From a conversation to a payment.

Request links on X

Create a wallet-verified USDC request and share its link in a DM, reply or post. The payer opens Ghost to review the amount and receiving wallet. Sharing a link does not require X sign-in and is not an X Money transaction.

Pay an @handle · USDC

The intended flow connects an authenticated X identity to a signed receiving-wallet record. The payer checks the matched handle and destination before approving. Recipients sign in with X, verify a receiving wallet and explicitly enable their receiving profile. Ghost resolves the current X user ID for each lookup, so a reassigned handle cannot inherit someone else’s wallet. The code is ready for connection; lookup remains unavailable until the X app credentials are configured.

X Money · planned

This is a separate USD payout route. It requires supported provider access, recipient eligibility checks, a conversion quote and verified payout confirmation. Those integrations are not available yet. No X Money transfer can currently be made through Ghost.