Merchant availability, settings and onboarding end-to-end

[ericmt-98]

Problem

Several pieces are disconnected:

• `MerchantSettings.tsx` exists but is not mounted in `App.tsx`
• `services/api.ts` calls `setAvailability('/users/me/availability')` but that route does not exist in the backend
• `patchMerchantAvailability('/users/me')` does not match any defined route in `users.ts`
• `merchant.service.ts` uses `merchant_configs` but the initial schema does not create it
• `trade.service.ts` reads `seller.availability` but the query only selects `id, stellar_address`, so availability never actually blocks new trades

Why it matters

A merchant cannot pause operations, change their rate or control limits from the APK reliably. This affects operational safety and cancellations.

In-scope

• Mount `MerchantSettings` in routes and nav
• Create `PATCH /users/me/availability` or align the client to a consistent existing route
• Add `availability` column with enum `online/offline/paused`
• Fix `createTrade()` to read real seller availability
• Persist rate/min/max/daily cap in `merchant_configs`
• Show availability banner and pending-sync state if network fails

Out-of-scope

• Merchant reputation display
• Merchant onboarding KYC

Acceptance criteria

• Merchant can pause/resume from the APK
• Merchant can edit their rate and limits
• Creating a trade fails with a clear message if the merchant is offline or paused
• Settings persist after restarting the backend and app

Test notes

• Set merchant to paused, attempt to create a trade as buyer, verify rejection
• Verify settings persist across app restart

Dependencies

• Fix database schema, migrations and runtime persistence #64 (DB schema) — merchant_configs table required

Complexity

high

[Richiey1]

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

Hello, I'm a Stellar developer with experience in both frontend and backend development. I can handle the end-to-end integration of merchant availability and onboarding. I'll focus on connecting the disconnected pieces between the UI, services, and backend routes, ensuring a seamless experience for merchants on the micopay-protocol. Ready to get to work!

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

[drips-wave]

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

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

[Richiey1]

Hi @ericmt-98, I've implemented the merchant availability, settings, and onboarding end-to-end as requested. Merchants can now manage their spread, trade limits, and pause/resume operations directly from the app. Review the PR here: #114