Infraestructura

Solana Pay

An open payment standard and SDK that defines URI schemes and protocol flows for requesting SOL or SPL token transfers and for constructing and returning partially-built transactions from merchant backends to user wallets. It comprises two sub-protocols — Transfer Requests (simple static payment URIs) and Transaction Requests (dynamic server-signed transaction fetching) — and enables point-of-sale payments, loyalty programs, and interactive commerce experiences using QR codes or deeplinks.

IDsolana-pay

Lectura rápida

Empieza por la explicación más corta y útil antes de profundizar.

An open payment standard and SDK that defines URI schemes and protocol flows for requesting SOL or SPL token transfers and for constructing and returning partially-built transactions from merchant backends to user wallets. It comprises two sub-protocols — Transfer Requests (simple static payment URIs) and Transaction Requests (dynamic server-signed transaction fetching) — and enables point-of-sale payments, loyalty programs, and interactive commerce experiences using QR codes or deeplinks.

Modelo mental

Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.

Piensa en esto como un bloque de construcción que conecta una definición aislada con el sistema mayor donde vive.

Contexto técnico

Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.

RPCs, validators, snapshots, indexación y plumbing de red.

Por qué le importa a un builder

Convierte el término de vocabulario en algo operacional para producto e ingeniería.

Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.

Handoff para IA

Handoff para IA

Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.

Solana Pay (solana-pay)
Categoría: Infraestructura
Definición: An open payment standard and SDK that defines URI schemes and protocol flows for requesting SOL or SPL token transfers and for constructing and returning partially-built transactions from merchant backends to user wallets. It comprises two sub-protocols — Transfer Requests (simple static payment URIs) and Transaction Requests (dynamic server-signed transaction fetching) — and enables point-of-sale payments, loyalty programs, and interactive commerce experiences using QR codes or deeplinks.
Relacionados: Transaction Request (Solana Pay), Transfer Request (Solana Pay)
Glossary Copilot

Haz preguntas de Solana con contexto aterrizado sin salir del glosario.

Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.

Abrir workspace completa del Copilot
Explicar este código

Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.

Haz una pregunta aterrizada en el glosario

Haz una pregunta aterrizada en el glosario

El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.

Grafo conceptual

Ve el término como parte de una red, no como una definición aislada.

Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.

Rama

Transaction Request (Solana Pay)

A Solana Pay protocol flow in which a QR code or link encodes an HTTPS URL; when scanned, the wallet performs a GET request to discover metadata (label, icon) and then a POST request with the user's public key, receiving a base64-encoded partially-signed transaction that the wallet can inspect, sign, and submit. This dynamic model enables programmable commerce flows such as NFT minting, coupon redemption, and multi-step checkout because the merchant server constructs the transaction at request time rather than encoding it statically.

Rama

Transfer Request (Solana Pay)

The simpler of the two Solana Pay sub-protocols, encoding a static SOL or SPL token payment request as a URI in the format solana:<recipient>?amount=<value>&spl-token=<mint>&label=<label>&memo=<memo>. Transfer Request URIs are fully self-contained and require no server interaction — wallets parse the URI and construct the system program transfer or SPL token transfer instruction locally, making them ideal for fixed-price invoices and tip links.

Siguientes conceptos para explorar

Mantén la cadena de aprendizaje en movimiento en lugar de parar en una sola definición.

Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.

Infraestructura

Transaction Request (Solana Pay)

A Solana Pay protocol flow in which a QR code or link encodes an HTTPS URL; when scanned, the wallet performs a GET request to discover metadata (label, icon) and then a POST request with the user's public key, receiving a base64-encoded partially-signed transaction that the wallet can inspect, sign, and submit. This dynamic model enables programmable commerce flows such as NFT minting, coupon redemption, and multi-step checkout because the merchant server constructs the transaction at request time rather than encoding it statically.

Infraestructura

Transfer Request (Solana Pay)

The simpler of the two Solana Pay sub-protocols, encoding a static SOL or SPL token payment request as a URI in the format solana:<recipient>?amount=<value>&spl-token=<mint>&label=<label>&memo=<memo>. Transfer Request URIs are fully self-contained and require no server interaction — wallets parse the URI and construct the system program transfer or SPL token transfer instruction locally, making them ideal for fixed-price invoices and tip links.

Infraestructura

Staked Connection

An RPC connection routed through a validator or RPC node that holds delegated stake, granting the connection higher priority under Solana's Stake-Weighted Quality of Service (SWQoS) system. Transactions submitted via staked connections receive preferential bandwidth allocation to the leader's TPU, significantly improving landing rates during periods of network congestion. RPC providers like Helius and Triton offer staked connections as a premium feature for production applications.

Infraestructura

Solana Mobile

A hardware and software initiative by Solana Labs producing Android smartphones (Saga, Chapter 2) with a secure element-backed seed vault for private key storage, a curated dApp store for Solana applications, and the Mobile Wallet Adapter protocol for standardized wallet-dApp communication on mobile. The Solana Mobile Stack (SMS) enables native mobile dApps to interact with on-device wallets without browser extensions or QR code scanning, targeting the mobile-first crypto user base.

Comúnmente confundido con

Términos cercanos en vocabulario, acrónimo o vecindad conceptual.

Estas entradas son fáciles de mezclar cuando lees rápido, haces prompting a un LLM o estás entrando en una nueva capa de Solana.

Infraestructurasolana-mobile

Solana Mobile

A hardware and software initiative by Solana Labs producing Android smartphones (Saga, Chapter 2) with a secure element-backed seed vault for private key storage, a curated dApp store for Solana applications, and the Mobile Wallet Adapter protocol for standardized wallet-dApp communication on mobile. The Solana Mobile Stack (SMS) enables native mobile dApps to interact with on-device wallets without browser extensions or QR code scanning, targeting the mobile-first crypto user base.

AliasSMSAliasSaga
Infraestructurashredstream-proxy

Shredstream Proxy

A low-latency relay layer that receives shred feeds from validator-adjacent infrastructure and forwards them into downstream search, trading, or analytics systems without requiring each consumer to maintain its own direct shred connection. Teams use shredstream proxy patterns to normalize transport, centralize access control, and fan out raw block data to internal services that care about block contents before standard RPC surfaces catch up.

Infraestructuraactions

Solana Actions

A protocol specification that standardizes how web servers expose signable Solana transactions and messages via HTTPS endpoints, enabling any URL to become an interactive blockchain entry point. Actions use a GET/POST handshake similar to Solana Pay Transaction Requests but are generalized beyond payments to support arbitrary on-chain operations (voting, staking, DeFi interactions), and serve as the server-side counterpart to Blinks, which render Actions as embeddable UI components.

AliasActions
Términos relacionados

Sigue los conceptos que realmente le dan contexto a este término.

Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.

Infraestructuratransaction-request

Transaction Request (Solana Pay)

A Solana Pay protocol flow in which a QR code or link encodes an HTTPS URL; when scanned, the wallet performs a GET request to discover metadata (label, icon) and then a POST request with the user's public key, receiving a base64-encoded partially-signed transaction that the wallet can inspect, sign, and submit. This dynamic model enables programmable commerce flows such as NFT minting, coupon redemption, and multi-step checkout because the merchant server constructs the transaction at request time rather than encoding it statically.

Infraestructuratransfer-request

Transfer Request (Solana Pay)

The simpler of the two Solana Pay sub-protocols, encoding a static SOL or SPL token payment request as a URI in the format solana:<recipient>?amount=<value>&spl-token=<mint>&label=<label>&memo=<memo>. Transfer Request URIs are fully self-contained and require no server interaction — wallets parse the URI and construct the system program transfer or SPL token transfer instruction locally, making them ideal for fixed-price invoices and tip links.

Más en la categoría

Quédate en la misma capa y sigue construyendo contexto.

Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.

Infraestructura

RPC (Llamada a Procedimiento Remoto)

The JSON-RPC 2.0 protocol interface through which clients communicate with Solana nodes to query chain state, submit transactions, and subscribe to events. Solana exposes a rich set of HTTP and WebSocket endpoints (e.g., getAccountInfo, sendTransaction) that abstract direct peer-to-peer network participation, making RPC the primary integration point for wallets, dApps, and indexers.

Infraestructura

Nodo RPC

A Solana full node that stores ledger state and serves JSON-RPC and WebSocket requests from clients without participating in consensus or voting. RPC nodes must replay every transaction to maintain an accurate account state database, and high-throughput deployments typically run dedicated RPC nodes with large SSDs, high RAM (256 GB+), and high-bandwidth network connections to handle concurrent client load without impacting validator performance.

Infraestructura

RPC Methods

The enumerated JSON-RPC endpoints exposed by Solana nodes, covering account queries (getAccountInfo, getMultipleAccounts, getProgramAccounts), block and transaction retrieval (getBlock, getTransaction), cluster metadata (getEpochInfo, getSlot, getVersion), and transaction submission (sendTransaction, simulateTransaction). Methods accept a Commitment parameter (processed, confirmed, finalized) to control the recency-vs-safety tradeoff of returned data.

Infraestructura

getAccountInfo

An RPC method that returns the complete on-chain state of a single account identified by its base-58 public key, including its lamport balance, owner program, executable flag, rent epoch, and raw data payload encoded as base64 or base58. It is the most fundamental read primitive in Solana development and is called at the specified commitment level, with the data field being null if the account does not exist.