Skip to main content

Activity Logs - Payments/ refunds/ subscriptions

Pelcro Product

Problem Statement

Collaborators and clients cannot see who created or modified customer-related records (e.g., addresses, subscriptions, payments, offline payments).

This limits transparency, slows support investigations, and makes it difficult to audit manual or collaborator-driven actions.

User Story

As a collaborator or customer support user,

I want to view all activity related to a customer, including what changed and who performed the action,

so that I can quickly verify account updates and identify whether actions were done by a collaborator or the end user.

Definition of Done (DoD)

  1. Payment detail view displays:

  2. “Posted by” field indicating:

  3. Collaborator name (for manual/offline payments)

  4. System (for automated charges)

  5. End User (for self-serve payments, if applicable)

  6. Refund detail view displays:

  7. “Refund created by” field indicating:

  8. Collaborator name (manual refund)

  9. System (by disputes)

Subscription Activity Enhancements

✔ Subscription Activity logs include an explicit “Action by” field > show the collab email/end user:

  1. System (auto-renewals, scheduled expirations, automated status changes)

  2. Collaborator name (manual cancel, extend, reinstate, pause, resume)

  3. End User (self-serve cancellation or renewal).

✔ Each activity entry clearly shows (payments/ refunds):

  1. Action performed (created / updated / deleted)

  2. Action Timestamp

  3. Action by (Collaborator / End User / System)

  4. Actor identity (name/email when applicable)

Posted by Rana Haleem ·
Status: Available1 comment

Log in to comment and vote

Comments1

  • Nada Shoukry

    Team•

    Sep 17

    •

    Merged request

    •

    3 votes

    Customer Record Audit Log (Changes & Deletions)

    🔍 Problem Statement

    As a publisher, there is no audit trail on customer records — when a record is changed or deleted, we cannot tell who did it, when, or from where. This makes dispute resolution, compliance auditing, and investigating discrepancies difficult.

    💡 User Story

    As a publisher, I want an audit log on the customer record covering both changes and deletions, so that I can trace every modification back to a collaborator and a timestamp.

    🎯 Definition of Done (DoD)

    • ✔ Given a customer record, when an admin views its audit log, then it shows a chronological list of changes — field changed, old value, new value, the collaborator (or system) responsible, and the timestamp.
    • ✔ Given a customer record is deleted, when the deletion occurs, then it is recorded with the deleted customer, who performed it, the timestamp, and the method (manual/API) — plus a reason where available.
    • ✔ At minimum, every Pelcro object a collaborator can create or modify exposes created_by, updated_by, and last_updated.
    • ✔ Authorized users can view and search these events in the platform audit log, with retention aligned to the audit log policy.
    • ✔ This change will impact UI / API — specifically the Customer detail page (Platform UI) and the audit-log resource (Core API).
    • ✔ Limitations: history begins at rollout — changes made before the feature ships are not backfilled.