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
- 4548c70967f41ac2bc614257bad5aa5773fa14caf655179ac7f31533856d8c47
- request
- 4110f8c99bf61d6ad01e109f90065da70ccc910be14517db81f77007b438be0a
- transaction
- d08cea61da11c609e537208f6e6bfe96aa3aad440d90068e62ea2fb2bfd2c7e9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46752
the chainentry 46752
- sealed to the entry before
- a8e691f358919ba69cf2281d20044f7641e72494835fbfdd8b815a736507d992
- this leaf
- 493b370c8e14c119e8723ab4db768523dbb5e74113f4c6d431b0a6c59c6d9b1b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XSmC97u4iadyXOsCSul2+9YYa+DiJapoqUOaeUtjayO5Bz9KpwIi+atp9N2A5ZsKFYFLgum6SSvDR0pMvvsUDg==