Use casePayment investigations

Missing payments, traced to a resolution.

When a payment goes missing, an agent takes the case. It matches the customer's message to the transaction, traces it through every bank and partner, and confirms the money arrived or came back.

How it works

From “where is my money?” to a closed case.

  1. 01

    Comes in

    A customer reports a missing, delayed or returned payment by chat, email or ticket. The agent opens a case and matches it to the transaction.

    /intake
    └ chat · “my £4,200 hasn’t arrived”
    › matched to TX-88213
    › SWIFT MT103 · sent 14 Nov
    ✦ case PI-20417 opened
  2. 02

    Worked across teams

    It raises traces with banks and partners, chases until they reply, and brings in payments operations when a decision is needed.

    /investigate
    › trace raised with intermediary
    › held for compliance checks
    › chasing release every 24 hrs
    ‖ recall decision · routed to ops
  3. 03

    Closed with evidence

    The agent confirms the funds arrived or came back, tells the customer, and closes the case with every message and confirmation attached.

    /close
    ✓ funds credited 18 Nov 09:12
    ✓ bank confirmation attached
    ✓ customer told
    ✓ case closed · 4 days

Systems

Works across your payment rails, partners and channels.

Agents read and act in the systems your payments team already uses, within the permissions you set.

Payments & cards
  • Stripe
  • Adyen
  • Wise
  • Visa
  • Mastercard
  • SWIFT messages
Ledger & data
  • Core banking ledger
  • Snowflake
  • Google Sheets
Customer channels
  • Zendesk
  • Intercom
  • Gmail
  • Twilio
Teams
  • Slack
  • Jira
  • Notion

Security and governance
for every agent action.

Agents act only within the permissions you set, pause for approval on high-risk steps and log every action with its evidence. No AI training on your data.

Read more
/scope
✓ read: ledger, CRM, inbox
✓ act: email, refund ≤ £500
✕ cannot: close accounts

Scoped permissions

Decide which systems, actions and limits each agent can use. Nothing happens outside that scope.

/approval
› step needs sign-off
‖ paused · routed to ops lead
✓ approved 10:42

Human approval

Set approval points for high-risk steps. Agents pause and route the decision to the right person.

/audit
09:14 message sent
10:42 step approved
11:05 evidence attached ✓

Full audit trail

Every action is logged with what was done, why, and the evidence behind it, ready for audit.

Certified security

SOC 2 Type II, GDPR and PCI DSS. AES-256 encryption at rest and TLS in transit.

More use cases

See a payment investigation worked end to end.

Necessary

Enables core site behavior and stores your privacy choice in this browser for 180 days.

Always on

PostHog measures page views and interactions. It uses in-memory identifiers, and session recording is disabled.

Mesh by Avina records session and form interactions and can use device or IP data to resolve business visitors through providers such as Vector or RB2B.