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
- cc132ec49f246b7ffdc80bb6914bfa6cfa08120d5769be6b13ae72a5a70a1846
- request
- 75c2c3a73745d894236a98dc0942f6f64923eaa1024af90b7b378f1591e409b2
- transaction
- a767d7049d26baabf7403784346d61ce712ff69b6681cf36b0f8483dc658d09bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63571
the chainentry 63571
- sealed to the entry before
- c096b41f5d38f0ed5a0f944c1d834115fd95fe185309d25148bc49ad6edfd950
- this leaf
- a97743c674a1c5615ac03a2d6cdbd61555b08f10b7178a46bd9bf165c941982a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dDllPSI5zW1ZwBL2s+3B3w5/KqX3Z98adxDucSRA76lowHs9EnvrJ8YtCkkjftydjz1+VkXcdJWw2cGRklevBA==