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
- e843a3c790d82ee740f136da6026b680b574d70fb3223b7f1a29b315a15e9c23
- request
- 89421adcf2bbd10b5f1469a9a43160beb39d0950bdee1cee4714fe3330f255d4
- transaction
- 8da75f8af19d0ddf804c19a15a6cc6779793f99fbe9f5120b23b6f4a770565e6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43756
the chainentry 43756
- sealed to the entry before
- db9b6653cf5f618c7f2e2f029f42ceaaf52d27b2c9ede16612289d3fc617156f
- this leaf
- caae9bb896508db02aebebf8c259fd84abbd9cd013faebd6217cb26f403afc8f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fggeuu5kNKKNcfRzj6xQPayVJhuh82hY5ZWdnF7fbUI+T1yEvihPP4gg4rH4T7UPfUM3TV5qfrxuqlLjF/E7CQ==