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
- 0cb826be358ae788c571e30b88bb9ab4aaa493df703952157c2d478220929471
- request
- 1c66f667e4b44b958ab07d748a5410ab4d63ad68b0ff65cac65eac0937ca2c89
- transaction
- f6dcee2666e0061893f734f84e92c2f5f6ac17b6631a7a516d81a44a79f0c213computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35607
the chainentry 35607
- sealed to the entry before
- deb38d71b17e26667abb336035492a2ee27e19f81589156ddd65ff9aeac225b9
- this leaf
- e6cf6dade10604c8af4708a87f423f3141fb7c42ce570051bdee723e312ad489
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oIKSI4/+Ry7KoN4YLBqgo6mLfbE4H1oYu2I2yGX47kdNWoEKOYMx1lsE1WLwJqthCwe2r3FSzK76KHD4bCTGBw==