FREE DISPUTE EVIDENCE LINTER | 18,000 UTF-16 CEILING & NON-DESTRUCTIVE CE 3.0
Free Stripe Dispute Evidence UTF-16 Counter & Non-Destructive CE 3.0 Linter
Audit your evidence[access_activity_log] payload before calling stripe.disputes.update(): verify that total UTF-16 code units stay within the 18,000 ceiling, existing merchant notes are preserved around --- BEGIN REVCLAMP CE3 EVIDENCE --- markers, and Visa CE 3.0 prior-charge requirements are met.
1. Configure Dispute Evidence Payload & CE 3.0 Priors
Choose a preset or paste your draft access_activity_log and existing merchant notes. Live API keys or secrets are blocked automatically.
2. UTF-16 Ceiling & Non-Destructive CE 3.0 Verdict
Displays exact UTF-16 code-unit utilization, UTF-8 byte count, non-destructive delimiter verification, and Visa CE 3.0 readiness.
[PASS_CE3_READY] • UTF-16 Units:
Non-Destructive & CE 3.0 Verified: Merchant notes preserved • Markers present • Priors: 353 / 18,000 (Remaining: 17647)2 (IP + Device bound).
{
"ok": true,
"preset": "valid_ce3_non_destructive",
"utf16CodeUnits": 353,
"maxUtf16Ceiling": 18000,
"remainingUtf16Units": 17647,
"withinCeiling": true,
"utf8Bytes": 353,
"nonDestructiveMarkersPresent": true,
"merchantNotesPreserved": true,
"priorMatchedCount": 2,
"hasIpMatch": true,
"hasDeviceMatch": true,
"ce3RubricPassed": true,
"overallVerdict": "PASS_CE3_READY"
}
3. Why UTF-16 Code Units & Non-Destructive Delimiters Matter in Stripe Disputes
Prevent silent truncation of CE 3.0 transaction IDs and accidental deletion of support/finance context when staging dispute evidence.