Unsupervised/unsupervised-scheduler
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 12 Wiki Activity

Payments: admin refund flow (refunded status is unreachable) #72

New Issue
Open
opened 2026-07-18 21:03:37 +00:00 by thatguygriff · 0 comments
thatguygriff commented 2026-07-18 21:03:37 +00:00
Owner
Copy Link
Copy Source

What

The payments schema and model define a refunded status (us_payments.status, Payment::STATUS_REFUNDED), but nothing in the plugin can ever set it — STATUS_REFUNDED has no other reference in src/. docs/features/lesson-booking.md documents the gap:

A paid payment is never touched — refunds are a manual, admin-side decision.

Today that manual decision has no tooling: the admin refunds in Stripe (or by e-transfer) out-of-band and the ledger still says paid, which also skews the monthly payment reports.

Proposal

  • Studio-admin action (manage_billing) to mark a paid payment refunded — e.g. PATCH /payments/{id} extension plus a button on the payments queue / student payment history.
  • For card payments, optionally issue the refund via the Stripe API (StripeGateway) rather than only recording it; handle the charge.refunded webhook.
  • Decide the effect on the linked registration (cancel the lesson/enrolment or leave it), and how refunded rows appear in payment-reporting totals/CSV.

Where

  • src/Payment/ (PaymentRepository, PaymentEndpoint, StripeGateway, PaymentController)
  • Specs: docs/features/payments.md, docs/features/payment-reporting.md
  • Tests under tests/Unit/Payment/
## What The payments schema and model define a `refunded` status (`us_payments.status`, `Payment::STATUS_REFUNDED`), but nothing in the plugin can ever set it — `STATUS_REFUNDED` has no other reference in `src/`. `docs/features/lesson-booking.md` documents the gap: > A `paid` payment is never touched — refunds are a manual, admin-side decision. Today that manual decision has no tooling: the admin refunds in Stripe (or by e-transfer) out-of-band and the ledger still says `paid`, which also skews the monthly payment reports. ## Proposal - Studio-admin action (`manage_billing`) to mark a `paid` payment `refunded` — e.g. `PATCH /payments/{id}` extension plus a button on the payments queue / student payment history. - For card payments, optionally issue the refund via the Stripe API (`StripeGateway`) rather than only recording it; handle the `charge.refunded` webhook. - Decide the effect on the linked registration (cancel the lesson/enrolment or leave it), and how `refunded` rows appear in `payment-reporting` totals/CSV. ## Where - `src/Payment/` (`PaymentRepository`, `PaymentEndpoint`, `StripeGateway`, `PaymentController`) - Specs: `docs/features/payments.md`, `docs/features/payment-reporting.md` - Tests under `tests/Unit/Payment/`
thatguygriff added the paymentsfeature labels 2026-07-18 21:03:37 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 enhancement
Extends an existing feature
 feature
New user-facing capability
 payments
Billing, Stripe, receipts, reporting
 security
Security vulnerability or hardening
No labels feature payments
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
thatguygriff (James Griffin-Allwood)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Unsupervised/unsupervised-scheduler#72