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
- 1696f126f43a14115adc0bfc2f1f0bb62a1e39e67d412d3895290701d0898b71
- request
- 3fb271a9668c77992bd2b5dbfd55e5125d81adceafde86072130da19c74cbae3
- transaction
- e60940af279d19695a3d00f41291ffbb6d8ae8b6871493b4c9c304b35b6c1dc3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49379
the chainentry 49379
- sealed to the entry before
- c2df2b0dff9cc7e46a37eb86e78c1aca802784f5f350890ddef1698e63116be6
- this leaf
- ccd93e82f418a7ec1b9fea515407ba46a751b7ec96d0eac885ddc39bc168f5a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ag5HDj+vkNbKVYgon0Yq3+/LFLFYUCfgrXuPMGB+Pz7VRmJdNsuBYrEVxY+RzIeeZfxgXiw+0bdnXlCjNFIYCA==