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
- 6ce52080165453cc156ebe17fb5bb9c1e7a1125b3e1f212c592783bca4abb1e3
- request
- 0fd80dd2778a86e5809098a4d5393102f5324ed6b4e9721ff26ba97a76991ab3
- transaction
- c0583ce7c71ec02e65de053abde26a235cc6f9923cfea3d4a758229c76dbdfe5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44910
the chainentry 44910
- sealed to the entry before
- e4c084e88df57becdaf11e498fd4f3823b7e15a9f70a117371de2a74ca4b6c92
- this leaf
- 9c028da4ee045c0088620f6711b9e3a6ad83c775a008ae1ecd26e09127ff4d60
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B3ePaOwQpdhrTwcH3UJCtF68FDxZJLyiZUxk3pHl0NWB4veAkcd2lSRLGHX+Jc2Ccos7f/PiouU7TwZzbvbDAg==