why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 13176a939dfac26f0241b545b86713e8f35508d1cc90b3ec06c6c69e12077734
- request
- a1d8a560dedee834e55d21cba985127661695ff88416ee6f2139765baee283b0
- transaction
- ff42d6c3c69da40181ec2fb8597caa4a752f021fbdeab50b1fafb84b6ab3b2eccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48748
the chainentry 48748
- sealed to the entry before
- 226f68e4e5e9d790dcca0b090ba5e1c83209837eef00366387598f7df64728f5
- this leaf
- 808ea13f4ae1f5fa1c0748facc3d2603f84ec08e2025cc6851691495c1eb29c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DeRqcLKxzyUrXsXG4WuMaEwjubhmiwHNfuNnE620xUSYgDrVR+LmC2u+LMS7XmMpJb3bFtrKhyN103RoFWS4DQ==