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
- 1826d9f1fe9fb886b96096e92563981489b34c56940a2112adfd94ed772d7eaf
- request
- 0d77a5cec04a71863d965280af41f5c080392ec00efe5110239d810b3363f01a
- transaction
- 49d90fdcbb27cc77566aa5551365429dae987efb5c86b692488bbdc246aadc57computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20575
the chainentry 20575
- sealed to the entry before
- 38735c1c6b67b2fb911ffd4667248d17633560addd34eb944026d0c5075c498c
- this leaf
- cdb0b74db1024a231be6ffd768e8561be98cb89e8f38c6a27cab6dccdb29065e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YuHYhiDiFU3yUAIT4S82Hz5C5cjRCGD3UAzvUMnuV759df/3FkfTYf8uTeBjx4UjeVWzPK2cdRox6ugvmEt+Dw==