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
- 109b59141ce3b7f682e31364eb28362d71b72381230085227cc541ceaab79800
- request
- 4bea4cd409b2b92f9b293edae05aa705a774cd9ea6a664a12c453f0ee3454f99
- transaction
- 255e9d5ea1d6ebf02f3ef7b544c576900f47fc029426981dfa049a78e1b69eabcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33679
the chainentry 33679
- sealed to the entry before
- 44d382336427632c8a80f3d1bfd3c047a753a44f6e540f9d107645d3f6019df7
- this leaf
- 68e9910252487e250c6b79d381e5c911e63049523cd9bf6e6347d20a62ffec2b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tZibNPIp0su8cH3cdY9wc0kU4+0sKgzy7X8aED3E7YrgvqTxItnRwToX9ZSTJWAZtU3DXqorQEn1FqiTW0Y/BA==