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
- 15373fa01fa51197697b7349dc8517d222edbcee57cc78123bf09c51a55da39a
- request
- c257f4c55be9108b4e7ad5f98a35e3315bb1ba1b9dcf672a7623a96779caffe8
- transaction
- eade229a6ed42249e2f2f9cce367f7eab406ff8622ea6f21b1e5188d565be1fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25372
the chainentry 25372
- sealed to the entry before
- 0671f8c99a26a3212100ac65578c84336d9a2c3c73f68a34dda21d414ddbdfa7
- this leaf
- 37ef69027e845031346b49458c79b8a59788dac574eb039b9ac300dceaed3420
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZTKAyE/3TmTGasMlrI2ayMO7rmcHIJuBAeDI7opmbIXpMkAXQFAhuoH8Fgostwcl7NBvMkJFq3jFrTBdGuCQAQ==