03.07 Transaction Investigation Timeline

Status: draft for discussion

1. Goal

User must understand what happened to a transaction without reading logs and without asking the development team.

2. Questions Timeline Must Answer

Timeline must show:

• who created the transaction;
• when it was created;
• which payment method was used;
• which routing path was selected;
• why a routing option was rejected;
• whether fallback was used;
• whether a request was sent to provider;
• which business result was returned;
• whether provider callback was received;
• whether merchant webhook was sent;
• whether manual correction happened.

3. Merchant Visibility

Merchant user sees a safe version of timeline.

They must not see:

• hidden provider names;
• internal provider configuration;
• raw provider response.

4. Platform Visibility

Platform user can see more details for support and investigation if their role allows it.

5. Ignored and Suspicious Input

If provider callback was ignored, rejected, duplicate, or suspicious, this must be visible to platform users in timeline.

6. Investigation Standard

The timeline should allow support to understand a normal transaction issue without reading application logs.

For MVP, the timeline should clearly show:

• transaction creation;
• routing start;
• selected route;
• skipped route options;
• provider request;
• provider callback;
• ignored or suspicious input;
• merchant webhook delivery;
• manual correction;
• legacy migration marker.

The goal is that support can explain the transaction result in 1-2 minutes.