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
- f36951e8f397d0fae67cda1020b56a7b7c27a3d351c14acc3f2b1bbfb07cb91f
- request
- a98a41c5701199ff29883c7fa155f99e05ee537ec276c8be1c1f8763fedb2e9b
- transaction
- cc5bcab561e435f61ac94dd391d484a371243e85dfff21c23d87b55eab50d9bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68850
the chainentry 68850
- sealed to the entry before
- 41abd167af92ab55aaec71c895ecdd9fc50177ef01e1746ca4806529e93b4660
- this leaf
- d02f29b25552460caf3745e0c16306b8bffa783903920d3e59eee2b673047329
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ly/VP9o0vzAYca9NILO11nPwELOh+M/eQvJnIDTnF5HXeJmC92Z9JHau8+4Kp5DP7dujNkhtHdcLGkoet+zwAg==