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
- 7b7f11fd39ebdbe74b80ef0e21abb041e3d00d85dfd65623f89e7be854b90c69
- request
- e8085d07e55d1cf10f340f14ca5d4aa52d4a3241a3ca23ad8da0785d2fdea0c7
- transaction
- 9bbc9142b379f2c90bd19cce037b1b36c35f7775545618e48bc05cb961230395computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61616
the chainentry 61616
- sealed to the entry before
- 20b51d9e2ceeecf1f0f76196100f95c5dc9b3bcee4657aaed8c20423f959db37
- this leaf
- c6669da2c7f52516497a1b4e2726567449bfe9f963336a53e29c8000267aa624
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VJch3Tes5OpU9BDsdIsHHslUxSCRbZzaV5dtbURSqxx6dkOYniQCC0riZNJ6eJdByzc0EMK0NEiU7yPkujd0CQ==