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
- 5fd8af169aff08590074c60de1e01b05192ee10acc09e892b423e4a3ca158505
- request
- 4349d06b9dba0b1dd69fbc5d8209d7d985789872f57c9324584ec16dddec7499
- transaction
- cdaf75cc95dc90e9f22f6366746dbeeb7e8810b2012669b864519ea8a2be2cc0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27186
the chainentry 27186
- sealed to the entry before
- 7f3857aba253977b2ac948ad6a8c7c0f5d9b0085a4f16746e648dc8b29d18ae9
- this leaf
- 346c6a2b14a632d2325f07b57fc681edf861098fe93a86bbc8fe1b086d93c760
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t6CqWAB8NMkR4zxWrR5hEs4a9dJMzZHKklmO90DI5v+Diswae0ksapb302aXR2GUCCWv/+orCWwXz4esK4slAA==