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
- 2ac2732f0c2db186508e85230f19b0eef311ae75a10c7181f87c709999fb0546
- request
- 96cd55d53c59b1cbc7e8fa6c0cd6eff56ccdccd7011ec0e8462c10fc63d4b9d7
- transaction
- 3bc309ac5de2a6a39468174b5ae2db31be3e2f21ad71e81a3b9e844714a6b85acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36012
the chainentry 36012
- sealed to the entry before
- 67daf8aa564f199d38d6bd1c56a1d13b7756441c2189b2a95966bd5f7c7062cb
- this leaf
- d970dbd5aa8fed4f92e486a6afae757d9066ead2dbd6e05d06e593f209873cf8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2w+XaEpGsfs1CkYM/VVpWOwLyyp7nLc2dll3HcR+9o0TQ/4+mffX0IgpGskOa/2HmRsafIC3uvlOWZqV9Xu8Cg==