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
- d235fe5b8e763cac2302534901808d42b7e26463cdbff325e4bb18c054fbf573
- request
- bc828037b81de7e889c942814fd5a84a9f62e3949c6ad38f6e7413fc27aaff28
- transaction
- 457efbbc249250b53f9817f17f43bb9bb5dca2223dfbb4a52d530fe1f5969541computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31180
the chainentry 31180
- sealed to the entry before
- 5b4dd1c67010edac98a3815afee08c2405df4ef4b7928f8f7273aa9677f4e652
- this leaf
- 5a4d29b79eb604797936748e2cd51fb5307f6d65d09676c5c6c0e4eabe71a847
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8hxhD/MKMSsC8MEEN+gDJ+L9bwj2oFCumAVGPkehXaLysJMr3UAYtm8asOb6cxm0HOTA9PWip3y/VoaT06oiAw==