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
- 5ac0ef738cde129c63256e8270bf0a1905d81022ac38e1f8081d97190064a3cb
- request
- 0d4c72b3d63cd7e40ba2cee592674c8bf76ee72e40e605fe744a8c0d2d19073d
- transaction
- b7a6b3209d008c850f467a802372881b43e8e7661cc6b80ee07289467a641030computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39256
the chainentry 39256
- sealed to the entry before
- cd5ad487c841713ba205d98b8e0aae19910b79670bcccaea63b71b6d9112c7e0
- this leaf
- 25147e9dce4ed2a9ba5b4c92ed5f8afaffb8b339ecd530dfbb2183d12a3af6c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UesOSxpTkFPgupmVgSltv19o6hZFb7/Og1YMtdqX+wDAdcSz1sQhhq11/5l5sbj/r6in9mXaZ7SxdXjzRRChDw==