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
- 86e98e1f6200470468aed4582f6c9cb6adca21b8ec28d99891f36a365d9d4f0b
- request
- 10ed57acbf8a645bcf72b641611acd8af950ff599c0a1d4da73c26808e41c5fe
- transaction
- 93abf381a98542fd15cb626614a51d9c12cbde879c05f49b4161b9cdc8110046computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67519
the chainentry 67519
- sealed to the entry before
- a8f13a3dd951f37e1618ae32cd73f4753eeddf8fb69335c52671d5e5d3564331
- this leaf
- 7da199c77e7d60b5e5a7510f47f17f633d195942afc445d41326409049c4ea94
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KrQA8Vhc6LWaffwLguStg/U3kyPRPZs/uv5MfLHVhIB1NTXb4OgQXamuXftTNK0OCXc9HlJ25p0x6Rew12DTAQ==