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
- a264e6d307c87981841227d1adbcefb659ca9c8e3da7fc41a52b80034afd77c8
- request
- 941527d75a4dddef834642015f3700e9da723be6ee234868ee8a0dcebf1d5dc1
- transaction
- e81c9523990bdbc279e0a7cba1d4d86e92df7bfe05d57443e82930027cc4f87fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39920
the chainentry 39920
- sealed to the entry before
- 61da192dd9bcde1582e6281b945d96833f4515c950ce91feb785b8257924f4af
- this leaf
- 529ff4bc8a636ae2138c52f6598c09f2f4b2908efad080cc8438ba63ebfdca18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZA8Oik0aYqkx6W9Yt8NZQLcEJmEs1TwJxx8ZOEB6r2wJ/uCnMwJaWtDeREPNpc6H52pTWbdsbVIm2e53VxgqAQ==