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
- 4c80608ade298df8607e947917b8b9ddc064bf3866495880eae2454457fb835f
- request
- 9ed1e953d0ed1cf02f7cb0de55e4a4c30c91d097d808fafa11fc66dd2bac24dc
- transaction
- dbc975cf715c07bc58cdd6b4a870bf56efff07db2d49def6fbf5052a36a85977computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30344
the chainentry 30344
- sealed to the entry before
- 16200f0c967079bb5db0d1ffa55eb3142737376a0a0ae57b1a5d31cb4e6c8377
- this leaf
- 3575ffab946c0a3c8a241d488ed9782f6726713579a4153747da20dabe626679
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b3VnnxZpuvDC2DlsTh6aM6SAmzShE7VdStWBU75aAy8f0SU8NE8dj6Yu2tZx/1TXm0C+UF1pnKGU1SwlIO1HCg==