API Rate-Limit Exceeded Feedback with Retry Countdown

[Kingsman-99]

Description

When the dApp's backend API rate-limits any request (not just invoice creation), the frontend surfaces a generic network error rather than explaining the situation and automatically retrying. A unified rate-limit handler with countdown and auto-retry should apply to all API calls across the application.

Technical Context

src/lib/api.ts (new or refactored) is a central fetch wrapper that intercepts 429 responses, reads the Retry-After header, and schedules an automatic retry using setTimeout. src/context/RateLimitContext.tsx (new) tracks the global rate-limit state and exposes it to src/components/layout/RateLimitBar.tsx (new), which renders a slim banner at the top of the page showing the countdown. Individual hooks in src/hooks/ use the central api wrapper instead of raw fetch.

Acceptance Criteria

• Any API call across the app that receives a 429 response triggers the rate-limit banner with a countdown
• The API wrapper automatically retries the failed request when the countdown reaches zero
• The banner is dismissable but the auto-retry still proceeds even when dismissed
• Only one banner instance is shown even if multiple concurrent requests hit the rate limit simultaneously
• Successful auto-retry resolves the original Promise and updates the UI as if the first call had succeeded
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

---

[Yerimahjr]

Hi maintainer please assign me this issue
I will deliver it in 24 hours

[kelvin1738-sys]

@kelvin1738-sys has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I've thoroughly reviewed the requirements and will implement a clean, maintainable solution that aligns with the project standards and fulfills all acceptance criteria.

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

[gitGolf]

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

Hello Maintainer, I'd love to work on this task.
Please assign it to me, Thank you!

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

[Jessicaayegh]

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

Hi maintainer! I’d love to work on this issue if it’s still available. I have a good understanding of the requirements and would be happy to implement the solution. Thanks for considering my request!

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

[Nuwe10]

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

I will like to work on this please

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

[drips-wave]

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

🧑‍💻 @Nuwe10: 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 🌊