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
- c3beaa2dc733ff02d1729415f10d87b6808ca11f18d3cea4c0805bd4eb012a75
- request
- 03811d1953b85e3c48a3ad6fbd63b5c24846193751678cffa2db8b2de1e42d26
- transaction
- 28a88deeebb6470dd970457444ef066b4275b85191901b238fb0961b9928117dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28649
the chainentry 28649
- sealed to the entry before
- 7eabe281dc97a6f2221b2296a3ac8d4d85f8c34a0450bbf6552b139367dffe81
- this leaf
- f3edcfb10f804719b20d5df858ed416e687a1b173394937e86125d2b26ca9e27
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 86jGgz+5TEOVS+pWWPnNs1nUMK87acyWNbBuN920nkKQ3FbmePacui9nPuj+poMz29e/x6eQPX3JdDyaxBHhAw==