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
- 7ee24fe2172328ff2ed105def8d00aff384327aa68621293f19ec540d73e5199
- request
- 6f24c61bf98c6aacfea1ba4b868796b9eff96b4caa15f07e85685ca52d4da7cf
- transaction
- 3921380b8c553407571b3bffdaf5ac47746dbab4b9a889a050b221f9b0307c16computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59601
the chainentry 59601
- sealed to the entry before
- 6a5b021580b73d37472448996d131b02ddb269b71d89268d690ece79d99a09fb
- this leaf
- 7246761fc3fcaa1adb05ff38d593b6b1bc4155aa5e63fdf24412860fa69ae8de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yjDtslqQqEfGR7KEa9O/JminwxHeGckeJiTJnPansErBXiEEEH3r/1t5hbG5Fzu0MGcXBo9mk+LnmOz5viekDg==