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
- 77b276a4be96f6e833a1b0440f09b9293ba68463468fbde43e4ed7d20dbac2ce
- request
- 1bcbfaafe2e7e67bd559f3a6d523c11cb6777a59b8b5708cbfdbf4a7b540c27c
- transaction
- 908953d48e8bf95d86f6128b3a2202ba7339ed1870efcb931a108446c605b2fbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40617
the chainentry 40617
- sealed to the entry before
- 5070cf45423b7e2b1ec74c5f6811f30a6efb65f1bd9b629f534b1719b8db7005
- this leaf
- 75238585916538a6484dc11643caa099e6914604a49ac20ef2740fcf6a589860
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eK0uB3umaTropxLk9qX1hyuzjmG2jGfMbMXRt1AquUqd6V2xtAvVNKcGvST5TcoaxgrE/J3Rmm19th7DsvbtCg==