Provisional Order on Sent Screenshot Proof
A payment completes and a screenshot arrives unsolicited because digital money still needs ceremony.
Consider the counterfactual: the payment completes and no screenshot is sent.
The recipient checks their account in two minutes. The money is there. The transaction is resolved. No additional proof was required.
This is not what happens.
Someone sends a screenshot of a completed payment even when the recipient did not ask for proof. This happens in a majority of documented cases involving digital peer-to-peer transfers between acquaintances. The screenshot arrives within forty seconds of the transaction. The recipient, who did not request the screenshot, acknowledges it with a thumbs-up or a short affirmation. Neither party notes that the screenshot was unnecessary.
The payment is faster than cash while certainty arrives through extra checks.
Under the provisional order, sent screenshot proof repeated twice must count as policy until someone deliberately breaks it. The first screenshot might have been situational. The second establishes precedent. By the third, not sending a screenshot would feel like an omission. The recipient begins to expect it.
Sent screenshot proof adds one extra confirmation check.
In the counterfactual without screenshots, the payment record exists in the app. The bank confirms it. The transfer is logged on both sides. Verification is available to both parties within moments. None of this generates certainty equal to the screenshot.
Both parties start waiting for visible proof.
The screenshot is not for the recipient. It is proof the sender paid without doubt. The screenshot closes the loop the pending screen opened. It is the completion ceremony for a transaction that completed automatically.
A fast payment develops a ceremony around certainty that cash never required.
Cash required no ceremony because the proof was the act. The notes left a hand and entered another. The absence and presence were simultaneous. Digital payment produces a record nobody looks at until something goes wrong, and so the screenshot substitutes for the physical transfer's self-evident closure.
The provisional order remains in effect.