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
- 1db65d088c65fbcaf0f908caca80206fa15225bb2b6885d839fe3b68b1fdfc12
- request
- fbb2df05a0b2e8f2dd76661731d15a63f1abe2e234b6e2d55faa5d9c9cda827d
- transaction
- 3d9954348991d75d8b564287231cc715f80a81aeeb1d18f37a66ecb46cfa948ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8312
the chainentry 8312
- sealed to the entry before
- 9fd66cb81fc35ae81fdc12c7b841316a6db374068a676cb6dd25a3400309bca3
- this leaf
- 4fdfe45df21420ff6bd9cd4d1901ca3d620ac0d343f807c334d0dd361250408a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- an5zGyPlgmEqlVRbu/KBeJjckif1iZDYQ81OrFtzHSj5oOUWyHBZl7F3qlOMMUtHBvIe9CXMjd+YArjUAWfODQ==