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
- 203fbf21bf0740dc762efe8d1f9892d879e1205124731aacd629c666673f0862
- request
- db848427615af019e37f3203bb12e71a904ddd21a233b2fda405e837631996f4
- transaction
- a8d00c88e922c8e183f07d8e4ee779339e11ad065a19e141df885d75ef67fa61computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11655
the chainentry 11655
- sealed to the entry before
- 508fe07a32d320743cc7a8fc70a3c7cb4167e38fbd14ad3d3b3fe8f304761edb
- this leaf
- 4b2745c6dc0dff67ec725dcb238276b41c3997aa78753f72d153060da4bb5795
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QpthYU+iYuzgGwk3pEn2Un+lR9ele72JFO5uL2p6ExpNwJ67RYYTmiHB/093LklvH2UmX1omI2YBLs8W2+qiCw==