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
- 626a47d517bc60b308856dc272c3c101a4a2b3383237edb4d2ee37da91ca59ca
- request
- e9eef238805877b24cae04c67ec20e7efa1d8e96b1fa56dde2007b27adf3dc82
- transaction
- 37684b8da2f8ebaa57dac05e7db943b1200b39d51c0d9660c452c93be170a3efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49828
the chainentry 49828
- sealed to the entry before
- 26f3439b7abf91a5cd473dee9459d9ab0d55a6122c46b7fc015e4c13d32ce3e9
- this leaf
- 9e78c0629cb9df3787571c015f332ad20d84920bf650297b43649fa8620bc104
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FZAA+PnG7GXKIY99CkthKEdjj4zV7YUSPcSShtgTSw9KyyMw/K9VhQnboXlrtSA3Ti24oW6cmtI0tIBzg2ZjCA==