Payment Operations Research
Auditing Card Terminal Fallback Documentation During Dispensary Outages
An audit protocol for checking whether a dispensary can document the fallback path used when a card terminal fails, including the customer remedy and the reconciliation evidence.
Key takeaways
- Audit outage cases, not terminals, so each failure has a customer and a remedy.
- Check whether the fallback was approved before it was used.
- Report duplicate authorizations separately from unresolved payments.
- Verify that the terminal batch and the sales record agree after reconnect.
Question and scope
This audit asks whether a dispensary can show that a card terminal failure was handled through an approved fallback and that the customer received a clear remedy. The unit is one outage case tied to one terminal, one transaction, and one customer. The review examines the terminal state, the fallback used, the customer communication, and the reconciliation. It does not judge the payment provider's network or the customer's credit.
Set the scope to one store and a fixed period. Record the terminals, the payment providers, and the fallback options the store has approved. If the store changes its provider or its fallback policy during the window, separate the periods. A policy change can make an old case look noncompliant when it followed the rule in force.
Include failures that lasted less than a minute and failures that closed the counter, because the short cases are often undocumented. Record the time, the terminal identifier, and the staff role. A sample of only dramatic outages will miss the routine gaps. The audit should show the full range.
What the sources establish
The PCI Security Standards Council sets the payment-card data protection context for terminals and stored records. FTC business guidance supports clear customer communication and fair remedies. NIST privacy guidance is relevant because outage notes may contain customer identifiers that should be limited. The sources support a process audit, not a legal conclusion.
The sources do not establish a required fallback method or a maximum resolution time. They also do not tell the store whether to accept cash during an outage. The audit therefore measures whether the store followed its own approved path and documented the customer remedy. The report should keep that local scope visible.
The sources also support separating the payment record from the customer note. A transaction can settle correctly while the customer communication fails, and the reverse can also happen. The audit should review both. A single reconciliation result does not prove the customer was treated fairly.
Definitions and measures
Define an outage case as a terminal failure that prevented a sale from completing on the first attempt. Define an approved fallback as a method named in the store's written procedure, such as a second terminal or a permitted cash sale. Define a duplicate as two captured payments for the same sale. Define a remedy as a refund, a reversal, or a documented explanation that the customer accepted.
Measure cases with a documented terminal state, an approved fallback, a customer contact note, and a completed reconciliation. Report duplicate authorizations, unresolved payments, and cases with no record separately. Keep the denominator as outage cases, not transactions. One case may involve several attempts.
Record the evidence type for each case, such as a printed receipt, a provider portal screenshot, or a batch report. A verbal assurance from a colleague is weaker evidence than a stored record. The audit should show the evidence type beside the result. A complete-looking case with no evidence is not complete.
Sampling and collection
Sample outage cases from the terminal log, the provider portal, and the store's incident notes. Include cases handled by a manager and cases handled by a cashier alone. Include at least one case where the customer left before the payment was resolved. Record the staff role and the time of day.
Collect the original receipt, the fallback receipt, the provider transaction record, and the reconciliation note. Mask card numbers and customer identifiers that are not needed for the match. If the customer was given a callback, include the call log. A case that depends on memory alone cannot be verified.
Include cases where the terminal reconnected and settled automatically, because those cases may still have produced a duplicate. Check the batch report for both the original and the fallback. The audit should not assume that a reconnect erased the first attempt. That comparison separates a genuine duplicate from a transaction that settled only once.
Verification pathway
Check whether the clerk identified the terminal state before retrying the payment. A timeout is not a decline, and a retry can create a duplicate. Record the message shown and the time. The audit should distinguish a documented decision from a blind retry.
Confirm that the fallback method was on the approved list and that any cash sale was counted and receipted. Check whether the customer was told which method was used and what would happen to the first attempt. A fallback that works financially but leaves the customer confused is an incomplete remedy. The customer should be told which method was used and what to expect on the statement.
Review the refund or reversal against the provider record. Confirm the amount, the date, and the customer notification. If the refund is still pending, record the expected date and the owner. A promise without a follow-up date is not a resolution.
Reconciliation side effects
Check whether the end-of-shift reconciliation matched the terminal batch, the sales record, and the provider settlement. Report unmatched transactions by type, such as settled, pending, reversed, and missing. A reconciliation that only checks the total can hide a duplicate inside a balanced batch. A batch that balances in total can still contain a duplicate that the report does not show.
Review the reconnect log for transactions that uploaded late. A terminal can appear offline while holding a payment that will settle later. Record the reconnect time and the batch number. The closing lead should sign the reconciliation after the late items are explained.
Check whether the outage affected the store's cash controls. A sudden cash fallback can create a count or drop problem at closing. Record the cash total, the receipts, and the person who counted. The audit should connect the payment failure to the cash reconciliation.
Analysis and reporting
Report the number of outage cases, the share with an approved fallback, the share with a customer remedy, and the share fully reconciled. Break the results down by terminal, staff role, and time of day. Report duplicates and unresolved payments separately. A single completion rate can hide a terminal that fails repeatedly.
Inspect the failures for patterns. A cluster of duplicate charges may point to a retry script, while a cluster of missing notes may point to a shift handoff. Choose one change, such as a terminal-state checklist or a refund owner. Do not rank cashiers by exception counts when their terminal exposure differs.
Report the time from the outage to the customer remedy, not only the share resolved. A high resolution rate with a two-week refund delay still leaves customers out of pocket. Show the median and the longest case. That tail is where trust is lost.
Keep the outage cases in a log that the payment lead can sort by terminal and date. A single case is easy to explain, while a pattern across a week is easy to miss. Show the duplicate and refund status beside each case. The log should be the first thing the manager opens when a customer disputes a charge.
Limits and next action
The audit cannot prove that the payment provider caused the failure or that the customer's bank posted the refund correctly. It also cannot capture a customer who did not report a duplicate. A missing complaint is not evidence of a clean case. The report should state what the store can and cannot see.
Set a repeat audit date and keep the definitions stable. Assign the correction to the payment lead and give the counter a clear escalation path when a terminal fails. The next review should test whether the same terminal or the same fallback gap returns. A useful result is an outage note that a customer and an auditor can both follow.
Record the date the store last tested its fallback path. A plan that has never been rehearsed may not survive a real outage. Add the test to the monthly payment review. The next audit should compare the test result with the real cases.
Sources
The sources below support the operational, privacy, and consumer-protection context for this review. They do not measure this store, and no source is presented as a local benchmark. Check each link for its date and scope before reuse. The operational finding comes only from the store records described in the method.
This article describes a measurement method rather than legal or compliance advice. Confirm current requirements with the applicable authority and qualified advisers. Keep the local evidence separate from those requirements. Record the review date and the owner who accepted the interpretation.
Reviewed by the DispensaryVA editorial team on 2026-11-09.