National merchant support guidance
How Do I Document a Recurring Processing Problem?
Create a simple incident log that shows what happened, when it happened, which checkout channel or device was affected, what staff observed, and what changed after each support step. A consistent record helps a provider distinguish a repeating pattern from unrelated one-time errors.
The short answer
Record comparable facts for every occurrence
Use the same fields each time: date and time with time zone, location or channel, device or application, transaction stage, exact message, observed impact, actions taken, and outcome. Include provider case numbers so later contacts can follow the history.
Incident log
What to capture each time
Time and context
Record the timestamp and time zone, business location or online channel, affected workstation or terminal label, network used, and staff role.
Observable behavior
Copy the exact error message or code, identify the step where it appeared, and note whether the problem affected one attempt, one device, or a broader workflow.
Business impact
Describe the operational effect without exposing customer data: checkout unavailable, delayed response, missing receipt, reporting mismatch, or another specific symptom.
Actions and results
List approved troubleshooting steps in order, who performed them, what changed, and whether the symptom returned.
Pattern analysis
Make separate events comparable
A useful log lets support compare occurrences without relying on memory.
Use stable names
Assign each device, location, application, connection, and checkout channel a consistent internal label.
Separate observation from assumption
Write what staff saw before proposing a cause. For example, record an exact timeout message and affected stage instead of stating that a processor outage occurred.
Note what was different
Capture recent software, device, network, account, staffing, or workflow changes that may help narrow the pattern, without claiming that a change caused it.
Track recurrence
Record whether the problem appears at a particular time, volume, transaction stage, device, channel, payment method, or staff action.
Support handoff
Prepare a concise escalation packet
One-sentence summary
State the repeated symptom, affected workflow, first known occurrence, most recent occurrence, and current operational impact.
Representative examples
Provide a small set of sanitized examples that demonstrate the pattern, along with timestamps, device labels, error text, and case references.
Prior steps
List the provider-approved checks already completed and their outcomes so staff do not needlessly repeat disruptive actions.
Clear next request
Ask what additional non-sensitive evidence is needed, who owns the next action, how updates will be delivered, and when to follow up.
Related resources
Continue troubleshooting safely
Common questions
Recurring problem documentation FAQ
Should every failed transaction be included?
Capture enough representative occurrences to show the pattern, then follow the provider's instructions for any additional records. Avoid collecting unnecessary payment or customer data.
Are screenshots useful?
They can be, if permitted and carefully reviewed for sensitive information. Prefer the exact error text, timestamp, and device or application label when a screenshot is unnecessary.
Should staff keep trying the same fix?
Follow approved support instructions. Do not repeatedly reboot, reset, reinstall, or change configurations if doing so could interrupt service or erase useful diagnostic information.
Does a pattern prove the cause?
No. A pattern helps narrow an investigation, but the provider or responsible technical team must verify the cause using the relevant systems and records.
Last editorial review: August 11, 2026. Sources reviewed: current NIST incident-response guidance and FTC business security guidance. Provider procedures and support channels can change.
Next step
Turn scattered symptoms into a useful support record
Start a sanitized incident log, use the same fields for each occurrence, and connect every provider case number to the timeline.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US