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
- e968b5b0fccf2b463eac6929c73fb488833668e7993d170138c6c6bb9f8d8b98
- request
- 4a58cac256cf2a5b7ee59503a75de47aaef3a945cde04ef6ad3261f2fffb4927
- transaction
- 52a5be36a21c45dca0290969627b60aae4c7ef5410145a099fc4cb8ef4f1235acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1560
the chainentry 1560
- sealed to the entry before
- ee4d636f947f267ac73c9d4b104c53431b3586f3c56ffbae391f482aeece56ea
- this leaf
- a01623e4a55a6110157ccc50e49dc71a29e9c5ead73abbe2efeebc9d6b2455c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x3GiGAwjvLh6QzS8EMFbPnocIu5Q+qvGfCE77Rwkg200v4eVZPMw9V5/oCpwwgEkUCrc/BPbU6DlvC5LUQ2CAQ==