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
- 6820fc13d14846053dda04f043ff615b6699ff4adcc0662d1deb2ed06354d24d
- request
- f377264ac356d67703e0ef8e28b5265da7e74f906c332b4aec054534589077d6
- transaction
- d79bc8290e97244c43f490745db90874fdb7d7144c159f2047fed5420385ff55computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39780
the chainentry 39780
- sealed to the entry before
- 0dae5f00edfbeebe560ecc8db6a6157d027f2ea384a2816e84937f262cc23212
- this leaf
- 09c824ffbeaaaa6ef0fe0da42ab35115dd8a6bbd0667daf7c5e33ad852e76b7e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kJa3jPz5EUMCtiCj1GAawgo+A5z76rpCMmhUvMiqLBSUbvHSk7SbDEHvxgMWH7qX1AEuz2eG9WqPEN6zJp6vDQ==