Operator guideEN

Payments Overview

Source-backed operator guidance for this page.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

Payments Overview

This page should explain how operators inspect and manage payment activity in the CRM.

Intended operator questions

  • what states can a payment have
  • which fields are provider-facing vs internal
  • when can an operator retry, approve, or escalate
  • which brand differences exist in payment tooling

Planned authored additions

  • provider caveats
  • delay expectations
  • escalation paths for stuck transactions
Related references

Related pages

pageActivity Tag Rules

Operator documentation for activity-driven tag automation rules, including list, create, edit, detail inspection, and recent application history.

pageActivity Tag Rules / Applications

Recent application history shown inside the detail page for one rule, including action performed, timestamp, and captured activity data.

pageActivity Tag Rules / Create

Create flow for a new activity tag rule, including optional clone-from-existing behavior and condition testing.

pageActivity Tag Rules / Detail

Rule inspection page with backend identity, conditions, timestamps, impact estimate, run action, delete action, and recent application history.

pageActivity Tag Rules / Edit

Edit flow for one backend rule or a grouped add and remove pair, including split or merge behavior and condition testing.

pageActivity Tag Rules / List

Main inventory for activity-driven tag rules, with search, activity and status filters, grouped rows, clone, edit, and run actions.