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
- 3f503c06bd115f223ba3cf39389c406e7206d4ec6d1b23e3ddb1aa7335e87f3d
- request
- 443d5f0bddef6c533c19458b011f0b4a2c0decd8efa012bf00758bf9f8354606
- transaction
- 27cc6cf57cb62751f9ba621ff5502eebcad64213e6014e56e90636438f5a972ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22184
the chainentry 22184
- sealed to the entry before
- c7cddab58ef795029f690395e7542707f805537d63d2a44f6f5b19506f330a53
- this leaf
- 7d1609d9222af9ee30aab163b59b0a35fb9c458e775fae82a229fec0a9b5696c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BdixRTWMJ4uk/OiausPVT78ikAj37hXqI1lWMSX21FWG4ucA3XxiXqSvStEj2URkB2lxIp3lFoSz1gASSuG5Dw==