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
- a5fc71d49fe66442f960957fcf5ba7b7e1143d142eede4aae792350c75b2aa43
- request
- ef0695b4d5bc29d858a3fe297294c84b611fb11c96a265c0d446da5ee43d6962
- transaction
- 32f20e9f82bf252c43bf0f8359810014445b17f1c175403b4046105f7e414460computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15952
the chainentry 15952
- sealed to the entry before
- d1fa33f95b858528fddd3bc05438f533fc6ce3d03e6e6ec7314b1602ed84d7e0
- this leaf
- d250fa3af7b54d9e77130d07d9c52f614aa2fcd2bb263b4c38d9254e0889a406
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /3QHuMNCmaw+kKLEqoqhPsio+87C4s5sguwhJlAPY5Xgso3z7JHTjLU6L02xPOFoLx5xALlnOjuQZXT/GI4dCQ==