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
- 53d1ddb470b3e95b1c3d3abbbdaa0ca947bf8dbf8b230324ffefbdc30a3ddce9
- request
- 958c3381e58fdb6c95be18f928af4249ecb4cdadd635c94b41255f1458314a6c
- transaction
- 8af45e77ae5c885db26294a87a5bf3e4be50afc17d4e1cce4a503cb9c4d5f15fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33925
the chainentry 33925
- sealed to the entry before
- cf1b9e41dadc93d5d0d6ec16b43af2a2090c610c47dc6b2c10ad72ee595e4c09
- this leaf
- d821cf0b8cba191f43c79b45b9b0a24ed51f37bc79eb88cd20c0020ac9a6656d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XGJoBp9JQ2Qmsrvkm46Wu/99f8Aev3PkRd58qAY9IqSLyNfQhfvDFYFZ28oVD72OBpbgkGVFkRtUORqhSm13DQ==