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
- eeb5a4f7c0de23fc712c7b4a1386a5a021e8465a46ad638f5fcd7379e3dc4fa6
- request
- 72eeda50d58bf14809eae705da10d3b36522554a05d6415502ef675112e1389a
- transaction
- a7c7e2571c59f8ed1d0e8c4d18f3ba586babf340431802af8a2c43c27ecafcd1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9414
the chainentry 9414
- sealed to the entry before
- 91b3caa4c298a3769cd81787c0c4a40bdf7e4992d7669d68c2aeafccb1f1ae02
- this leaf
- 7cf095ecaf4def96c45a0d2b18d96e753cc83c8f6300a92ea46a0a6ba9dc14ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z3J++Zt60jLchffcaK6W88aCqLTUMZvQ0Noaf4fwwwvc3aT2xrZSASVog0AndYvG8gudXzga5aoVsEoB8dHxDw==