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
- de485fb2e7647a0e6b8431e8a3fe1f3c041ae2c6591f0104345ca2ea41c80423
- request
- 3f205cae39ea82d9e2afdf810ab51aaec399c8ccc7376c050ef5fe5d277edf8f
- transaction
- 2d54041377c0a4f6c3013dc6aaf0efa118f4ddecf8a8ca7477dabec3af045406computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54560
the chainentry 54560
- sealed to the entry before
- 499055a0b1a21df0742665ad258cd91ff619fe3c1caddc4d5c958301d45a2c16
- this leaf
- 508f6bf00b7bc412ded1c85445fbad7ee2ec2b06b1d5de86d3e1efdcafc584db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jHIqkoQO78PD0TywNnbKfOESZMF0wCuYXDhNI38iSWOjmkAI70dAkIFkrjjqxBmvqx9ZHrVvTyh22XQQKeXZCg==