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
- 9c55edbfcd3a62a9f281b6434a235a0bb4c0fae710454cc2f38326e8e346b32c
- request
- e5728734783a011a1bf69e6e3139dc3affb08754995a17b64858b19653677895
- transaction
- 6a6d5e1dbd6aadc5d07f9593d44929219ec04850e288e65e7bac5c541fadb37dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52936
the chainentry 52936
- sealed to the entry before
- 3acbea7b2c9e6b191916a4bd6670842e2125105d8287e0d44f0853ec2ca41070
- this leaf
- 3295262344701a356a4ea5baa7f0579875272f8dd1ab451e41eec7c2bc81fbad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mhfZx03JlFjFj1ecNT5LfX52sVSFxOGjiF4iK8mM0xGGqZvdhcCUWxR7WqO3Q5SfXgtUbqJ8wFq0BibNmYZZAg==