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
- 923f1afb0cf884c1ff2fe9e92cf7e16a4d93a02d45f58d40b92acfb4fa0a708b
- request
- 98dece8947dea1b013704cecf4fc94193f5aa1a9601f27ebcad37a1f6025beee
- transaction
- 04878439adecaf761038c32128ffa17ae73ea6475734019d6c7f7e30600f089fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72179
the chainentry 72179
- sealed to the entry before
- 971e1bbfb671e5b9d87cb0213000de4dfc69d6d3e010a4363298a6150220fd90
- this leaf
- 9c48e4b2cf45d9b5a77bc9dda289e5b6c270ad82783d26e55774f7854c0bf8c2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7YY1KQzxyOOI/vAcH+4jwzmulhwl5UGxym+UZOJj4prHamUZaXTMUJcUmJRXxddJw1AuXSbepuzc/NvVkHyuCg==