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
- 11999f300d7791929c495aa412567f68d50adb8fe5c361adceeb8bb1c08d2999
- request
- e8fe2cf970df8a402a965052c35c8408fb6df78b9956c4b8b321452e42d3226a
- transaction
- d11a56e1ef77386349f5acf2746f3cb05d55bc53d0331df4bdbbd9dfe0b25a28computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51384
the chainentry 51384
- sealed to the entry before
- 6ddd30eb126339eaab5f3559abaa57d0c4916fd28c38acd9a08b7d9faa0ebe5b
- this leaf
- 905206182972ee351c6b726d9384aee39e85fb982f8ede1746ef5eafa675956a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p/kYSIt4pl7X0SlxYAwp2bFD3k8QEjW/vKmlmvwXAH1b6ef4E2Op6KGjWTxRUvWP1RC4FJO7A3eqgvNbDIogCA==