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
- 2a979b0bd75622bd310f869278aa9e4fe37393e57381495c12148120aa264d45
- request
- 38c0e8bffaf7fb1f8bbe7ecb8867736a9d7114732f8b7b7130abf5a56542fb2b
- transaction
- 34d8665f56a1467074aef460644899c361393640076ce78002cd3538e966e4f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3728
the chainentry 3728
- sealed to the entry before
- 07a01f07f0d109599d33dde5eda181edd4d935feb5a964e050782c3d17c5e6fa
- this leaf
- 6ba11bfd5f4d91a948162e2ac00c50e7ab0e5bcde79f0e88ecf0b17541343806
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gTC87XPRhN/h0zZQqSBAkh9lT3PiBYW5FdvaJ/Kpf/g7lDjBjnum1STKW/dp52miu9tXKEFt2Dj3UZBXYYehCg==