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
- db37c4bc461ba0158bb422f37cd4aef72b7f29e73b027e89a37eb11367668bff
- request
- 6423d1c4b0a55dcdbb9a90390a5190dd701e69db31791598a71202de8497bbd7
- transaction
- 2e6808be6024c09041a84592b004e84772abd9cf778d61143fb9f4c287e86b17computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14437
the chainentry 14437
- sealed to the entry before
- 7e2e16832b5cb048653449d97efe581a6352794e50ad9551d9ebeb943bcd1dc0
- this leaf
- b714b2129285727e0515dcac85c4f9110a36d3fa26f305595397dbd675025447
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v1mmZLE3g2Gs3ehSbJZFIpz+ekrSZQBhzXgvVIFCKVBOqLcBbEuvX1LsatMF26x+QrDdXzQzOOCMgHGVocPCDQ==