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
- f765911f0757498ac9557df1e8086f64f97ab97574ce5d9acdc741fe0f5d6235
- request
- 6f210310d2a4775c313c1aa633ca3c2dd5613cee7cc7373b74adea701b31c1ed
- transaction
- cf8ad4e7482ac1f68ac2a88111b7c116e241293ec167a5d55f2f6cc62c402437computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51438
the chainentry 51438
- sealed to the entry before
- 775e65daf83dd276beec8cb2a485d506f9addd873f152fa4be05f95a55ae42cf
- this leaf
- cc3995f259231d6091d6ed7dbb23c451713844b60803a34c64d3de41bedf225a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D29TmNHEjvKALIGfMxe36stepjXmdoeqjEf8PlTzZODT3aGA55RCi0vJMKhnED/HtQ+SlcIuwJcgF/ktUgkMAw==