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
- 765a769cba6fb548c1f23b528957dbcce64926a17b457af1432139a39629af2c
- request
- fe3af43a85e93dcea1e7b8afe892c32997afd456fa7e37de63be14d8eb5f131c
- transaction
- 19b6f0e7b448f331478d04e18e3746e5493b9fddeefdece5599371ef735c937fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40358
the chainentry 40358
- sealed to the entry before
- 5de7da20c253459e9004e45bb16f039b4d6006ef7a7a5f7e3ee90d284da8b0bb
- this leaf
- f1effb2e4975f3f6a47ab2b418b49450d7d1e16576015a0cae36295256c944f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R5Gh0NE5eKphXUuAoFzu1hPez8iTYod4eTK5AyazHjacgPhKcdiCpNX3PV2PUalNfVWRLSAHcDhCeDaorN1LBA==