Key points in this article
When the card fails
A card anomaly can block a session or double a charge. The first move is not panic but sorting which scenario you are actually in before touching anything further on the device, because a wrong step now complicates the fix later.
The sound view
Sort the scenario before the method. Visible records of the attempt settle most arguments quickly, so keep the evidence before contacting support and risking a he-said-she-said later, because a log never changes its story under pressure.
Step by step
Stop the session and keep the scene, confirm the fault with the responsible party, and retain the log. Order matters more than speed when tracing a card error back to its true cause, and a clean sequence turns a mystery into a closed ticket. A log never changes its story under pressure, and the card problem that was recorded properly becomes a closed ticket instead of a mystery that keeps resurfacing whenever the same driver returns.