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
- ce9cfdd3748ef9ff9e93415ee7d0869ec0414ecf5180096e7e951905bb5b4c94
- request
- 32163745f6d91e3796300fa3d8ec9fce04c8a2b88dba1bcdf0ae115701cb0721
- transaction
- 09ed18cc466406bb331efe68d42b853ab78f251dd71c6bef01a25c92405df19fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59018
the chainentry 59018
- sealed to the entry before
- 0f1dc5ae67adb895d564379e33d81c2887f3fd7e12d001cfef7ae5e96574a074
- this leaf
- 22583bc2780d5412524a4dec7c685492ff7aaf4671528b30fc60ac96ac44d81c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iAJWbeXz7ly8XuM+/AC+QtMaE7qFm1zVxmizPPcjDrfyK6RR8SommI6lcv4ehgGIpbLebeCrMEfHyFa2lDCpCg==