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
- ed9b2115ed885eb87c12ffde4d74950ca736cd7350ed57a9444b583b5a8d9a3c
- request
- 0aba52f62ffa081d9d21cff1f160ecc18d15139e5c367093c503288a133e381f
- transaction
- fff61db8fb3ec9b014e50f6eb6bf331a20895069e4239095faa32f25600f20e6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21801
the chainentry 21801
- sealed to the entry before
- da63c35491540f56b9c35d3dac6748326bb1df4dc47c75c7fb37bd70fa032137
- this leaf
- 4863bea7fc61b86e15eef3622ee54b6b7089021e6629941e5b7208c194e39e32
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gOWifeBG3rhEm5rlKfpLHKV2AFT9FDyOpYmb7VCTvjcUl5ARn5ouPklYVLnNWsB9/72bqoclsmQEemkbJknOCg==