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
- 22b0faabac1dedbbc6add71805e3de8394c240491736b9edd8643fbbaa094040
- request
- e6754f52518e1c8f49c0772e8fa80093883be5354438959b8472328d3ac99893
- transaction
- 5e5f996d3184ef7d0599ed0711f2950d85003a7dacb4e6a8566f86b486d298a8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3536
the chainentry 3536
- sealed to the entry before
- 34e540853edfb84ae3913adb00e67621865bcc9113fef926422b75b0cbb47a85
- this leaf
- eff63a6f8ac279bf00fe1f149475609125362435670d5fa76d8a099bcaa0441d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4ASa/Oaufpr2sjo5K3aUzZNlEJo2v/P30ZSUF1FwUFpV8bmdTTXuiQLlBfio83IYWZadn4kHgJvzN8X6C7gMCQ==