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
- b5ccb6e24e58e776f5484534310f4c436f58edb975c1cac7bc2ecd40f152a33a
- request
- ae8e4685864026a1c0abf6edd2fdc394d472e5818f373727124075bf609cbf84
- transaction
- 7c7d5c656147d0c0ff49e231176a8df54cf111ffea648d437137c72299d99f2acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1720
the chainentry 1720
- sealed to the entry before
- c0e2c5402c0ce4791252b83bcc63bb2ec92ad0363735cc9ce49e4d646f09ed90
- this leaf
- db7cb5ab81f05ecefa90a1fc079f203bb49670b17d25aa62a2ca60e778935d92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- liHIuoFyKWU4LY5XPYlo85dpzqoCd0YEaxzGmKEMB2MzpnwFtT7YaXJUPXo5yefviz4rivxR7HHRXvuJxa6+BA==