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
- d33b1179d01ec1647025a393459b67504c251df5ee82a81db3d8460298a8215c
- request
- 828ead565032d12297b90398899f3d674d5260b805c7e7458951b0c4bceadc74
- transaction
- 3a502f8891f0f815a4b9d9ffce2c371ed236395715487c28515a078a49ba020bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43022
the chainentry 43022
- sealed to the entry before
- 445c37176ef67dd4abc113bad662acf82906d7bfcf4824571550a969d8d3608a
- this leaf
- 164ce1e24bf7aeb6a0bb6d49d6536b0f860e124329cdbd884141921c3817a09f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NGOVtzcGyEzi20ZXdC1HptAAL4DgS1MoIHQaAvkdEDudsbUw+rmRayfFATJWbK54waOUaBTRK6+bpEDAbwqaCg==