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
- 8f601e460b3edebcbf042debbf66b0144c699bedbfd2dfd998e509aa5b25289f
- request
- ae06ef340774a039035bac0d9a8152c1eb1c50cdcbf26bda53b9dacaabf7f978
- transaction
- 86d09fd18b18950d5fc7579df04aa65a8ffac1307f373e596dc38387029fdfcdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48159
the chainentry 48159
- sealed to the entry before
- 942c2ac4ebb03e0f0d9e419ce3afbe3b23d566ae93228a4b18038d1ba7e3d230
- this leaf
- f7e6199749561bda8d9579f06328bb92a3adb6856deb44c6717f6cb69833f8f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7stxPVRji+JHP50U+60sLRlk/LQsJ1vwTZfENJaXTrPe7wKbMkgiLjI5qQyQDO+cuuVHpAaolrARF9UJZZLjDQ==