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
- cc6234931ebafa30db2c9af15c2d71e382d8d5498fe5fe46f878c05a3f55a61b
- request
- 33faf87c3b281b13ebb3a2eee769be310f3ef45ee093fc6b4d30a9611de3ebc4
- transaction
- 89f6b0a336543252c992dd7ca528a0dd0acaf84ff97e086a5ba2a14fadb56995computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60053
the chainentry 60053
- sealed to the entry before
- 347d0de53a19e79a65d42eeafeb0a5fa97e270739e6c28678e6c61a434924bfc
- this leaf
- aad3082eaa3e9ad0d1050820f5fdbf22fc50e4f3fd5f14ac03e9719e85cb2938
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6bsgpCsYSqeec6jJOCpkvnLyTDiHikWeS/ZTGSEooY9vfoeaQnsvrJIW/VJOSwScjweRhz+EUPZhIUAxdQTxDw==