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
- 9abb18a375bde0cd32295339a5197faa0dd79b8a60a98e2732e4ca0d6a07ce49
- request
- 20dc9e8be2faaba69bdf932d70bba2b7266f40d07e43c1da514956f98ea5cc68
- transaction
- aa3debb3129d2fa7fa8cdeadfc90deca8e93827bfc65029397099e2a537b8db5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46950
the chainentry 46950
- sealed to the entry before
- 56d05602c2845dda704e69cb75c41d967d3ec82bcbe23415c5f04bf1363d145b
- this leaf
- d69eec3d7d490540aa3f2488322574f9e623ea6ee2cb599639f74ec3ebb76d43
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xfwSVT5qENfu7+JIcwLCEwDUSIs7oGPVKnrsFVOr+M9JV9IPJPGgkiPhmIL96km5UYVPTbCHlcnIj8Lzl23NBA==