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
- 349f091bb8379b2ccee83f2fc63a58dcea10e913b453c82e7125d78eb83bb291
- request
- f5f5bed561a5b531de61ad77cbed4761cf5b1179836db7134c0c3102fa769a1f
- transaction
- 5b4243cfce0c3f4e3bd9b9d9a91a07229bb5a485bffc7461f19c8d52b1f7161fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57049
the chainentry 57049
- sealed to the entry before
- e01bc90fb2223a4a87e4ba6f45f4a87265a7d01833367a4314bd264b34807874
- this leaf
- a65639e2b8a47e63ae3ccb96901c1b37857590ace2b11b61b3abed6c3a5866c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L9YEBZkXCya+SawfIuT57ckxpzchuuGA++YKiOpdMgTaR1VaQLJYHTK1NKwC1QVxeN4Gk/hW/wK0K4PncGUQDQ==