Add shared HTTP client configuration type

[therealjhay]

Description: When inter-service HTTP calls are implemented, each service will need HTTP client configuration. A shared type would ensure consistency.

Requirements:

• Define ServiceClientConfig type: { baseUrl: string; timeout: number; retries: number; authToken?: string }
• Define ServiceName as a union of service names
• Export for use in api-gateway when calling other services

Suggested execution steps:

1. Add types to shared/types/index.ts
2. Export ServiceName = 'api-gateway' | 'fx-engine' | 'settlement-engine' | 'indexer'
3. Export ServiceClientConfig
4. Rebuild

Example commit message:

feat(types): add inter-service HTTP client configuration types

[Praxhant97]

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

Greetings, i would like to work on your BettaPay-Backend project! Leaving inter-service communication without a unified network configuration model risks configuration drift, unpredictable timeout behaviors, and brittle error-handling policies across microservices; I am highly comfortable with TypeScript type systems, engineering shared monorepo packages, and designing robust HTTP client abstractions, which will allow me to seamlessly implement the shared ServiceClientConfig structure and ServiceName string union within shared/types/index.ts, ensuring smooth integration when the api-gateway communicates with the fx-engine, settlement-engine, or indexer platforms under a 12-hour timeframe.

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

[HassanKorey]

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

Pls assign

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

[dedukpe]

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

Please assign this to me
Thank you

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

[drips-wave]

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

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