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
- 659ffeec9431d75fc5d7876a1acc177543238f5f031ce850705a7f02fc698377
- request
- e095dc88e629b6a59d2b657068ff3987969b22203fe7c3812133bc80fd4d7fd3
- transaction
- f9bf1500a7bfeaa833e08bcfa17931dba7bf774ab8009c7a03d10dab25ee484ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41737
the chainentry 41737
- sealed to the entry before
- 82ba139f6ba2381e4eecc03173fdeb4e89ffb668376a61b307854b33b8b9d678
- this leaf
- dca6068acb2d27173ffabf083632e56fb95164a957a63da18c4c82fba16a7186
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GyxXGjEIsWZdZPWjvSVh5Qg1NIINk5I1z0lEcP1IlFVVEow/83SPxAx2MmrMBLT0mt+vhcxr/x/rp0JWdclbDA==