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
- f2d9c10a50a7ef4d6ffca8dfb4fda29d9ecac10a5e4f2484d4f512cc0aea35c7
- request
- 2b19acb2e7fd1e6467a8b845eee69a817857756fd891e36f6c42fb2e349455f2
- transaction
- 5fdd283808076dd3fb954326482c6db6c11a4177eb3f913fe5a1d9998ccbfb8fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2490
the chainentry 2490
- sealed to the entry before
- c550da98c4834661c92c7ccc2bc3efd9103ea142c92e97d1887d5383aee16fbf
- this leaf
- cf7d012f1f0d39c50c0974e52ebb0545e21d90a0594dd926e178e62bd0bb6ab6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V7VNGrFzt7QUwd9l0KFj4cRvyTHH9MPSX3FgBxoO7LCf0/XRgDxuezyLMFYaUA492LVohwiAZ9eqRhyjq6puDg==