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
- 7a142e7f294c52f07367d8f55a29f68c5daf7bb2eff93317d34aa742b264981d
- request
- a5e02ad738fb507bc438e5bce46f50a2cc66ea930e73b38b9c364369fe89cb1b
- transaction
- 49561ff164300ff9ffd2784dc29aa90226807408c3bbabc052db8d5d22808587computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42811
the chainentry 42811
- sealed to the entry before
- 9dd63a90cc39b8768ea6452a64d23a2cfa958fe58a99132ed5938a70ddf50493
- this leaf
- 6f038eeaeb85900150b0bc8a850d5c0435bc1cf86a436b137322f106e416a10e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +qYqT2RGig/Qefd/v8cVyQfUt1myF0nCsWJ+9GN8h9UetuClW4X0GzmMnXPfk3fJoyEJOrShve9ebixFQeTADw==