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
- daf1477ca0e568e25fab209e8c97697e1dd451484e3c1456136572f9a93fee49
- request
- 4c4d8144d5f44c3ca1c8572894bee596729080c9a189ed7f4b57a04a9a09be1e
- transaction
- 296e583dd540beb6298a1e90f711a4344874a54417978c09ca08bf79283ea9f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63225
the chainentry 63225
- sealed to the entry before
- e14382f8a81bdaf97a5b0c1c1927ecd72259e630230f8b58528ef40a8cf8786b
- this leaf
- 8f20319b3a028b2046bf6bb5d5c9f2a90bbe85c23ec9b6ad3f73b734575ddf3d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tRYEpdVDjM2gmm7nRAghghPnQXavOk8XXxV1sm2nC2zy0RLqgVlgER7LDiuGbCN6X6/y1yPrOUZh2kXaeeo/Bw==