For the first time, you can build a website and accept stablecoin payments from anywhere in the world in about ten minutes using AI. There is no payment processor account to open, no KYB, and no rejection because your business is located in a country the processor does not support. This is why Request Network exists. Funds move freely, from your customer’s wallet straight to yours, with no one in between.

We built two ready-to-use prompts to get you there. One that builds a brand new e-commerce website, and one that adds crypto payments to an app you already have.

By the end of this guide, you will have a live e-commerce website that accepts stablecoin payments on Ethereum, Base, Polygon, Arbitrum, BNB, Optimism and Tron. We built one to prove it: see the demo sticker store live. Everything is free, and the whole setup takes under ten minutes.

Before you start

You need two things:

• A wallet to receive the funds. If you do not have one, set up a crypto wallet in about ten minutes.
• And a free Lovable account.

Step 1: Connect your wallet and create your payment destination

Go to the Request Network dashboard, choose whether you want to accept stablecoins on EVM chains or on Tron, and sign in with your wallet.

Then on the home page click on set up your payment destination. By default, the wallet address is the one you connected with. Pick the chain and the token you want to receive funds on. In this example, we picked USDC on Base.

Activate wallet screening with one of the available providers. Every payer’s wallet is checked before a payment is initiated, which keeps you from doing business with bad actors.

Step 2: Paste the prompt into Lovable

For this guide, we wrote a prompt that builds an e-commerce website on Lovable to sell stickers. Download the prompt, copy it as is or adapt it to your own use case, then paste it into Lovable and let it build.

Alternatively, if you want to add crypto payments straight into your existing app, download this prompt and paste it into your AI app builder, whether you’re using Claude Code, ChatGPT, Cursors. All the steps remain the same.

Step 3: Create your Client ID and Destination ID

Back in the Request Network dashboard, click Manage under your receiving route. Scroll down, click Generate New Client ID, add a name, and generate.

Once generated, click View to copy your client ID and destination ID.

Paste the Client ID and the Destination ID into the secure fields in Lovable.

Step 4: Publish your website

When the build finishes, publish your website from Lovable. It is now live.

Step 5: Register your webhook

After publishing, Lovable gives you a webhook URL. Copy it. 

Return to the Request Network dashboard, click Manage under your receiving route, scroll down, and click Add Webhook. Select the Client ID you created, paste the webhook URL, and create the webhook.

The dashboard then shows a webhook signing secret. Copy it.

Paste it into the secure field in Lovable. This secret proves that payment confirmations come from Request Network and not from someone pretending to be it.

Step 6: Test your first stablecoin payment

Open your website, add a product to your basket.

Open your basket and click pay with crypto.

You land on the Request Network secure payment page. Connect your wallet, select the chain and token you want to pay with, and click Pay.

Watch the transaction go through, and see the payment confirmation.

You can click on the block explorer icon to see the transaction on the blockchain.

Open the Request Network dashboard. Your transaction is there, with the status set to Paid.

Click on the transaction to see all the details and the wallet screening audit.

Want to test it properly? Run these four scenarios:

• Same chain, same token. Your receiving route is USDC on Base; pay with USDC on Base. The simplest case covered in this blog post.
• Same chain, different token. Pay with USDT on Base. The protocol swaps for you.
• Cross chain, same token. Pay with USDC on Ethereum. The protocol bridges for you.
• Cross chain, different token. Pay with USDT on Ethereum. The protocol bridges and swaps for you.

In every scenario, you (the merchant) receive USDC on Base while your customers don’t have to manage bridging, swapping or gas fees.

Why your customer pays no gas

You will notice something during testing: on the six EVM chains and on Tron, the payment asks for no gas.

Normally, every blockchain transaction costs gas, a small fee paid in the native token of the chain the payer transacts on. It is what pays the network to record the transaction, and it is the classic point of friction in crypto payments. A customer holding 50 USDC but zero ETH cannot pay you, because they cannot cover the gas.They have to buy ETH, and often they drop at this stage.

Request Network removes that step. Anyone holding stablecoins can pay you, without having to hold other token to pay for gas. This applies to the six EVM chains and on Tron.

Accept stablecoin payments from anywhere in the world

Anyone holding stablecoins on Ethereum, Base, Polygon, Arbitrum, BNB, Optimism, or Tron can pay you, which covers 95% of global stablecoin supply. Customers pay with what they hold, you receive the token on the chain you chose. Whether your customers are in Japan, the US, France or more restricted countries not supported by traditional payment processors like Nigeria, Pakistan, Egypt, Morocco, it makes no difference, they can all pay you.

Want to see what that feels like from the customer’s side? see the demo sticker store live and pay for a sticker from whichever chain you like.

Going further

The full documentation is available at docs.request.network. And if you want to get paid in stablecoins without building a website at all, generate payment links straight from the dashboard.

AI coding assistants have made building software fast. You can describe a tool, watch Claude or Cursor generate the repository, and have a working application running locally inside an hour. The friction begins when you try to collect your first payment.

Request Network removes this barrier with an open payment protocol that goes live immediately. Anyone can accept capital from anyone, wallet-to-wallet, with no platform authorization or contract negotiations required. Receiving international payments becomes a single prompt and a few clicks away.

Direct payments and simple fees

Request Network is a direct payment system with no middleman. No bank or payment corporation holds your money before it reaches you. When a customer buys your product, they can pay using their preferred digital currency. The money lands directly in your account, and the system automatically updates your database to show who paid — removing the need for manual tracking.

The cost structure is straightforward:

• Processing costs are a flat 0.9% per transaction, capped at $500 per payment.
• There are no monthly platform fees.
• There are no upfront setup fees.
• There is no minimum sales volume required.

You can start collecting revenue without signing contracts, creating corporate accounts, or submitting identity verification paperwork. While the setup requires no bureaucracy, the system runs automated security and compliance checks in the background. This design protects your wallet from high-risk accounts without creating delays for your customers.

So, let’s get started.

Integrate Request Network with a single prompt

Copy and paste this exact prompt into Claude, Cursor, Lovable or ChatGPT to integrate stablecoin payments in less than 10 minutes:

Request Network stablecoin payments — integration prompt

Step 0 — Detect the environment. Before writing anything, identify which of these this project is, since "server endpoint" means something different in each:

- A. Conventional server app — has its own backend framework (Express, Django, Rails, Next.js API routes, etc.) and a database you control. Implement normal server routes.
- B. AI-agent-managed site — a CMS/site edited by an agent via API-level access, with no dedicated app server (e.g. WordPress via REST + Code Snippets). Use that platform's own extensibility mechanism as the "endpoint" — e.g. a custom REST route registered in a snippet — instead of assuming a server that doesn't exist.
- C. No-code/low-code builder (Lovable, Bubble, Webflow, Replit Agent, etc.) — use that platform's own backend primitive (Lovable Cloud/Supabase edge functions, Bubble backend workflows), not a conventional file-based backend.

If none of these cleanly fits, ask before picking a default.

1. Checkout endpoint (any environment). Expose one endpoint/function via whatever mechanism the environment provides. It must run server-side — the client never sees the client ID or secret. It accepts { amount, referenceId } and calls https://api.request.network/v2/secure-payments with:
- requests: [{ destinationId: RN_DESTINATION_ID, amount: String(amount) }]
- redirectUrl: this site's URL with ?paid=1 appended
- redirectLabel: label for RN's "go back" button
- webhookUrl: this environment's webhook endpoint (below)
- reference: referenceId, only if provided
- Header x-client-id: RN_CLIENT_ID

Returns { url: data.securePaymentUrl }.

2. Webhook receiver (any environment). Expose a second endpoint/function that:
- Reads the raw, unparsed body. In frameworks that auto-parse JSON (Express, etc.), exempt this route from that middleware. In environments where the raw body is always available regardless of parsing (e.g. WordPress's WP_REST_Request::get_body()), skip that workaround entirely — check what your environment actually does first.
- Verifies x-request-network-signature against HMAC-SHA256(RN_WEBHOOK_SECRET, rawBody) with a constant-time comparison (crypto.timingSafeEqual / hmac.compare_digest / hash_equals, per language) — strip a sha256= prefix if present.
- Responds 200 immediately; defers processing where the environment supports it (fastcgi_finish_request(), a queue/background job); where it doesn't, keep the post-response work trivial rather than blocking on it.
- Parses totalAmountPaid, currency, txHash, network, paymentReference, explorer (a ready-made explorer link — use it directly, don't rebuild it).
- Logs/handles the payment in whatever this environment's actual persistence layer is (its database, a custom table, a CMS custom post type, a no-code data collection) to update order/access status.

3. Frontend checkout widget. Using the project's existing stack and styling only — no new framework or dependency:
- Floating action button → checkout modal.
- Preset amount chips (e.g. $5/$10/$25), one active by default; typing a custom amount clears chip selection.
- Optional reference/description input, max 120 chars.
- Submit calls the checkout endpoint, opens the returned url in a new tab, closes on success, shows inline error otherwise.
- Closes on backdrop click, close button, and Escape.

4. Frontend success confirmation. On load, if ?paid=1 is present, show a thank-you message; on dismissal, strip the param via the environment's history/URL API without a full reload.

Secrets. RN_CLIENT_ID, RN_DESTINATION_ID, RN_WEBHOOK_SECRET — store in whatever this environment's real secret surface is (.env + server env vars, the CMS's snippet/constant, the no-code platform's secrets panel). Never paste real values into the agent conversation.

CSP. Only relevant if a CSP header already exists and the browser calls api.request.network directly. If the call is proxied through your own server/function (required anyway, to keep the client secret off the client), the browser never talks to that host and no CSP change is needed.

Before writing code: state which environment (A/B/C) this is, the concrete "endpoint" mechanism for it, and where the three secrets will actually live — then wait for confirmation, since this wires up real payment collection.

Constraints: match existing language/framework/styling conventions, no new frontend dependency, no unnecessary comments, the redirect field is redirectUrl not returnUrl.

Connect your Wallet to the Request Network Dashboard

While AI is integrating Request Network, you can generate the environment keys needed to accept and send Stablecoins.

How to generate your environment keys

You need to copy three IDs and paste them into your server environment file:

• RN_DESTINATION_ID
• RN_CLIENT_ID
• RN_WEBHOOK_SECRET

First, your RN_DESTINATION_ID is your public wallet address where your business revenue will land. If you do not have an address ready, follow our step-by-step setup manual: How to set up your first crypto wallet.

Go to dashboard.request.network › Connect your Wallet › ⧉ Symbol

Second, you need your unique client credentials. Create a new Client ID from the dashboard screen. The portal generates your project identifier string immediately. Copy this text block and paste it into your server environment file as RN_CLIENT_ID.

Go to dashboard.request.network › Connect your Wallet › Manage Receiving Route › Generate new Client ID

Third, navigate to the webhook settings section inside that same project panel. Enter your active server endpoint URL (for example, https://yourdomain.com/webhook/payment). The system generates a cryptographic signing secret used to verify incoming transaction notifications. Copy this string and add it to your environment file as RN_WEBHOOK_SECRET.

Go to dashboard.request.network/manage-destination › + Add Webhook › Enter your Endpoint URL & Create Webhook

Moving your deployment to production

Your AI assistant will generate the backend endpoints and frontend interface files immediately, matching your project’s existing stack and conventions.

To take the code live, add your variables to your production environment file. Your destination identifier is your public crypto wallet address. If you need to generate a secure address for this configuration step, review our onboarding manual: How to set up your first crypto wallet.

Once your keys are set, your checkout button is ready to process global digital dollars. For alternative configurations and multi-token setups, review the official Request Network use cases documentation.

Your software application is now equipped to capture global revenue directly.

What a crypto wallet is

A crypto wallet works a lot like a bank account. It’s where you receive money, hold it, and pay from. Businesses use wallets to collect and send payments in stablecoin from customers around the world. Individuals use them to send and receive money, from splitting a bill to paying an invoice globally.

There’s one big difference from a bank account. Nobody sits in the middle. You open a wallet in minutes, without paperwork or approval, and you’re the only person who controls the money in it.

In practice, a wallet is an app. It can live on your phone, in your computer’s browser, or both at once. You’ll be sending and receiving money from it the same day you create it.

Before you start

There are many wallet providers, the same way there are many banks holding your accounts. For this guide, we deliberately picked MetaMask and Trust Wallet because we consider them the most widely used and the most reliable. They are equally secure and take the same few minutes to set up. The only real difference is that Trust Wallet supports Tron and MetaMask does not. Tron is widely used for USDT payments, so if you expect to be paid that way, pick Trust Wallet.

Both wallets come as a browser extension for your computer and as a mobile app, and choosing between them is not a commitment. You create your wallet once. After that, you connect each device you want to use to the wallet you created, the extension at your desk, the app in your pocket, or both.

Which wallet to pick

There are many wallet providers, the same way there are many banks. You pick one, open an account, and you’re set. This guide uses MetaMask and Trust Wallet because they’re two of the most established and widely used wallets, they’re free, and both work with Request Network out of the box. You can browse the full list of supported wallets on the Request Network dashboard.

One warning before you start. Fake wallet apps circulate through search ads and unofficial links, and they’re built to steal funds. Use the links below, type the addresses yourself, or use the verified download links inside the Connect Wallet window on the Request Network dashboard. Never install a wallet from an ad.

Set up MetaMask

MetaMask covers the six main EVM networks: Ethereum, Base, Polygon, Arbitrum, BNB, and Optimism. Pick the desktop or mobile flow below.

On desktop

1. Install the extension. Go to metamask.io and add the extension for Chrome, Brave, Firefox, Opera or Edge.

2. Create a new wallet. Click the MetaMask icon in your browser toolbar (top right of your browser) and select create a new wallet.

3. Choose how to secure it. MetaMask offers two options: a Secret Recovery Phrase, or a social login through Google, Apple, or Telegram. The recovery phrase is the standard method, and the one this guide recommends: a sequence of 12 words that acts as the master key to your wallet. Social login exists for people who prefer signing in with an account they already have. Either works with Request Network.

4. Set your password. Create a password for opening the extension on this computer. Done. You have a wallet.

5. Write down your recovery phrase. MetaMask shows you the 12 words. Write them on paper, in order, and store the paper somewhere safe. Then confirm the words in sequence when prompted.

On mobile

1. Install the app. Go to metamask.app.link, which routes you to the official App Store or Google Play listing.

2. Create a new wallet. Open the app and select Create a new wallet.

3. Choose how to secure it. MetaMask offers a Secret Recovery Phrase or a social login through Google, Apple, or Telegram. The recovery phrase is the standard method and the one this guide recommends: 12 words that act as the master key to your wallet. Either works with Request Network.

4. Set your password. Create a password for opening the app on your mobile. Done. You have a wallet.

5. Write down your recovery phrase. If you picked the “Use Secret Recovery Phrase” option in step 3, write it on paper when the app shows it, then confirm the words in the order requested. This confirmation step proves you recorded the phrase correctly.

6. Turn on Face ID or fingerprint login. Recommended. Follow the prompt during setup, or turn it on later in Settings › Security and Privacy › Device Authentication. From then on, your face or fingerprint opens the app instead of your password.

Chose social login? If you want your recovery phrase on paper anyway (recommended), open MetaMask and go to Settings › Security and Privacy, then select Reveal Secret Recovery Phrase. Do this in private, and write the words on paper only.

Set up Trust Wallet

Trust Wallet covers the six main EVMs and Tron, which makes it the pick if you expect USDT payments over Tron. Pick the desktop or mobile flow below.

On desktop

1. Install the extension. Go to trustwallet.com and add the extension for Chrome, Brave, or Firefox.

2. Create a new wallet. Open the extension, accept the policies, and click Create a new wallet.

3. Secure it. Choose fingerprint recognition or a password. You’re all set — click open your wallet to open the extension showing your balance.

On mobile

1. Install the app. Go to trustwallet.com, which routes you to the official App Store or Google Play listing.

2. Create a new wallet. Open the app and select Create new wallet.

3. Secure it. Set a 6-digit passcode, and turn on Face ID to secure your wallet.

4. Back up your recovery phrase. Tap your wallet icon at the top left, select Back up manually, and accept the warning checkboxes to view your recovery phrase. Write the words on paper in order, then confirm their placement. This confirmation step proves you recorded the phrase correctly.

Protect your wallet

Your bank secures your account with a PIN, a password, and two-factor login. If you forget them, a reset link or a phone call fixes it. Your wallet works differently, and this is the one thing to understand before you receive your first payment.

When you created your wallet, it gave you a recovery phrase: 12 or 24 words in a fixed order. That phrase is the master key. Anyone who has it controls the money. Anyone who loses it, and loses access to their device, loses the wallet. There is no reset link, because there is no company in the middle to send one. That’s the trade for full control.

The good news: protecting it comes down to three habits.

1. Write the phrase on paper, in order, and store it somewhere safe. A drawer at home works. A safe is better.
2. Never store it digitally. No screenshots, no photos, no text files, no cloud folders, no password managers. Automated scripts scan the internet for exposed phrases and drain the wallets they find.
3. Never share it. No legitimate company, including Request Network and your wallet provider, will ever ask for your recovery phrase. Anyone who asks is trying to rob you.

Do those three things and your funds stay safe.

One last piece of context. The wallet you created in this guide is a software wallet: an app that stays connected to the internet, which is exactly what makes it convenient for everyday payments. As your balance grows, you can add a hardware wallet, a small physical device that keeps your keys offline, for the funds you don’t touch often. Think current account and savings account. You don’t need one today.

Connect your wallet to Request Network

Your wallet is ready. The last step links it to Request Network so you can start accepting and sending crypto payments.

1. Open the dashboard. Go to dashboard.request.network, select EVM or Tron, and click Connect Wallet.

2. Choose your wallet. Select MetaMask or Trust Wallet from the list.

3. Confirm in your wallet. A window from your wallet opens automatically. Click Connect, then sign the request. Signing proves you own the wallet. It never moves any funds.

4. Access the dashboard. Once you’ve signed, your dashboard opens with your wallet connected. From here you choose your receiving route by selecting the network and asset you want to accept payments in, and you’re ready for your first payment.

Frequently asked questions

Does a crypto wallet cost anything?

No. Creating a wallet is free, and there’s no monthly fee, minimum balance, or paperwork. You only pay small transaction fees when funds move, similar to a bank’s transfer fee — and on the six main EVM networks, Request Network payments are gasless, so your payer covers nothing extra either.

Is it safe to share my wallet address?

Yes. Your address works like an IBAN: people need it to pay you, and knowing it doesn’t let anyone touch your funds. The only thing you must never share is your secret recovery phrase.

Can I use the same wallet on my phone and my computer?

Yes. Install the app on one device and the extension on the other, then import your wallet with your secret recovery phrase. Both stay in sync because they’re two doors to the same account.

What happens if I lose my phone?

Your money isn’t on the phone, it’s on the network. Install your wallet app on a new device, enter your secret recovery phrase, and everything reappears. This is why the paper backup matters: it’s your way back in.

What if I lose my recovery phrase?

As long as you still have access to a logged-in device, open your wallet settings and reveal the phrase again, then write it down. If you lose both the phrase and every logged-in device, the wallet can’t be recovered. No one can reset it for you, which is the trade for no one being able to freeze it.

Do I need a different wallet for each cryptocurrency?

No. One wallet holds many assets. MetaMask covers everything on the six main EVM networks, and Trust Wallet adds Tron on top. You’d only add a second wallet for a network your first one doesn’t support.

MetaMask or Trust Wallet: which one should I pick?

Both are free, established, and work with Request Network. The deciding question is Tron: if you expect USDT payments over Tron, pick Trust Wallet. If you’ll operate on the EVM networks only, either works.

Can Request Network access the funds in my wallet?

No. Your funds go directly from your payer’s wallet to yours. Request Network never holds them, and connecting your wallet to the dashboard only lets you manage payments — never move funds without your signature.