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
- 911335151bcb88e832539d8da1a91d6f31cb949dfb34ea7a939c77863719fa2d
- request
- 89e57b2d5cc6a77641b9927a67bd840f8b0611e5760c70aff861828717de2bbb
- transaction
- 962942f2b4470ccf186a622e1416870796eb008667b5cded0a2b68984648c3c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74403
the chainentry 74403
- sealed to the entry before
- d137865aefdbf6d357f37bef71ae6db4e29bae3a7625fa22895acdf0deed37a3
- this leaf
- 645120e02f3fd3a6a10f209f8b721f10eab16e8e9e4c7f2b9c247570ad99ce1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sC9hqAAKspU6RPtaTOYzTX6u6Fd/J+kqIUpKJH7LdUz4ISU5ra8BseDvzFlajoW+OiLvhxb1mLtDXebvO9baCg==