An enabled store and a payment link you can test.
1. Create a project
Click Create project and enter a name. Projects separate wallets and business settings. Choose your reporting currency and timezone in the project settings.
A new project does not create a store. Locally supported wallets are prepared for the project; Monero needs a separately connected view-only wallet. Keep the project paused while you finish setup.
2. Back up the wallets
Open Project → Wallets → Backup all. Choose plain text or the single-file HTML backup with search and QR codes. Both contain private information and are not encrypted. Store them offline in a secure place, separate from the VPS.
Check the backup includes the chains you plan to use. Recovery words may not immediately show every invoice address in another wallet. Keep the address/derivation details too. A wallet export does not replace a full application/database backup.
3. Add your first store
Open Project → Stores → New store and enter its name. The identifier is generated automatically. In Basic, review its status and the active domains to use for checkout/API links.
Use one store for one checkout policy or shop. Add more when branding, accepted methods or invoice defaults differ. The default store’s appearance can be reused by later stores.
4. Choose payment methods
In Store → Payment methods, enable the chains you need, then select the native coin and supported tokens for each. For USDC or USDT, check both the network and contract/mint. A ticker alone does not identify a token.
The catalog first loads a smaller batch, then fills up to 3,000 assets. A catalog match is not automatic acceptance. Check the 30-chain guide before adding methods.
Under Invoice, review fiat currency, expiry, confirmations, spread and underpayment tolerance. Tolerance changes settlement acceptance; the checkout still requests the full quoted amount. Zero confirmations trades safety for speed.
Under Checkout, add a logo, colors and customer text, then open the hosted preview. The preview is not a real payable invoice.
5. Create a manual invoice
Enable the store and project once the setup checks are complete. Open Project → Invoices → Create invoice, choose your store and enter a positive amount, for example 10 EUR.
Add an order ID, email and customer details if you need them. Metadata can hold your own order references. Leave payment methods on store defaults, or narrow them for this invoice.
Open checkout from the new invoice. Share that link with the customer. They choose a listed chain/asset and send the displayed crypto amount to the displayed address, including any required tag, memo or comment.
6. Verify the first payment
Test with a small amount that still covers network fees. Processing means a payment is detected but not yet settled. Wait for settled and check any Needs attention flags before fulfilling the order.
Invoice Details shows the chosen asset, transaction, customer details and metadata. Use its explorer link to compare the transfer. A return-to-merchant redirect is not payment proof.
If detection is delayed, check the selected chain’s scanner status. Do not ask the customer to pay twice. Use verified IPN/webhooks when you automate order handling.