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
- 56ad4e5090c874a3ca49e5a01ad34436ae377193c3848f74bdd4932a4bffae61
- request
- 2b029f084a9e7eeacd41333a32ffa598688cce423d365a7092ee7434733b853a
- transaction
- 2f594b105da1333a5f5e90c6417dfb5172e95bfbaa6f15af07648f63d21a28e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76290
the chainentry 76290
- sealed to the entry before
- 96d5cf1c8fefc734d2fb6886ca7242dd0abaeaa48d3fa30ca5584fa979494295
- this leaf
- 464e4ceac2c03f3ec34c1206002cc0caceafda63695c39a79980e8e11d2f9b51
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zAYEkbnLzpdB8Au6xf0K1oW6Nsr6mB6rY2wsJ9OJCOIsic4L2D60cyPqDV9AzZDzTl2yBKPpkqBhBQMw4g1KBA==