Frontend: Add Internationalization (i18n) Framework with Full RTL Support

[Smartdevs17]

Context

AgenticPay serves a global user base. A single-language interface excludes non-English speakers and creates adoption barriers in key markets.

Current Limitation/Problem

The frontend is English-only with no internationalization framework. Adding translations requires significant refactoring. Right-to-left (RTL) languages like Arabic and Hebrew are not supported.

Expected Outcome

A complete i18n framework with next-intl, automated translation pipeline, RTL layout support, and locale detection. Initial translations for top 5 languages.

Acceptance Criteria

• Integrate next-intl for route-based localization
• Support language switching without page reload
• Auto-detect browser locale on first visit
• RTL layout support with mirrored UI components
• Translation files for: English, Spanish, French, Japanese, Arabic
• ICU message format with pluralization and interpolation
• Extract all hardcoded strings to translation keys
• Translation management dashboard (for missing keys)
• Locale-aware date, time, number, and currency formatting
• SEO: hreflang tags and localized sitemaps

Technical Scope

• frontend/src/i18n/ - i18n configuration and locales
• frontend/messages/{en,es,fr,ja,ar}.json - translation files
• next-intl integration with App Router
• RTL CSS with logical properties
• frontend/src/components/common/locale-switcher.tsx - language selector
• Automated translation via DeepL API in CI
• Edge cases: missing translations fallback, mixed content, dynamic content

[tecmalik]

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

Hi,
Please assign me this task. I’ll implement the next-intl localization framework with RTL support, language detection, locale-aware formatting, translation files for five languages, and a DeepL CI translation pipeline.

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

[Bigmehelen]

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

I would like to work on this issue, please assign me to this issue

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

[devsimze]

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

Hi I'd like to work on this issue

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

[drips-wave]

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

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