Release 1.97 (Tech Release 1.110)

🟢 Platform: New Payment Reconciliation Report

We’ve added a new Payment Reconciliation Report to help finance teams easily reconcile Pelcro transactions with their payment processor’s monthly summaries — reducing manual work and improving accuracy.

What’s New:

  • A new Payment Reconciliation tab under Accounting → Reports.
  • Monthly report with a YYYY-MM selector and currency filter.
  • Simple, structured table showing:
    • Payments (received)
    • Refunds
    • Disputes
  • Each row includes:
    • Online Total
    • Offline Total
    • Total
  • Export to CSV for each report view, matching on-screen data.
  • Online vs. offline classification aligns with Pelcro’s existing payment source logic.

🎯 Impact:

This report enables clean, one-to-one monthly reconciliation with payment processors, helping teams validate totals faster, reduce errors, and maintain consistent financial records.

🟢 Platform: Added Last Active Tracking for Better Engagement & Segmentation

We’ve introduced Last Active tracking to give you clearer visibility into recent user activity, enabling smarter engagement and churn-prevention strategies.

What’s New:

  • A new last_active_at timestamp is now recorded for authenticated users.
  • The timestamp updates whenever a user interacts with your website.
  • Last Active is now:
    • Visible in the platform UI alongside Last Login
    • Available on the JS SDK user object
    • Exposed via the API
    • Included in customer-related webhooks

🔒 Limitations:

  • Activity is tracked only for authenticated users with valid sessions.
  • Anonymous or unauthenticated activity is not recorded.

This update helps teams identify inactive users, build engagement segments, and trigger timely re-engagement campaigns with greater accuracy.



🟢 Platform: Enhanced Payment Method Management via Direct URLs

We’ve improved the payment method update experience to support direct URL access, clearer user flows, and better error handling — making it easier for users to manage their cards without navigating the full dashboard.

What’s New:

  • Direct payment method updates via URL

    • ?view=payment-method-update&source_id={id} opens the update modal for a specific payment method.
    • Automatically redirects unauthenticated users to login.
    • Ensures the payment SDK is fully loaded before rendering the form.
  • Payment methods list accessible via URL

    • ?view=payment-method-update&list=all or ?view=payment-method-update opens the payment methods list modal.
    • List displays all saved payment methods with edit and delete actions.
  • Graceful handling of invalid or outdated links

    • Invalid source_id values show an in-modal error message (no broken or empty states).
    • Users are given a clear path to recover via a “View all payment methods” action.

🎯 Impact:

These enhancements enable seamless card updates from email links, improve transparency when issues occur, and give users faster access to their payment methods — all without leaving their current context.


🟢 Platform: Improved Sign-In Button Handling to Prevent Plugin Interference

We’ve improved the Pelcro Sign In experience to prevent third-party WordPress plugins or scripts from incorrectly intercepting the login action and redirecting users to search results pages.

What’s Improved:

  • The Pelcro Sign In button now reliably triggers the correct authentication flow, even on sites with form- or search-intercepting plugins.
  • Updated event handling within the Pelcro React Elements SDK ensures login requests are executed as intended.
  • Users can now complete sign-in without unexpected redirects caused by external plugin behavior.

⚠️ Notes & Limitations:

  • This update does not override any custom code that explicitly targets Pelcro elements.
  • Conflicts from plugins injected after Pelcro events complete may still require integration guidance.
  • Sites that dynamically rewrite button DOM nodes may need additional configuration.

This enhancement improves login reliability across WordPress environments while maintaining compatibility with existing integrations.