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
- ee12874f918b03234c1c024c26ebbabef5b627c65b514ce274e4b30e7b8968a0
- request
- 7b46af15047b28043e57951270a8e9c751f79bc1e693702238bb009b6d743ce9
- transaction
- cc8d28b846e40081fc8ecfed4825b7895527cff709d34221b9d18985215e74decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24136
the chainentry 24136
- sealed to the entry before
- 70014a19efd6356c088cb83e4949d663c63f2eedf3bd921aa05b190f8e5b1c6f
- this leaf
- 72ceff7df6fe593d89ddca72afd66f8670a346e228bd5cda4b08d37094e8966d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SMRSUm6S2e54pADHfAYgtBfVBLUpAxa7Kg8kjpShA9i02MiObgo7eaKKAnpbaS+ZPzBm4dpkkJdxZnltNKnuAw==