Solana Pay - How It Works, Fees & Reliability (2025)

Q: Do my customers need SOL to pay for gas?

Not necessarily. You can enable a fee relayer so you sponsor the tiny network fee; the customer only approves the invoice amount in USDC .

Q: How fast is the settlement, and what does it cost?

Confirmations are typically seconds . Network fees are usually $0.001–$0.01 per payment; add a small priority fee during busy periods to keep reliability high.

Q: How do I reconcile and keep auditors happy?

Embed a unique reference ID (order/invoice) in each payment, listen for the transaction signature via webhook, mark the order PAID , and store the signature in your system. Optionally, hash your PDF invoice and store the hash for a tamper-evident audit trail.

Q: What should I accept, USDC or other tokens?

Start with USDC on Solana for accounting simplicity and price stability. Add other tokens only if your customers demand them and compliance allows.

Q: How do refunds work without card chargebacks?

On-chain transfers are final , so refunds are a new transfer back to the customer’s address. Tie it to the original reference ID (order number) and log the refund hash for your records.

Solana Pay – Learn Solana Pay in 2025, how it works, fees in USDC, reliability, refunds, and quick setup for merchants with Actions/Blinks & session keys.

Card fees didn’t go away, checkout still fails at the worst possible moment, and settlement delays are a drag on cash flow.

Solana Pay tackles those pain points with a simple idea: let customers pay you directly on-chain, usually in USDC on Solana, with near-instant settlement and tiny network fees.

In 2025–26, the stack has matured: link-to-pay via Actions/Blinks, cleaner human-readable signing, session keys for fewer pop-ups, and better priority fee handling so payments go through even during traffic spikes.

This is your plain-English, merchant-friendly guide to Solana Pay today: how it works, fees, reliability, refunds, compliance, and what to watch before you roll it out.

TL;DR

• Solana Pay lets customers pay merchants directly from a wallet (Phantom, Solflare, etc.) by scanning a QR or tapping a link.
• The site/app generates a transaction (amount, token like USDC/SOL, reference) → user signs in wallet → instant on-chain settlement with tiny fees.
• Merchant verifies the payment using the reference and shows confirmation/fulfillment in real time—no chargebacks.

Comparison Table: Cards vs Solana Pay (2025)

Aspect	Cards (Visa/Mastercard etc.)	Solana Pay
Typical Fees	2–3% + fixed ₹/¢ per txn	Cards (Visa/Mastercard, etc.)
Settlement Speed	T+1 to T+3 banking days	Seconds (final on-chain)
Chargebacks	Yes (issuer-driven)	No chargebacks; rely on refund policy
Refunds	Through the acquirer, fees may not be returned	Merchant-initiated on-chain transfer
Fraud Risk	Card-not-present fraud common	Lower by design; wallet-auth + signatures
Disputes	Card networks & issuers	Merchant support & policy (no network disputes)
Cross-Border	FX + extra fees	Native stablecoins; minimal FX if paid in USDC
Compliance	PCI-DSS, acquirer/KYC	KYC via on/off-ramps; no card data stored
Reconciliation	Batch files from PSP	On-chain tx hash + webhooks/logs
Integration	PSP SDKs, POS terminals	API/SDK + wallet flows; no card hardware
Recurring / Subscriptions	Mature tooling	Possible with session keys/payment links (dev work)
Customer UX	Familiar card form	Cards (Visa/Mastercard, etc.)

What exactly is Solana Pay?

Solana Pay is a checkout rail built on the Solana blockchain. Customers pay you by approving a transfer (most commonly USDC) from their wallet to yours. It can be triggered by:

Scanning a QR code at the point of sale,
Clicking a payment link/button embedded in your website, invoice, email, or social (via Actions/Blinks),
Or via NFC interactions in supported wallets/devices.

Because payments are on-chain, they’re final on confirmation (no chargebacks). Your system can attach a reference ID/memo to the transfer, so you can mark orders as paid and reconcile without chasing screenshots.

Solana Pay, a decentralized, open-source, peer-to-peer payments protocol built on Solana by Solana Labs, is now available to millions of businesses as an approved app integration with Shopify Inc. (NYSE, TSX: SHOP).

The leading global commerce company that provides essential internet infrastructure for commerce.

Solana Pay makes it easy for merchants to get real-time access to their money and greater ability to manage working capital, liquidity, and liability protection.

With no intermediary, Solana Pay eliminates bank fees, chargebacks, and holding times while enabling immediate, direct payment settlement of USD stablecoins compatible with Solana.

“Solana Pay on Shopify opens up millions of merchants to a more dynamic and efficient payment choice.

While consumers get the convenience and increased utility of being able to pay for goods and services with digital dollar currencies from the vast network of merchants using Shopify,” said Josh Fried, Head of Commerce Business Development, Solana Foundation.

An extra benefit for merchants and consumers of using Solana Pay: Payments become a gateway for web3-enabled commerce experiences, including token-gated offers, simple cross-border payments, and NFT-based loyalty programs.

Solana Pay is an open-source protocol built on the decentralized Solana network. Solana’s high transaction speeds, near-zero fees, and sustainability make it an ideal choice for scaling web3 payments while providing a great user experience.

Several brands currently active on Solana have already committed to making Solana Pay a payment option in their Shopify-powered storefronts.

Seeing the opportunity of providing a web3-native payment option for their web3-savvy customers: MonkeDAO, MadLads, Helius, and Solana’s merch store.

The 2025–26 checkout flow (step-by-step)

Create the payment request
Your store generates a payment intent with: amount, currency (usually USDC), recipient address, and a unique reference (order ID). Optional: a small priority fee and a fee relayer setting (so your customer isn’t stuck if fees spike).
Customer scans or clicks
- In-store: They scan your QR; their wallet opens with a human-readable summary (“Pay 24.99 USDC to StoreName for Order #1234”).
- Online: They click a “Pay with Solana” button (a Blink/Action), get the same clean summary, and approve in their wallet or embedded wallet.
Approval & settlement
The wallet approves the transfer. On Solana, confirmations are typically sub-second to a few seconds, even during busy times when you include a small priority fee.
Webhook/callback
Your backend listens for the transaction signature tied to that reference, confirms on-chain inclusion, and then marks the order PAID. You render a success screen and send the receipt.
Receipt & reconciliation
You store the transaction hash + reference. Your accounting can hash the PDF receipt/invoice too and store the hash, creating a verifiable audit trail.

What’s new in 2025–26:

Actions/Blinks let you turn any link or button into a safe payment entry point (no clunky wallet deep-links).
Session keys reduce signature prompts for repeat interactions (handy for subscriptions or in-app purchases).
Human-readable signing makes it obvious to the customer what they are paying for (amount, merchant, item).
Priority fee & relayers smooth out spikes so you don’t lose payments to network hiccups.

Fees, speed, and reliability

Network fee: Usually fractions of a cent (≈ $0.001–$0.01). With a priority fee during peak demand, you’re still typically below one cent.

Card comparison: Cards often cost 2–3% + a fixed fee and settle T+1 to T+3. Solana Pay settles near-instantly with negligible per-transaction cost.

Reliability tips:

Always include a tiny priority fee in your payment intent.
Use a fee relayer if you want to guarantee UX: it tops up the fee on behalf of the payer when the network is busy.
Add a simple retry flow: if the customer closes the wallet, keep the payment intent alive for a few minutes so they can re-open and pay.

What do merchants actually implement?

A. POS / In-store

The tablet/terminal shows a dynamic QR.
Customer scans, approves, and you get a paid signal in seconds.
You print or email a receipt; your POS logs the transaction hash.

B. Web checkout / Link-to-Pay

Add a “Pay with Solana” button powered by an Action/Blink.
The wallet opens (embedded or external), the customer approves, and you mark the order paid via webhook.

C. Invoices & subscriptions

Generate a payment link with the amount + reference.
For subscriptions, use session keys or scheduled payment prompts (still customer-approved; not pull-based like cards).

Refunds, disputes, and customer support

On-chain transfers are final, so there’s no card-like chargeback. Refunds work like this:

Customer contacts support, provides order number/wallet address.
You verify the original transaction hash and status in your system.
You initiate a refund: send a new transfer back to the customer’s address, referencing the original order ID in the memo.

Good practice:

Publish a clear refund policy (timelines, conditions).
Use reference IDs consistently so support can find the original payment fast.
For partial refunds, just send the partial amount back and note it in your system.

Compliance & accounting (practical, not scary)

Tender choice: Most merchants accept USDC to avoid crypto price swings.
KYC/AML: If you operate under strict rules, use allowlists, sanction screening for large tickets, and verifiable credentials (VCs) when relevant.
Invoicing: Generate normal invoices; hash the PDF/JSON and store the hash for a tamper-evident audit trail.
Tax handling: Treat USDC receipts like cash receipts in your base currency using your policy for conversion rates (e.g., oracle rate at payment time). Confirm details with your accountant.

Security & UX best practices

Official SDKs & verified links: Only use trusted libraries and verified Actions/Blinks.
Human-readable signing: Make the payment intent summary crystal clear—amount, merchant, order number.
Phishing controls: Post official links on your site; teach staff to verify the merchant address on screen.
Session keys: For repeat/pay-in-flow experiences, configure tight permissions (amount ceilings, time limits).
Observability: Log every step, payment created, wallet opened, signed, confirmed, with timestamps and transaction hashes.

Where Solana Pay shines

eCommerce & link-to-pay: Email invoices, chat-based checkout, creator storefronts, event tickets.
Point-of-sale: Cafés, pop-ups, venues, fast lines, no terminals locked to acquirers.
Digital products & gaming: Microtransactions that don’t make sense with card fees.
Payouts & marketplaces: Near-instant seller payouts or affiliate splits on confirmation.
Subscriptions with consent: Session-key flows keep friction low without handing over a pull-based card credential.

Common questions (2025–26)

Do customers need SOL for gas?
Not necessarily. With a fee relayer, you can sponsor the tiny network fee so the customer pays only the invoice amount.

What happens if the network is congested?
Include a small priority fee and keep your intent alive for retries. Solana’s recent fee-market + QoS upgrades make payments reliable even during spikes.

Can I accept other tokens?
Yes, but USDC is the default for accounting simplicity. You can offer others if they fit your business and regulations.

How fast do I get the money?
Usually, seconds to confirmed receipt. Funds live in your business wallet immediately.

What about chargebacks?
On-chain transfers are final. You handle disputes with a clear refund policy and manual refunds.

Risks & how to manage them

Stablecoin policy risk: If you accept USDC, stay current on issuer/regulatory updates. Keep balances reasonable and sweep if policy changes near you.
Staff training: Teach staff to check the merchant name, amount, and order ID on screen and to verify confirmation before handing over goods.
Customer UX variance: Not every wallet is equal. Offer a short “how it works” tooltip and test with the wallets your audience uses.
Key management: Use hardware-backed or custodial business wallets with role-based access and approvals for larger transfers.

A quick deployment checklist

Choose USDC as the primary tender; add alt-tokens later if needed.
Implement Actions/Blinks for web + QR for POS.
Include priority fee and consider a fee relayer.
Add reference IDs and webhook confirmation for reconciliation.
Publish refund policy; train support.
Set up observability (logs, alerts) and daily sweeps to treasury.
Test with 10–20 real payments before announcing widely.

🔑 Key Takeaways

Solana Pay cuts transaction fees from ~2–3 % on cards to fractions of a cent, making micro-payments practical.
Payments settle instantly on-chain—no T+2 banking delays or chargeback risk.
Merchants keep control of refunds and reconciliation through on-chain records and webhooks.

*For educational purposes only. Always review current network fees and compliance requirements before integration.*

Conclusion

Solana Pay is finally merchant-grade. In 2025–26, customers can scan or click, approve a USDC transfer, and get near-instant settlement with fees that round to zero.

With Actions/Blinks, session keys, priority fees, and simple refund workflows, it feels like modern web checkout, minus 2–3% card charges and multi-day settlement.

Start small, use USDC by default, add a tiny priority fee, and log every payment with a reference ID. If payments touch your margins (they do), a Solana Pay pilot is worth doing now.

FAQs

Do my customers need SOL to pay for gas?

Not necessarily. You can enable a fee relayer so you sponsor the tiny network fee; the customer only approves the invoice amount in USDC.

How fast is the settlement, and what does it cost?

Confirmations are typically seconds. Network fees are usually $0.001–$0.01 per payment; add a small priority fee during busy periods to keep reliability high.

How do I reconcile and keep auditors happy?

Embed a unique reference ID (order/invoice) in each payment, listen for the transaction signature via webhook, mark the order PAID, and store the signature in your system. Optionally, hash your PDF invoice and store the hash for a tamper-evident audit trail.

What should I accept, USDC or other tokens?

Start with USDC on Solana for accounting simplicity and price stability. Add other tokens only if your customers demand them and compliance allows.

How do refunds work without card chargebacks?

On-chain transfers are final, so refunds are a new transfer back to the customer’s address. Tie it to the original reference ID (order number) and log the refund hash for your records.

Table of Contents