Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Question: buyer-authorized discovery of existing merchant rewards through Link Agent Wallet

Abierto
  • ¿Algo no está bien?
#460 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
payments

Línea de trabajo

Start with the Link Agent Wallet guide and SDK, then check the payment and financial-data resources and the read-only insights interface mentioned in the issue. Determine whether a supported public, preview, or partner path exists for exposing buyer-authorized rewards before checkout, and whether agents can discover them through Link or need separate integrations. Done means identifying the supported path or the appropriate team to answer.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

We are building StabileRewards, a loyalty platform focused on agentic commerce. In one of Shopify use case, it issues single-use Shopify reward codes after qualifying purchases. For these purchase-issued rewards, points are deducted at issuance; the buyer already owns the code. We have buyer-authorized code retrieval through MCP.

We want a buyer agent to know ‘you already have $10 off at this merchant’ during shopping, apply that existing code at checkout, and use Link to approve payment for the discounted total.

I reviewed the Link Agent Wallet guide and SDK. I found payment and financial-data resources, but no reward/offer publishing interface; insights exposes reads. I also saw Link offers described in the privacy center.

Is there a supported public, preview or partner path for a loyalty provider to expose buyer-specific existing rewards through Link, either as stored rewards or an authorized provider reference? If so, can Link-connected agents discover them before checkout, or does each agent need a separate integration? If this belongs with another team, a pointer would help.

Related UCP context: the loyalty extension, provider discovery proposal #384, and our reference fixtures in #863. We're asking about Link implementation support, not assuming these protocol discussions imply a shipped Link feature.

@prasad-stripe — given your work on the Link payment handler proposal in ACP and your contributions to UCP, could you help point us to the right team for this question?

Lenguaje dominante
TypeScript
Estrellas
856
Forks
143
Merge medio
17 h 34 min
PR fusionados (30 d)
77

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de stripe/link-cli

Todos los issues de stripe/link-cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.