x402 Payments on NEAR with Solvador

Accept x402 payments on NEAR with Solvador

If you want to accept x402 payments on NEAR, you need a facilitator to verify and settle them. Solvador is that facilitator.

You point your x402 middleware at Solvador, keep pricing in plain USD, and we handle verification and on chain settlement on NEAR. The same integration also covers every other network we support, so you write it once and reuse it everywhere.

The exact scheme on NEAR

Solvador supports the x402 exact scheme on NEAR:

• exact. Charge a precise, fixed amount per request. Ideal for flat priced endpoints, one off unlocks, and simple pay per call APIs.

The upto and batch-settlement schemes rely on EVM primitives such as Permit2, so they run on Solvador’s EVM networks. On NEAR you use exact, and the rest of the integration is identical to every other network Solvador supports.

One integration, every network

The real cost of going multichain is not the payment, it is the infrastructure behind it. Solvador collapses that:

• Integrate once and cover NEAR plus 14 other networks through the same facilitator.
• No per network facilitator to run, monitor, or maintain.
• Adding NEAR to an app that already uses Solvador is a config value, not a rewrite.
• Identical developer experience across every supported network, so your team learns it once.

You price in USD, your users pay in stablecoins, and Solvador settles on NEAR.

From zero to first payment in under 3 minutes

Frictionless onboarding is the point. Here is the whole path from nothing to a live 402 payment on NEAR.

1. Grab your Solvador API key.

Create a key in your Solvador dashboard and keep it in an environment variable. You will pass it to the facilitator on every verify and settle call.

export SOLVADOR_API_KEY="your_api_key"

2. Add the x402 middleware to your server.

npm install @x402/express @x402/core @x402/near

3. Point it at Solvador and pick NEAR.

import express from "express";
import { paymentMiddleware, x402ResourceServer } from "@x402/express";
import { HTTPFacilitatorClient } from "@x402/core/server";
import { ExactNearScheme } from "@x402/near/exact/server";

const app = express();

const facilitator = new HTTPFacilitatorClient({
  url: "https://api.solvador.com",
  createAuthHeaders: async () => {
    const auth = { "X-API-Key": process.env.SOLVADOR_API_KEY };
    return { verify: auth, settle: auth, supported: {} }; // /supported is public
  },
});

app.use(
  paymentMiddleware(
    {
      "GET /api/premium": {
        accepts: [
          {
            scheme: "exact",
            price: "$0.05",
            network: "near:mainnet", // NEAR
            payTo: "your-account.near", // NEAR account ID
          },
        ],
      },
    },
    new x402ResourceServer(facilitator)
      .register("near:mainnet", new ExactNearScheme())
  )
);

app.get("/api/premium", (req, res) => {
  res.json({ data: "paid content on NEAR" });
});

app.listen(3000);

4. Make a paid request from any x402 client.

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactNearScheme } from "@x402/near/exact/client";

// signer is a NEAR account
const client = new x402Client();
client.register("near:mainnet", new ExactNearScheme(signer));

const fetchWithPay = wrapFetchWithPayment(fetch, client);
const res = await fetchWithPay("http://localhost:3000/api/premium");

That is it. Your endpoint now returns 402 Payment Required, the client pays in stablecoins, Solvador verifies and settles on NEAR, and your content is served. No per network glue code, no facilitator to operate.

Why NEAR

NEAR is a sharded Layer 1 with roughly one second blocks, fast finality, and fees that cost a fraction of a cent, running one of the largest daily active user bases in crypto. Accounts are human readable names like alice.near instead of hex strings, which makes receiving addresses easy to manage, and the protocol’s chain abstraction and intents stack has made NEAR a primary home for AI agents. That makes it a natural fit for high frequency x402 payments, pay per call APIs, and agent driven services.

Whatever brought you to NEAR, Solvador makes it a payment ready network from day one, with the exact same developer experience you get everywhere else we support.

FAQ

Which x402 schemes does Solvador support on NEAR? Solvador supports the exact scheme on NEAR. The upto and batch-settlement schemes rely on EVM primitives such as Permit2, so they are available on the EVM networks Solvador supports.

How long does integration take? Most developers go from install to their first live payment in under 3 minutes. It is a middleware install plus one config value.

What tokens can I accept on NEAR? NEP-141 fungible tokens, including native USDC on NEAR. Confirm the current asset list for NEAR in the Solvador docs before launch.

Can I use the same code on other networks? Yes. Switching networks is a config change. The same Solvador integration covers every supported network.

Start building on NEAR

Ship your first x402 payment on NEAR today. Read the docs and grab your facilitator endpoint at solvador.com.