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
- 430664a5fb9d961867386b501465e434e7bfaedbfc333d4c2ba479b6a4a09430
- request
- b9f22f9d35e731299eb1cd48006866d77b02c4ed326bebf143f2316cd223020d
- transaction
- ba08a15974dad7dfd674dc1ab010204f243f511b1fd55ef6b21c0e90d9b3cf4fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75595
the chainentry 75595
- sealed to the entry before
- 965f4af483c4fb49dbd7c39dcd484cd0d53b2e9a93cc55a005534954ca424195
- this leaf
- 1a89239ebe3b19f65e27521fd8808c2ec1ac673d9d44d1a599b49e9ccf966627
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oG232+XDf9EfXxwH9sGAjr7LbqVxgSyuQMa7yiClpFUZvXHfbssDHwbNLxromww/t0Lr+AfjOTmn5qNE9cM7Bw==