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
- e28b4d041bf0a7c48d148093c5ec13d1e1add7dee857907f08e9f60afd9c6531
- request
- 538fd6b15d098e8b05b559f7beff9b4bbfdcd0f944705c1b916de6f19f36b88d
- transaction
- 92b7856fcee1959a92c59d10b7dfde76bf6efed3e0143579152e0be31e77f753computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40724
the chainentry 40724
- sealed to the entry before
- 7079cab0305882e79ed741709b37f51f6cb8efd2c3275398b7546070e64f4344
- this leaf
- db5b572e15474eda2826cd009f83503eb3b421b3a0f3606ef8af4ff4fe593ac7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5DMOFJ9UB78YC8ifuDIOLv+wg7vRyjjDPoUXLu/PMDbp63f2wQdOyIlMD3tdZOfaQpimTj0OXdsX/4eyOuKoCg==