Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#460 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
payments

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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?

Lingua principale
TypeScript
Stelle
856
Fork
143
Merge medio
19h 32m
PR unite (30g)
75

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di stripe/link-cli

Tutte le issue di stripe/link-cli

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.