Files

T

soroush.asadi ec51e87d2d feat(payment): standalone ZarinPal broker on pay.flatrender.ir

A generic multi-client payment gateway so FlatRender, meezi.ir and
bargevasat.ir can all pay through ZarinPal's single verified callback
domain (pay.flatrender.ir).

New Go service services/payment (clones the notification skeleton +
vendored deps):
- migration 31_payment_broker.sql — `payment` schema: client_apps,
  transactions, webhook_deliveries.
- ZarinPal v4 client ported from the proven identity PaymentService
  (request.json -> StartPay -> verify.json; codes 100/101).
- client API: POST /v1/pay/request + /v1/pay/inquiry, authed by
  X-Api-Key + HMAC body signature; GET /callback/zarinpal (the single
  verified endpoint) verifies, then 302s the user back to the site's
  return_url (signed) and fires a signed, retried webhook.
- per-client ZarinPal merchant override (default = shared merchant);
  amount stored canonically in Rial, unit to ZarinPal env-configurable.
- admin API /v1/admin/* (FlatRender admin JWT): client-app CRUD +
  key issue/rotate + transactions list.

Deploy wiring: payment-svc in docker-compose.v2.yml (host port 1607),
pay.flatrender.ir server block in mirror-nginx conf, ENV_FILE +
README updates (cert SAN + manual migration note).

Admin UI: src/components/admin/PaymentsAdmin.tsx (client apps with
one-time key reveal + rotate, transactions table) + /admin/payments
page + nav link + fa/en strings; pay-admin proxy route to payment-svc.

Docs/SDK: deploy/PAYMENTS.md (integration contract) + deploy/sdk/flatpay.js
(zero-dep Node client + webhook verifier) for meezi/any site.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-15 23:59:54 +03:30

956 B

Raw Blame History

How to contribute

We definitely welcome patches and contribution to this project!

Tips

Commits must be formatted according to the Conventional Commits Specification.

Always try to include a test case! If it is not possible or not necessary, please explain why in the pull request description.

Releasing

Commits that would precipitate a SemVer change, as described in the Conventional Commits Specification, will trigger release-please to create a release candidate pull request. Once submitted, release-please will create a release.

For tips on how to work with release-please, see its documentation.

Legal requirements

In order to protect both you and ourselves, you will need to sign the Contributor License Agreement.

You may have already signed it for other Google projects.

956 B Raw Blame History

How to contribute

Tips

Releasing

Legal requirements

956 B

Raw Blame History