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
- bc4632bd9ea07a52209f431f262b91a3136d110465755251de2d424a422893f5
- request
- b9895b6baad32dab0680706e66e94f7d25b78e5a160870439ebb9e99dffea78a
- transaction
- 8379bee871d04aa63777ae3f65e3a9dc199afe9f65823cad9bc8cd0c48d6f726computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42123
the chainentry 42123
- sealed to the entry before
- 567e031bc21afbb894917b868269358da8c435558f4a2261e3bde9f27c826646
- this leaf
- 104689a20d69cab949b71542e837b12d86ff60d2c53e2d4b3560a012cedf0686
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qw1zPPUzheM/XorhbCBzU4KBd5EtDL1401kuvmI66nS1UyNrcOvvKDZiZdRQPNVMadB6NETqgM4pcm2NNAywBQ==