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
- b38ad434659652cd5900c84d609414b7daaed15284bf302048853f5daa1e4efa
- request
- 70098a3a1c70d9698ea409dff390a995ffe044829dda2feab4fa0849856e45e7
- transaction
- d6407548223e0aabc9d7c582cdaa87de86cfd9157ee559193a6537b452de47a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28248
the chainentry 28248
- sealed to the entry before
- 15ab1f89c10ac7049bcc9e3123d4b65e3c7eb4c88884b6eb7c14d8ff7ff488fd
- this leaf
- 1022a2c143135c1f2a1f839739adf69b87a62c3dbd7aaec5304bc6d2dac56344
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- khe/u2f62EHYc931KyCefafEPIqF3WAc7OZuS9sEB1gWq7+hL741NLYuDTTXcrXnNzYBrCwaI97J3TF9AfjXCw==