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
- 2689a1cda7ffc5db8dc7bfc7df462b07b77d8f33ff9a11d8c8f3bd05d2675df6
- request
- f7702585534d1f479deafd0ccdac8d93646dd4aca9229c7043ff9c5b49bef551
- transaction
- aaedf70c76c5a3991f88f7716953b745e32969769cb9f79dade03dff667ba0a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58010
the chainentry 58010
- sealed to the entry before
- f798f0e856978166d261ab80f4ef8866b8616f78c61d2dcac93b795527a246f8
- this leaf
- f14880435b7380776b35c4d316e3a99941b03a3a7568bf99955ec7a5b52df3ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GGQUIhGTPdvHrFkT5Rkpa4kinlFNFHjTjRFvlvSvPA1sncImp9hz928NIfoGe5uKbzcfa3BT+zsWq1ZmkoG8CQ==