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
- 50fd85755fb98bec5d5749b106cefc8d6e4081b605499d2eb39cb8c3b8c373f6
- request
- 40f60cabe6fca6ac00227a58a943a6a31d8350011f24b6c1a940ed48341f455f
- transaction
- ecf378acd8fd5f1fc182fb7a1c9d5d6a15848cd6f69eb3869074f1ea0c134873computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24442
the chainentry 24442
- sealed to the entry before
- b9a5cf21505a718c5f3f517398ccffe0321c9a31e76000515fb0662f4a1ace5d
- this leaf
- 2cddb778dd144fc48718a371fc3fd470d03211bc9c0e0303d6fb57748d5287bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BdxS2WwCCjtGvwTx7v9CKC7qupFHwfj859hN7O6LuVh2NOusIjuu0eChl30XH70wql2j1s2IIIXtuJxDTo2RBg==