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
- 3799c4431d82308d73f26b09fc0d419a9c60ced5f4171c05cecce9f1e72356b7
- request
- 42a41768a4823996cb79c7bad2bda1bd7e6cc3dadb301feaa96ecc6ec0cec0dd
- transaction
- d68bf441442520d051ee5c130bb9f5fe4bfc7b1a9f350496d6b4596baf496741computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16405
the chainentry 16405
- sealed to the entry before
- 2d85d2e1237b8e27541642eda3633ee4189c0f637f589aeee84494f499060f64
- this leaf
- d0ea4c245528edb203fad398d2d9770e7640f410ef378fd6d970c53643621acb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SIXBA3qW02uDJVGoWxUEWKFm3w5jGULFChtiukFoYpeAzvO5djK3Pm2610/b+9wIveAMtV0SXp4mzf8IDk2uDA==