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
- 53e7fda4d609ef60d5d2b51d0d30f2863fa1cc2b70b9747c5de52787d7fae389
- request
- cee343c8598d04ac45aea7b9e6fe410d36a231385256deed66484666d9d8933c
- transaction
- f3601a2fb4fd45fe3546bbbeda1500e1ad35e409f837cb09cdd5c8de1752e3afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29573
the chainentry 29573
- sealed to the entry before
- 3754842d7700139a3a60b3fbf23f5ba487db7bcd56430a5392ab0421cad85e15
- this leaf
- 9caad53a1b938cd05ec86697ff6c94bf80693224183d4a59786180e6aa4d2bad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jg/5owa68RUOQ3iBF+2u9iJpHqD4HIa7wtYty6AIkUaY8TmpqjBnfnI56tEoYLOntUomMPT8Z8uhhpeLcdnTDw==