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
- 1e45c97a6e56d9d49c9b4ad66eea18c6d5b51889f4aeb255e6870a1912ab841e
- request
- aef15e6d153926a34033cd71ad15736e485511261d96e812e5480e3efa60a5d1
- transaction
- fb0c4bc7d19bfaa38a1ccfb2db5f6cb00f5a725730387a25cfe733001c0f55eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28624
the chainentry 28624
- sealed to the entry before
- 9d5d2dbd2372afa256f3bfa37b11c0e9e6fae2d203ee351c852d30eab19fa3fe
- this leaf
- 4b1449e27601dc9d64dc91dd810fee30c1d7b5d798ee27ff76e0e8c9110d6a74
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M5QeH4rF0D0r2HM6WVnqimsqXuiNLU/OxTL4D5Y559Q9qUWcZpaZVa4WOUwImZ1+OZ9dAsyyv0xj4HnCHpLzAg==