Admin Subscription & Subscription Payment Endpoints

[codebestia]

Background

Listing/detail for individual subscriptions, plus a view over subscription payment history. The payments endpoint has a real dependency worth calling out explicitly rather than silently assuming it's satisfied: it reads Transaction rows where transactionType = SUBSCRIPTION_CHARGE, which only exist once a SubscriptionChargedEvent handler is writing them.

Proposed Steps

1. GET /admin/subscriptions — paginated, filterable by status, planId, merchantAddress (via Subscription.merchantId → Merchant.address, no join through the plan needed since merchantId is direct), customer (address, exact match), sortable by sortBy in [createdAt, lastCharged] / sortDir.
2. GET /admin/subscriptions/:id — subscription detail, including the related plan's description/amount/interval inlined (one query, include: { plan: true }) so the admin doesn't need a second request.
3. GET /admin/subscriptions/payments — lists Transaction rows where transactionType = 'SUBSCRIPTION_CHARGE', paginated, filterable by merchantAddress and date range, mirroring the filter shape already established for invoices.

Acceptance Criteria

• GET /admin/subscriptions supports all listed filters, sort options, and pagination
• GET /admin/subscriptions/:id includes plan details inline; 404 for unknown id
• GET /admin/subscriptions/payments returns only SUBSCRIPTION_CHARGE transactions, correctly filtered and paginated
• The dependency on SubscriptionChargedEvent handler is documented in code (comment on the payments endpoint) so an empty result set is understood as "no charges indexed yet" rather than assumed broken
• No new Prisma models or fields required

[Peculiarr7]

Hi! I’m a full-stack developer with a strong blockchain background, and I’m confident I can resolve this issue quickly and effectively. I’ll deliver a clean, reliable solution with immediate attention to detail, ensuring it’s completed as soon as possible. Please assign it to me—I’m ready to get started right away.

[bobo-24]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!

[shogun444]

Hey, I’d love to take on #46! Went through the repo and Prisma schema—the requirement is crystal clear.

I'll implement the three admin endpoints cleanly: handling the direct merchant filtering, inlined plan details in a single query, and the SUBSCRIPTION_CHARGE payments filter alongside full pagination and test coverage.

Portfolio: https://portfolio-amber-one-v8ggyhsjyr.vercel.app/

Ready to jump on this right away upon assignment!

[codeZe-us]

Hello, i can get this done. I will build the three admin endpoints using Prisma queries on the existing Subscription and Transaction models, with no schema changes, adding filtering, sorting, and pagination to the list endpoint, and a plan included with a 404 fallback on the detail endpoint, a filtered query with a documenting comment on the payments endpoint to explain its dependency on the SubscriptionChargedEvent handler.

[grantfox-oss]

🦊 GrantFox — @shogun444 has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #46)
2. Your PR will be reviewed by the ShadeProtocol maintainers

Good luck! Track your progress on GrantFox.