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
- 3e542ec5fc6f9f358028933f4ad1894d00ecf5c9202e6cb0da688aa02f0f1fc2
- request
- 551ad75dee9ff461fb98105366c5fb3315480b9ee1113d15585571291faace12
- transaction
- 70a4968d05ebbc65f5f30bdf929df754fa0955fa6a4ac8ac2a0e980df794271ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76748
the chainentry 76748
- sealed to the entry before
- 32d762cbf4dd1129593b96de67777c73e6046b87799dd400898459ee8a6eebda
- this leaf
- b04fd76c62247b4b2469c84722c83111049ddfc5f9e61c0adeab50d77854e81a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KV3gm5HvOrEqg8Bg97O6AbW2S7xqd1KLKuSnSnFmD7SqM6ZGN4LAx7y6dw3VNbyhT3SKhiFo1T17rxLP5ZR+AQ==