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
- a74175c336c6b015144086e06db1c46de42d6321739e8929dc06eeb6a1924492
- request
- 5016f59a55457e11e27489bbfa4bddf4344bae28e034259c847756d9c7d3c027
- transaction
- 3556ab6462b57df3df88974cbd906170d11c0e322fd45678297035c41df5a1f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71257
the chainentry 71257
- sealed to the entry before
- 6d92ef61b15072e64a01c0afd979230d740d24cd26340c066d3c8316d492722d
- this leaf
- f378d9a82e72c9aeaf66449d2fa69ffbf55b1de82498852ac38742031044ecaa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Bb6v1mcONrWr5cUchnDm5qiS3c5kh1zkP82t4tEhFFoPspxQd55FB5fgOIOVcXSBoWe3MaO1jL7u6CAXtKL7AA==