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
- 2092e72e115a2dcabaf8535ac43c4bff4172416dc4173635ba9c289523e6ee0c
- request
- 13dd02e0ba0220740c883385d2c230bd33d5f0bc3d6631e69441683046fc0f7f
- transaction
- 0b4acd43726795e71cbbf4b47ffe305af341591f7898a0d011ad991fb8cc85ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16959
the chainentry 16959
- sealed to the entry before
- 67b16927ca2fb6c38c13a89db154fad10d5e078307a95d09b3390484623eadcc
- this leaf
- 6820696c1882986c3d534ff020b8cf371109fa4368791f2996f8362bb0977a52
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HOahFuBMW+rR/jA7A5ToKcOyQA6ukBv8vuXIgq/jZ3eZbKKrxlSToDWfNc7nceZv0C6b7jS8tCmk3grq734UBw==