T-3 · Surfacear reputacion del proveedor en las tarjetas de descubrimiento

[ericmt-98]

Contexto

Las validaciones V-7, V-9 y V-12 muestran que la confianza en un proveedor se construye principalmente en el momento del descubrimiento — no despues. Los usuarios priorizan negocios conocidos, calificaciones y un historial verificable.

Que existe hoy

El badge "verificado" ya se muestra (DepositMap, ChatRoom, Home). El rating de estrellas existe en SuccessScreen. Pero completion_rate, trades_completed y tier — que el backend ya guarda en la tabla merchant_configs — no se muestran en las tarjetas de descubrimiento, que es donde el usuario decide.

Depende de: P1-1 (#151) ya mergeado — el refactor de merchantToOffer ya usa datos reales.

Que construir

En cada tarjeta de proveedor en ExploreMap.tsx y DepositMap.tsx:

• Mostrar porcentaje de completitud de trades.
• Mostrar numero de trades completados.
• Mostrar tier del proveedor.
• Distinguir visualmente "negocio establecido" de "individuo" (senal de V-9/V-12).

Todos estos campos ya estan disponibles en el tipo AvailableMerchant (services/api.ts).

Archivos a tocar

Archivo	Que cambia
micopay/frontend/src/pages/ExploreMap.tsx	Mostrar reputacion en tarjetas
micopay/frontend/src/pages/DepositMap.tsx	Idem
micopay/frontend/src/services/api.ts	Verificar que AvailableMerchant expone los campos (probablemente ya estan)

Criterio de aceptacion

• Cada tarjeta muestra completitud + trades + tier reales de la API (no constantes).
• Se distingue visualmente "negocio establecido" de "individuo".
• Coordinado con P1-1 (P1-1 · ExploreMap shows hardcoded merchant economics — use real API data #151) — no duplicar el refactor de la tarjeta, solo agregar campos.
• tsc --noEmit pasa sin errores.

Delivery: abre un PR que modifique los archivos listados. El maintainer revisara y mergeara.

[Peaostrel]

@Peaostrel has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i can handle this quickly

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Peaostrel to this issue.

[OG-wura]

@OG-wura has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer. I would love to work on this. I can fix it

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OG-wura to this issue.

[midexol]

@midexol has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hola responsable del mantenimiento, me gustaría ayudarle a resolver esto rápidamente. Por favor, asígnelo.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @midexol to this issue.

[Abba073]

@Abba073 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Sir,

I came across your project and will love to have the opportunity to work on it

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abba073 to this issue.

[Emoji-dot]

@Emoji-dot has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I can work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emoji-dot to this issue.

[Thoni76]

@Thoni76 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Asunto: Postulación Issue #192
Hola equipo,
Me postulo para resolver este issue. Mi enfoque:

• Constantes: Centralizaré los umbrales (5% y 0.8%) sin hardcodear.
• UI: Mostraré el fee total combinado en ExploreMap y DepositMap.
• Guardrail: Añadiré la advertencia visual si el total supera el 5%.
• Calidad: PR limpio tras validar con tsc --noEmit.
  Listo para comenzar. ¡Saludos!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Thoni76 to this issue.

[SaviourBosan]

@SaviourBosan has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day I would love to work on this issue. I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process. Please consider my application.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SaviourBosan to this issue.

[drips-wave]

Congratulations, @SaviourBosan! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @SaviourBosan: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊