A public receiving address, a management credential and a wallet recovery phrase serve different purposes. Understanding that distinction is more important than copying a string that looks valid. Current PayIn creation asks only for the public receiving address for your chosen network; it does not need wallet recovery words or a private key.
Use your wallet's Receive function
For ordinary QR or Link receiving, use the Receive function in a compatible wallet that you control. Select the network in the PayIn form and check that it matches the network in your wallet. EVM addresses have the same general format across more than one network, so format validation cannot choose Base or Polygon for you.
Check the entire receiving address rather than only the first and last characters. A successful format check is not ownership verification and does not show that a token account is ready. The current Solana flow stops before signing when the receiving token account is missing.
Keep private access separate
The private management link returned by PayIn is not a wallet seed phrase, but it is still access information. Save it separately from a public request and keep it out of printed QRs, customer messages and public analytics. Losing it does not create an account-recovery entitlement.
A wallet recovery phrase controls wallet access. Do not paste an existing production recovery phrase into a payment-creation page, support chat or documentation example. A website migration and a logo update do not establish that an unrelated wallet tool is appropriate for storing funds.
The separate Open utility
The historical wallet-tool entry remains a separate address-generation utility for the Open ecosystem. It is not required for hosted PayIn receiving. Its original application and security flow are retained; this resource explains the boundary rather than replacing address-generation code with a new implementation during an SEO migration.
Self-hosted Open operators may need derived addresses and address pools for their deployment. The operator is responsible for generation, custody, export handling, permissions and recovery. A public address list and its recovery material must not be treated as equally shareable files.
Before using a generation workflow
Read the utility's instructions for the environment in which it runs. Avoid handling production recovery material in an ordinary browsing session. Keep generated exports and backups under the operator's own control. A private browsing indicator is a browser condition, not a complete security audit of the device or deployment.
This content migration does not generate a wallet, test keys, request a signature or transfer funds. For the current merchant flow, the simplest relevant input is an existing public receiving address from your own wallet. For self-hosted work, use the complete Open address-pool and security reference for your version.