Merchant Introduction
Merchants are the backbone of the xPlug payment network any application, business, or decentralized service that accepts payments through the x402 protocol. Within the xPlug ecosystem, merchants operate through xPlug Facilitators, which ensure every transaction is verified, gasless, and securely settled on-chain via Solana.
In simple terms, merchants are the recipients of x402 payments, while xPlug Facilitators act as the trusted relay ensuring all settlements occur transparently and without downtime.
Merchant Role in the xPlug Ecosystem
A merchant interacts directly with two layers:
xPlug SDK or xPlug Pay to create, manage, and verify payment requests.
xPlug Facilitator to relay, validate, and confirm transactions on Solana.
Once a payment request is created through SDK or Pay, it is automatically routed to a Facilitator, which ensures:
The transaction is correctly structured and signed.
Payment tokens are valid and supported (USDC, SOL, or any SPL token).
Settlement occurs trustlessly via the x402
This design eliminates the need for merchants to host or maintain servers, making integration frictionless and verifiable by default.
Onboarding Merchants
To become a merchant in the xPlug ecosystem:
Register / Connect Wallet Merchants authenticate using a Solana-compatible wallet (e.g., Phantom, Solflare). The wallet serves as the merchant’s on-chain identity and payment endpoint.
Define Payment Parameters
Supported tokens (e.g., USDC, USDT, SOL)
Settlement wallet address
Callback or webhook (optional, via SDK)
Facilitator Assignment The merchant’s transactions are automatically routed through an available xPlug Facilitator Node ensuring 99.9% uptime and optimal routing performance.
Start Accepting Payments Once configured, the merchant can start generating verified x402 payment links or integrate directly into their dApp.
Merchant Endpoints (via xPlug SDK)
While xPlug abstracts away complex server-side logic, merchants can still interact with standardized SDK calls:
createPayment()
Creates a new x402-compatible payment request.
verifyPayment()
Confirms that a transaction has been verified by the Facilitator.
getSettlementStatus()
Checks whether funds have been received on-chain.
All SDK methods operate gaslessly, meaning merchants don’t pay network fees Facilitators handle the transaction costs using internal relayers.
Settlement and Receipts
Each successful transaction generates a Settlement Receipt, containing:
Transaction ID
Client wallet
Merchant wallet
Token & amount
Timestamp
Facilitator node ID
On-chain verification hash
These receipts are stored and verifiable on Solana, ensuring that merchants can independently audit all incoming payments.
Last updated