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
- a26773419380ac201c6a35ef41e7b2a1e9616bbbb8787de7c62276d0d260fb21
- request
- b67bf16e83c1236765ec08c589b7d9e710b3a6f38f2c2545abed7f9fba990481
- transaction
- 9755c3f049da9352610572ac186c52854a30c8ac51ee56dbc2f23287fb4c3637computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68048
the chainentry 68048
- sealed to the entry before
- 79aae26c9dd9daefb0631f279f9b2197c7e8a5f74b409d944f6079f8467597b0
- this leaf
- 3745781cd83f60da9dd11cac1412401be56b0b529390d6a42a14a96dc23aa248
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SFoGocQplzjtDXPwf20AhYKPDaOf9jDc9d4JHI7XrdKOR/1P8yA2GVi0fvgB7oUI/2hw+OuLoGoBgsvTAdlhDg==