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

Question: issuer shared_metadata support for Link SPT requests

Abierto
  • ¿Algo no está bien?
#479 1 comentario 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, payments

Línea de trabajo

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.

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

Descripción

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.

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.