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
- 2d147f8bfd332de7e4de9c199fe08090fc43181ddd0ad068052a6aec6e3a332e
- request
- 37e803c1040bf8d5a794612ae09e556577163f028f922175a6241f36b6065462
- transaction
- 0802c5c349bab3dbd5ba1b64d74ecbf2b0b71ccbb8ac3ef2363e514267c04ae7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56334
the chainentry 56334
- sealed to the entry before
- 027e94b0fd77f472c27ea9d203dfc816d2502bf3aad08604ac1c0396e8df49ff
- this leaf
- 8b0100becdea2757fbb277a1e31223995c17fbd7951699c6a492c8ff24fd557d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jll3woAiH3EAhhOX/QRoWMmzszZ/zjOOfBN8h0NZehED4MiIBHXcoCeyTZhwt81ZRdwsQSErYJu7nydRlwuSAA==