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

Question: issuer shared_metadata support for Link SPT requests

Aperta
  • Qualcosa non va?
#479 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
api, payments

Direzione di ricerca

Start by reviewing the Link shared payment token API and the MPP challenge and Stripe reference implementation linked in the issue. Determine whether Link supports requesting issuer-visible shared_metadata, and compare that with the existing sandbox observation. Done means documenting the supported capability and the recommended integration for challenge binding and merchant-side order association.

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

Descrizione

Clarification: optional issuer metadata support, not an established MPP defect

After rechecking the current MPP specifications and reference implementation, we need to correct our original framing. Requiring shared_metadata[ticket_fairy_request_binding] is an additional Ticket Fairy application contract, not a demonstrated requirement of Stripe MPP. We have not established a Stripe or Link protocol defect.

Standard MPP authenticates the echoed challenge (including payment parameters and optional expiry/body digest/opaque context), and the Stripe reference implementation settles the exact challenge amount/currency with the SPT and a challenge/token idempotency key. It does not require a granted-token shared_metadata lookup. The server-authenticated challenge and issuer attestation of a specific purchase are different assurances; our implementation had demanded the latter as an extra condition.

The sandbox observation below remains reproducible, but should be treated as a capability question:

  • Official @stripe/link-cli 0.29.2, one explicitly test-mode SPT request, existing test seller Profile, amount 100 USD minor units.
  • Explicit SpendRequest metadata ticket_fairy_request_binding=<opaque test reference> was retained on the approved SpendRequest.
  • The seller retrieved that exact granted token: HTTP 200, object shared_payment.granted_token, livemode false, empty shared_metadata.
  • No token was consumed and no PaymentIntent, live charge or transfer was created.

Does Link offer a supported way to request issuer-visible shared_metadata, or is the recommended integration to rely on the standard challenge/body binding and merchant-side order association instead? We are reviewing our additional restriction for interoperability rather than asking Link to satisfy a supposed protocol mandate.

Sources:

No credentials, tokens, customer data or account identifiers are included.

Lingua principale
TypeScript
Stelle
856
Fork
143
Merge medio
17h 34m
PR unite (30g)
77

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.