31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
# ADR 0002: Moyasar As The Payment Gateway
|
|
|
|
## Status
|
|
|
|
Accepted
|
|
|
|
## Context
|
|
|
|
The platform needs a payment gateway that supports Saudi Arabia, SAR currency defaults, and local payment methods (e.g. STC Pay, Apple Pay, Samsung Pay). The backend already implements a `MoyasarGateway` integration and models `payments.Payment` with a `moyasar` provider option.
|
|
|
|
## Decision
|
|
|
|
Use Moyasar as the payment gateway for the MVP. Payment creation, capture, refund, and webhook reconciliation are implemented through `apps.payments.services.gateway.MoyasarGateway`.
|
|
|
|
## Consequences
|
|
|
|
- Supports KSA-focused payment methods and SAR by default.
|
|
- Operational dependency on Moyasar uptime and API stability.
|
|
- Payment flows and webhooks are tied to the Moyasar API surface until a gateway abstraction is expanded.
|
|
|
|
## Alternatives Considered
|
|
|
|
- Other regional gateways: deferred until the MVP is validated.
|
|
- Stripe or similar global providers: not selected for MVP due to KSA-specific coverage priorities.
|
|
|
|
## Related
|
|
|
|
- `backend/apps/payments/services/gateway.py`
|
|
- `docs/runbooks/payments_sanity_check.md`
|
|
- `docs/architecture.md`
|