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
- 13fee161ae64efbc233f4de94630526889dcef0550123c765e0eb0a566fb8952
- request
- b09d7473cfe00ee3cb26230c8c9bf06651496ac26fc53a05c857a1bc6d8fa7e5
- transaction
- bc6aeef80fa723ed366628882eb184b1e90e01abaceab2f8331fe7365ead42c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68307
the chainentry 68307
- sealed to the entry before
- 8f1a5b71ddd6db9c07ae64dae01477bb5af190fe5b68f3ca434375bdda3eeecf
- this leaf
- 87f8699d2fe947f3aa25dd96e96646898fc2c2ae72479dfe72c72ea2fbcb1c09
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nPk7SANoR4NVsfqaKhlaPSKX2wJVcA3hxrX6cLq900CiacYlUiftFS03R5GEuYWvvIpQW9Goulu9AuwwTa9UDA==