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
- 9d36e55025331d5044a2bb3cf8fed1a75d8e2822db1fd5a2603b8557a27be503
- request
- 3f60d448a372212f49a286a6e109770f591408cc1e0ad49784047ce196fac308
- transaction
- 2eb59cd1830717718e01e6159cf0d4d89b65263c9fc6f46a7570a06b7e40cab1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29417
the chainentry 29417
- sealed to the entry before
- 939feadf26cf380046a3b703503fde1cb83663df033243507872bdb34f2faf8d
- this leaf
- e28ac1f19196b317c1e9f8b5724ed59fac161ce641fb530a74729648fd96c018
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xjvkNQd6vLE5ZQYara87z60GmKgO/f8F4S/1TCh4/1Vsp8EwOF8MRK8ME9CB2bT2KXYS2QFu6k6P7DppMWgQDg==