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
- af9defaeaa01bdaa438db82ec6a02dd3c75a56710ac90bf563b83dd466fb0a97
- request
- 9822f643ef0dfc936ea775f5f94280761276388d395ec97fa9dcc76f03f7c319
- transaction
- c3365f4c82444a3fcf4450eedc594e7df1a013420286c5cd51593d49d91f0382computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68194
the chainentry 68194
- sealed to the entry before
- 0e96a1fe5bf3a42d1f7248f32839446adb18c4feb1a9a74cb83022663f7ee96f
- this leaf
- 8c8029d72c6e4133fbf4f40cb9551bed2811057f6607860afa974fa7fae270aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6cNFi+30typPbnbsS42LIPOO8o3r6ZdehTSrRQp4bEiHbIe0ee86w3MBmscXio5BhmTVBaSa5H1h2Wp2VjYYCA==