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
- 77356f24f28f8fd73fe1162676c22473962039ee346e5231a335225d5e737073
- request
- 53b71eb596a76d260c7138476fd73eea74cac4197aa1cbd5f7811e5657acdd46
- transaction
- abd6d42d48831dd6c95b16a4c099678b20fc9c59cb3088f6a7f8615be20d1b50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25072
the chainentry 25072
- sealed to the entry before
- 49f796622766995f9a8833f815d067260506ca0283e1abd6c05fc9f2b246ff51
- this leaf
- e932d8e30ec67496967026c3598922331b35a2aee0635672bc4d5dfeb24ba2a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FdZjW0w4n3n5b0OtiQxr3i+VTZAT2zmX4aQiZUcoM10wN2BU0xizFpd5R5hRyPRuD+9dSuRiW9xFmPSkbZAKCw==