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
- c6e1c8d94b6ede9ebf2c8077a194737145a968b0bad016709d21c26c86ac7d52
- request
- 74f2956445d748e6177ddfacd64181ddce92279b1208ba6cb88999f19a9a00e2
- transaction
- 11520fcd3255c59b67339da31e91f8c525ae2517a99b7dbced32a4b297665feccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38028
the chainentry 38028
- sealed to the entry before
- 6fc79f629eb2912c3bfc9ee7ee2a9dd248b837da9d40f84d0c58583c9e1b3839
- this leaf
- c022ec8ef4de0fe56739dcd508569e8a3e6f1ebe40027d161e28df243daa295d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CTQafLj/aQRQyuAg7rCQMuU0uEm6Nb725NYAzmvoUIKG+wLHkkxamV/Hb5RlRx43iPEAJtERiWOUkIKwLRNeAA==