Payment History

Every payment maintains a complete history of events from creation through completion. This audit trail helps you understand what happened during the payment lifecycle and who took what actions.

Accessing Payment History

1. Navigate to the payment you want to review
2. Open the payment detail view
3. Click the History tab

Understanding the Event Timeline

The history displays events in reverse chronological order (newest first). Each event shows:

Common Event Types

Payment Lifecycle Events

Manual Action Events

System Events

Event Details

Click on any event to expand its details:

For Manual Actions

• User ID — Who performed the action
• User Name — Display name of the operator
• Reason/Notes — Any notes provided with the action
• Timestamp — Exact time of the action

For System Events

• Trigger — What caused the event
• Rule Name — If a rule was involved
• System Notes — Technical details

For Blockchain Events

• Transaction Hash — The blockchain transaction ID
• Block Number — Which block included the transaction
• Confirmations — Number of confirmations at the time

Using History for Investigation

The payment history helps you answer questions like:

Audit Trail for Compliance

The payment history serves as a complete audit trail:

• Every action is logged with a timestamp
• Manual actions include the operator's identity
• Records cannot be modified or deleted
• The trail shows the complete payment journey

📘

Note

The audit trail is permanent and provides a complete record for compliance purposes. All manual interventions are attributed to specific users.

Exporting History

To export the history for a payment:

1. View the payment history
2. Click the Export button (if available)
3. The history exports as a CSV or PDF file

Workflow Details

For technical debugging, you can access the underlying workflow system:

1. In the payment history, look for workflow events
2. Click View Workflow to see technical details
3. This shows the internal processing steps

📘

Note

Workflow details are primarily for technical support. Contact your system administrator if you need help interpreting workflow information.

Best Practices

Regular Monitoring

• Check history when investigating payment issues
• Review the timeline to understand payment flow
• Use history to verify that actions were taken correctly

For Investigations

1. Start from the most recent event
2. Work backwards to find the relevant point
3. Look for manual actions that may have affected the outcome
4. Check for rule triggers or flags

For Reporting

• Export history for compliance reports
• Use event timestamps for SLA tracking
• Document patterns across multiple payments

Permissions

All users who can view a payment can view its history. The history is read-only—no user can modify historical records.

Related Topics

• Payment Details — Understanding payment information
• Reviewing Payments — Actions that create history entries
• Payment Doctor — Corrections that appear in history