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
- cb31f76caafc15d1934b19658aff6a7d9dafcdf9ea84ee66c414fc7359fcc4f6
- request
- 4627aa01437527947b75b9e5c59fd10de7d4e4e9fb51248125a58b8d409e2d3b
- transaction
- 652333c02c1fee99e8d3c128de69d9ed19f74b7d593dd8cf69eedd94c73bd968computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25551
the chainentry 25551
- sealed to the entry before
- b43ac1832344e16fc37c50896b0fdf700195f389738fc6d3c1d1344f48304a5c
- this leaf
- 346cb7071371ac28524c393367871e3af9d5839e7e9025c8d7f4d659cbb22e52
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h58ozw235IbGLBOEsvdyOsGH8mHCnBe7ZUyqnPEc6ZY5tQ43Y7Z3Ql93xuJ4GTTMgT/py2OL0tPksdkEy9XMDw==