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
- a2d17a970821daf20e0abb7635693c9572826f07b343aab1be3b538c2f66cef7
- request
- 3b7e04cec44f0e29a7f61612b605e409c5035f06fd642e99a2847da3395c8243
- transaction
- 14115c87c241c85db3a6e275fd96336f3a16974e125299115350516d5170a57ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28752
the chainentry 28752
- sealed to the entry before
- 95661f1c09a2d19116c5a745b724aecb51babab85f0c5a6e51729908c68398dc
- this leaf
- 4a2851f548c684df3c03ea967dea7c97787ff3c20a9e7f458d19f2e341cbfa1c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 03x453A9RtcqNrHn9nzYZXjDKAplWYs4cDRmjeQsTG77ktdk/rQT6OdwWae0FY+5mCMdiZt4hnYd97HQ4+p5CA==