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
- 35fd183383b7eb0465b197451534e8e411d25110b270b1f3a86eeab749e5a863
- request
- 8721c1af52b3a5e9655e3b9b7c16e33607329d06712739fca14d952390697ece
- transaction
- 6a408413e44bf30d903ddd9f4a6a070c41a5eabdf4031c9cfc7271ba6f05767ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10206
the chainentry 10206
- sealed to the entry before
- 148de9af8229b1ca91ffe3815a7cad335c0d2a47cfa366dae61d29b0eb5a80fb
- this leaf
- eca86a67c3838b9fa18d6795c8af50442b39627778c167f082d3579600a39804
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RbbLoLt80RsmKxbVQalUhXh8Fpim4izYUCRBR1jTb1dvSkLYhx4OwR0vdLu8eVuN5U/6j89Uv4ZZ/BbRUcZ6Ag==