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
- e492a8fb816593a76746ebd30057ffb9a5a5df501bf67df3b484283c55988e05
- request
- 5dee5c2886e4f56b1e1112929c7b071202ea75e51bb296e3a9b79e301720b579
- transaction
- 17ae96426cd8ef9f249c8757f76187d2c63678185b8570b001c04fe57ababc98computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50170
the chainentry 50170
- sealed to the entry before
- 4c0b4a4eee0fc35d203b068d823a46b4370001ca424d25639e242cea88c751e6
- this leaf
- 7cc48f4268b7ad816c71004d6a752513fd084e3490218339b3f43e2378be6d0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WISZ7spznDfM7VMyqi8jWMpMIaRCdtHOjm2mhfiaMGMM0Bu00tNZ/HqP+LJeYiyn5Jx4D3Pl3pYRZ6CZiBEiAA==