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
- 4cb0ae4405bbbbedd0a8b46e972ab8d316ca76733f529b1b99628695362fe878
- request
- 351c31e370de27135310aca736221491f62277f0ee2356b5458bc63f4c2f44ef
- transaction
- 31c95c37f922a233a384136e9d9d56cbd1efc035c60b3d5d29c182eaf934b532computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30240
the chainentry 30240
- sealed to the entry before
- e0ad20702b6cae532c1c5551729e4bb6d14b0aeb4ae05e7e832821da98f738d3
- this leaf
- bfccf8a391e2077941023f6039fff0f56d3a5994f9693b69c92c0a2865ff0a04
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tlrts+S7HX/a+FjWx6Y3nNscTU517E7WFyp6OC6yrryKvKD8sbxf5xEKtMXz0RO/bkLho9KsEbO0g9iJ/NHnBg==