You have agreed a price with a customer. The next step should be a clear payment request beside that offer—not a message containing a wallet address with the amount, network and next steps scattered elsewhere.
A PayIn payment link can be placed in an ordinary website link, a quotation or an invoice message. The customer opens a hosted request and follows the supported wallet flow. Your business still needs to associate the receipt with the right order before delivery.
AI-generated concept illustration. The shop page and payment screen are fictional, not product screenshots or a working store integration.
Choose what the link is collecting
For a specific deposit or single-price service, a fixed amount can make the request easier to understand. For varying totals, a customer-entered amount can be useful when you clearly communicate the agreed amount and verify it afterward.
Use a recognizable title, such as the business or service name. Show the price in USDC, accepted networks and what happens after payment in your own offer. Customers need a compatible wallet and supported USDC on an enabled network; the link is not a card checkout or an automatic conversion from any token.
Create the setup through PayIn's payment-link entry. Prepare the receiving networks and save the private management link. For the form and handoff screens, follow the creation tutorial.
Copy the public Payment link
Open management and choose Links. Copy Payment link, which is intended for customers. Do not copy POS display access or the private management URL into your website.
The same receiving setup has separate links because the customer request, counter feedback and merchant settings serve different jobs. Test the public link in a separate browser tab: it should show the intended request, never your management controls.
Add a website button using an ordinary link
In your website builder, add a button or text link and paste the copied public URL as its destination. A merchant-controlled product page could say:
Workshop deposit: 30 USDC. Pay using an accepted network. We confirm your booking after matching the completed payment to your registration.
That is an illustrative offer, not a PayIn ticketing feature. Publish your own delivery, cancellation and refund terms alongside the request.
For an HTML page, the basic shape is:
<!-- Replace PUBLIC_PAYMENT_URL with the copied public Payment link. -->
<a href="PUBLIC_PAYMENT_URL">Pay the deposit in USDC</a>
Do not publish the placeholder. Use the complete URL supplied by management and a label that explains what the customer is paying for. Management's Integrations section also provides a downloadable website-button snippet; inspect its destination before placing it on your site.
A link does not require embedding an API secret in the page. Keep management credentials, callback secrets and wallet recovery material out of HTML and client-side scripts.
Place it where the customer can understand the offer
A service seller can put the button beneath the agreed deposit terms. A freelancer can include the public link in the same email as the invoice. A shop can use a clearly marked USDC payment option where it fits its existing order process.
On a small phone screen, keep the amount and important conditions close to the action. Avoid a generic “Pay” button that sends someone to a request with no explanation of the asset or network.
If your existing ecommerce platform controls checkout, adding a link does not make it a native PayIn integration or automatically update its order status. Use the platform's supported customization options and decide how your staff will reconcile the separate payment.
Decide how an order becomes paid
For a small number of orders, manual matching may be sufficient. Retain your invoice or order reference and compare it with a completed receipt in management. A shared link does not automatically identify which invoice each payer meant to settle.
For automation, your system needs an explicit order-to-payment relationship and verified server-side results. A return URL helps the customer navigate back; a completion callback can support processing on your server. Neither creates an order system by itself. Read callbacks versus redirects before enabling fulfillment.
Do not treat a click on the button, a wallet connection or a visit to your success page as a paid order.
Check the page before sharing it
Open the actual published button on desktop and phone. Confirm the public destination, title, amount mode and enabled networks. Check that your offer explains who to contact if the payment is unclear. These navigation checks do not require a wallet signature or a real payment.
If you change the receiving setup or replace the public link later, retest every website and invoice template that uses it. For printed or in-person requests, follow the payment QR guide.
PayIn is currently free to create and use without registration. External wallet, network and conversion costs can still apply, and current pricing is not a permanent guarantee.
Create a USDC payment link after deciding how it fits your offer and order records.