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
- fe4fc29d862cb3573bdb46d552c27fc18b53af98b8d4dc91935560f3f826c776
- request
- 4b94ab788ca26e9274c6a0fd0f6c86485ee98062b1ed655eda90fd76a85c7868
- transaction
- e84c09c21b55e32bffd47eff87d118de0dda3580b92025cb9e07d09d23deb885computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8913
the chainentry 8913
- sealed to the entry before
- b01f33dce5639f77d84158e937e4fd27a03dae592b1d2cf15dacb342fd81f38f
- this leaf
- 95a861d1ea4fa5a917691d240d6cec6f8140409b4db92746b2bf9035920d1d83
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1BxQwBx4iVnA2yMUgDR3yFzfnRa3/VuPErM5xr0Xf+sae2zmofaU6zkjJw/+nIyHfn3DXVY9wmgysYVTx4FrAg==