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
- baccaad316f65674af658bab9609dd84e1c26f80388b2480a4eab997dca57e89
- request
- cc2291adf385008833174f5603dcc10a2e5ef2d54cbdd7b1ee7b8d798197f3b2
- transaction
- ca2711c9ec49f64130ac11bded78032895e16567deed86a7ed1377ec3e9da664computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66153
the chainentry 66153
- sealed to the entry before
- bbdafaf3e1b489bcf7ead5807e181bacc2b6099ac5c8d35c4cfa19bcee4f0637
- this leaf
- 6c91938acb31b5d95c50fef3049a5f8abd824dc2f36e13f7e7c8d2b736b46c42
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L4kGmhKJxeDnqUQcUw0oWmEiGN9oWZkiWOBZC025bmaULLb43FONXSz4RngnqdWXVoNadall5wPRrVxS6W8zDg==