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
- 357f546fb8f79d544c199cb70129a3deb72fbfcb1b62a15a80bf58c6eba2016f
- request
- 03ab5d9554bf3987c729e54a1424ac7690bfebc51f6cb4ac01d3eb52f6800853
- transaction
- 39e47177b9192ee1946f998e60465d1607fc48bb342fffd55e38446bbed089f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24342
the chainentry 24342
- sealed to the entry before
- 3c462e10a42f870662895316710ae8bacbeda548f7d87986c376ad969fad6d44
- this leaf
- 8fb345df99110436371db5631544025f412df1982c4389191eef5ee7bc44e1de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hsCSD3gjDf/lQqN4y1aRjVNt9PWELOXlRzlDPZY9S/hXHRUXsrdp7GkPnTmkAep35xPNBoBywX5NRXKuOVDBBg==