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
- e2df3bc2b8c3bb8304c9258c829d1d80f6997d5e767403c8789bcad8d9e54980
- request
- 4e90fc301446d60f17d367a222161d599cb5978a31949bc0486cab4243a65bb9
- transaction
- a7e2827c7b87a46add4c11b33bde576822113bafa038e190c9e9650488ac6f09computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25082
the chainentry 25082
- sealed to the entry before
- d53e1943bb8078c30bc44e652b8f9a72c38ce6711c603c6a112f4f84a74fcd5d
- this leaf
- 6ab326373354200ce965ef0f6d52139e3a2af9f75f39cb82a82d5466f6617c7f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zmpxewwd7ihoA40veD9jGsAC9/r54iKgiLfZrlLzVv+PnbV2Lwv3yKYqGxZy20RhXDZDemNSHiHmaXKotr2mDw==