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
- fe0b59d19e54cdff9492181fe600d9c4822deaf75b7622f701680362edc79962
- request
- d7f3298bea6ffbb29a7bc551a697ff86db0db314fb09ce6810c53a0da32cd997
- transaction
- 11986abaf75f413f7ee98bfe498e8d9eae4b45279cc2df02a77ea205c3af6d8acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46004
the chainentry 46004
- sealed to the entry before
- 55544da67c8d297b64070248a2b521e7389061a0fc3ee22d7828afc028d1ebd5
- this leaf
- 19282b933667605d831c77a4b9b371d95263db55dd5111029b156f64d6385ede
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O6XohaV/hIeecrggo2grmUEW0hsmuTssRJ4UuqmUoWWlw5kKyeb87//6fYyh18Kl34z/qIZNok9lx96LbeP/Bw==