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
- 78e4bf7f152bceb4781c80e8ddcb847337d276b33c4f67b60a766e8ad06b98cf
- request
- 6b33ef2404220773e9d28f5788982a98e12772a18572bcb331d1bd0678e0b2c0
- transaction
- 2ab96269fcca6e0a2c4c1f1daa65a0eb2352af89cf9d01e563befc1e8fa28f47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42184
the chainentry 42184
- sealed to the entry before
- 496d369d17aab877128542b09c44ebbe0bf409a771b40721a2a99ac1cd3f7797
- this leaf
- c42431be09e13c165a185c8fd49e39e924364130d814162a3772c9cf3e07e4fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aA14DraPNz8KtCaDQlyFruvGu/eGFm8pecV8YSxOuw9GjHTyqBSX+YNxpH1OQHNKT4acdd42ie35U/5IrmFFAg==