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
- 111a64ff6b24d222da26c0247cf60e66ed1f3831c5ff5644184498d51e54a047
- request
- 7f2264aa0f48ffa06d2be7a9ad303343f87f36dce978454ee81eef0f19e74a18
- transaction
- 791f55309bb008231756bb87c7722eb091027da6e8772f3d4cd8fe9e20e83b53computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30934
the chainentry 30934
- sealed to the entry before
- 925145484d9a32bbca49f8416a7f64fe33955c8c8af6a1c00d1debe949b8e7c3
- this leaf
- ddeddf278621d00635c07a651e8e9406bda63e02606fb8f5e52cdeebab6f1df9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ImBBQ+Bij5nrTSUOiNXKu+3ceJCEb8EwEneq5Ejsfi9XlBLP4INrqNNzcVzXfH7y8dLBxXf/Erhr/NyQ2zU/Dg==