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
- 76aa58ef2ed8263c172f90e742238bf8ad471671d6ad4b362c8e61c3f28c398e
- request
- 82ab8f9f2f1ac111c5ac03cbcb721305d3e365b7eccbfb8e2c3706a8f78895ea
- transaction
- 675cf1252773768bc8f277ca69a171e0e582a2218c93573e1b5b2a262b46efe4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18124
the chainentry 18124
- sealed to the entry before
- 895f0d66d5324037f7f7dca05762f50d9857dceb89d9e9f0ab0849e01ceee450
- this leaf
- f041133eae9c1cf71b8cfb4f04ce037d33ea802addad07e1d47ddecd871f7b6f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SNCFsGab6hmsr3qcbJkkG5DQImEQLd0Ttx4tzJjTj/wSbXdgeQmKFgwQcE5nSN4EAPK132tIKSh9bwodlyL8Bw==