PayIn provides a payment page for receiving USDC directly to your chosen wallet. PayIn QR is the counter workflow; PayIn Link is the same payment request shared across your sales channels. You do not open a PayIn merchant balance or buy USDC to create a request.
Prepare your receiving wallet
Choose Base, Polygon or Solana in the creation form, then copy the public receiving address from a wallet you control. An EVM address can look identical across networks; its format does not establish that you chose the right network or own it. Verify the network in your wallet before publishing a request. Customers need USDC on that same network and a compatible wallet.
Use the Receive function in your wallet. Never paste a private key, seed phrase or recovery words into a PayIn creation form. PayIn cannot recover a lost wallet. Keep the recovery information in your own secure process. Creating a request is separate from approving a customer payment.
Create one request, choose how to use it
Open Create a counter QR for a shop, market stall or event check-in. Use Create a payment link for a website, event page, message or email. Both produce the public payment link and a counter display for the same receiving setup.
Enter a recognizable business name. Choose a fixed USDC amount or let customers enter an amount. A fixed amount is useful for a particular offer; a customer-entered amount is useful when the total varies. The creation form accepts decimal amounts from0.01 to1,000,000, with at most six decimal places. This validation does not guarantee that a customer has sufficient funds or that every network transaction will succeed.
Review the full address, network, name and amount before creating. Changing a receiving address later affects where new customers should pay; it does not move previously received funds. Check the resulting public page before putting the link on a sales channel.
Save private management access
The result includes a public link and private management access. Share the public link or QR with customers. Save the private management link and backup separately. Anyone with management access may be able to operate the request; do not print it on the counter, include it in customer emails or add it to public analytics.
The website asks you to confirm that you saved management access before proceeding. Copy confirmation appears only after the clipboard operation succeeds. If clipboard access is unavailable, select and copy the value manually. There is no account-based recovery promise for a lost management credential.
Receive and check a payment
Customers review your business name, amount and network, then approve in a compatible wallet. A signature alone is not proof that the payment arrived. Check your payment record, amount and transaction before handing over goods, confirming entry or starting work. If the outcome is unclear, investigate the existing attempt before asking the customer to pay again.
A counter display can provide sound or spoken amounts on a supported foreground device. Test it on the device you intend to use. Background tabs, lock screens and browser permissions affect delivery; do not rely on sound as your only payment check. A shared payment link does not automatically identify a specific order, ticket or item.
Know the boundaries
PayIn currently exposes Base, Polygon and Solana USDC payment capabilities. Wallet adapters and network services still matter. The Solana path stops before signing when a receiving token account is missing; first-account creation and its cost are not automatically handled. Fees and confirmation time vary. The website's approximate two-second observation measures wallet confirmation to the payment-success screen in prior tests, not a guaranteed settlement time.
Refunds are separate transfers arranged with the customer. PayIn does not provide a merchant balance from which to reverse a transaction. For operational setup, read the receiving guide; for customer instructions, use the payment guide.