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
- ad915ddd2360655ee1ef457d73d94fa114b1804398198f920d90233d79e85fca
- request
- dd1d17c280c29e3f15f5de36f3b230e578a22b0122a6c1c3206d295911e6396d
- transaction
- 69ea919c204ca8247d378f5fa33b5080fb6bde989cd5329b5e92e7cea090aa58computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35171
the chainentry 35171
- sealed to the entry before
- 0e8f155e159194480b105322ac200a8cb19cdb38f92c316dde8785657df1f1ea
- this leaf
- 4bb225fce9c5b6dac94bba5536074099a79dee6c8be87a7404949230d813e71d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RRLVC1Ivl62zG0rEBkfrYy3yaByLOQRfcyTNuj5GFYu8JnAqo8XMHXry22hxjFUKW2HhimAuyDA3/dE2HPZSCg==