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
- 0923b71ee1c360cd79b0ec97a4cdb014f9e92e978670eb300d83682b3b54d561
- request
- 20fd13042292f05e59f8f455e03cd24b1d6e4fdb5b56bf6cda26497854744f0d
- transaction
- 7eb8f56ca0fab7e8a1910f8db9c2b83817e236384860047df00ebef7886f35becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2060
the chainentry 2060
- sealed to the entry before
- 39f439794e404911eaa3746801756f01e001c29c74af6cda36594015e13bb5cf
- this leaf
- 2abf098ab2a196ddfabb596b29825c14c46c8c52124de8196682e9e0dac18b3d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jhzAEDGVknYF4yzGxJowQ5bjYCcuWmVPShRQuSfnZsEk8FZoec5v2uGHyLzYW2cN6FofIH094WkmX/o7fYYHDw==