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
- d42eb0c1990f42b1184af092783065a892a9ae0a7cee6e98133adef200200311
- request
- 425370a71fbd613185a3be59cfb413e546b345c88e34da659070e9462a072769
- transaction
- c18b7ebc90a13b380c6a004c6e6b3b853af7e4693a303f63505f5c0c568260f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1355
the chainentry 1355
- sealed to the entry before
- 62c8bd52a943191f345eebcdcec660499dffc160694de585db2278d576d0af94
- this leaf
- 2bf845513d648aaeb58c194b8ee264aab0186d08dfabdfc8d27cde2fc6486bd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z2506nTsAxq1DaEdfIICAB/sETtnfhr/J5ULg1EaGwG71/qjv2hz+bU9ZbEqmeBpHvVEwTsF2pONcw4dX+UGBw==