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
- 709a85e18601f279e83ed43dce5be0a636de431b08b7804122e82f973d6e7868
- request
- 0bf1aceabacb44b3661fca3f984fd0139594541766c222f1c314a0d30b273dfd
- transaction
- a5791f073a4944cb688c65f3fe3987f76731c416584f466a2e101c82333e2c06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61914
the chainentry 61914
- sealed to the entry before
- 7791e5806a27b560259a137be8e4435ccd8fb97896d4051d83c0ae037e7cb2bc
- this leaf
- bc96a3f923b14b754d45d0301c7989386dbb6a3c74b110556c75e16535ad9000
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hjBB1ZdABwxlyP9jkWxK7J4tLWBQl6O0ozSP4+Du3PXlUOaYbEjOcuGgpblzYPX7I1nFfEoG+6uYtPXC1q6yAA==