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
- fe60888b0dda4199849b1ddd96731d0407151064489d8ad9fe7452a6e3dcfa53
- request
- b0397b328082ec6adba45ed2ad4185f2d972571e71bc9170df67654f1dd09e69
- transaction
- 6954ac98ffc4b6127879e807a991bd7244d11c3c01870ecaf038e6ae423470a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3285
the chainentry 3285
- sealed to the entry before
- 70581aa6dc93da3ddb64cac6cf02352214f4843b98ec2cdd70b15bb4f315b430
- this leaf
- 3053c734332d1f22bbc6c0c6b603d7c2e8075804e1497de703050c5468fefec6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y/E7KZv5MqEX34WiuGkafebrkweGWaCahGaBGKVhbPzTTQ0sjO4Bj1umEq26m7VJMGepLLuOO/FlVO4xyHg7CA==