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
- 1fe5c52354a078c23d162d6bf61cb7e48cab37349b13902b67f63397a3cbc61f
- request
- fa838974900216e781d9bc8514e020235405453d271657918d981ac5177683dd
- transaction
- 879e0f3d8ba68e13e5f96c9827a17a8582304881add84bbeffa6610a7fc0d769computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33164
the chainentry 33164
- sealed to the entry before
- 649cce505593a5864ad5588cbe68a3a221096b949c9f6709422f8da2b4885df8
- this leaf
- 072dec1bd26706bb817b7d3cb26aa9b3f9a1a0c0a9dd80810b4415362d2d5c71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D+xKByMHOwg034TAR2IpitkjDzKJ0U188YMu58vrAlIqWjUXMNuZYYZGAT6Kas5kOCFptxGjbkUhMAzh6wkzCQ==