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
- 59d362bec8a807a3b232c4d73a43080ed8064690c7686da00cd3563340be4570
- request
- f7adb3a575a15e21f2fa18a18dec69f172e749850eab60079a99f330ed98e5d0
- transaction
- 5cd1de52b450d9f6b63d91c5de3845abe7be39edb52efce2c7ed0adaeac48718computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44005
the chainentry 44005
- sealed to the entry before
- 017be4c31f5df0b47d2f096614e37a6af770999086dacf5244c588fbf3b028a6
- this leaf
- e26bfd8d0bf4528dd03884745a05a002daed29a7ecada9e45def9cc8c909847e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- td9E3MGhLkVWbwXkglP4H8rStiVZ8MwdBp+IF7iYY+Hm7JgDtap4qC3vyEmYIviN+mM1tu0yZ8rQMGhdFYGPBQ==