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
- fe3749bbe3bd6ccdf581f40b5fb3812649b17f56ff92b2b7e5f79b9538841679
- request
- c4119244c1658316ab8a09e3310ca23c4f3719f4df54a2944de4eb88b3a033d5
- transaction
- b1a4200edbaee4c073d4684aa1e325209ffcc10a951540538b9f87aff3e09f94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42403
the chainentry 42403
- sealed to the entry before
- 946a4b57de61a806d086644483b3b8139bd11e5a40302447b5965402cca812af
- this leaf
- ec250737c1333e67fe5a5d5df24dd0837ece2f6ab7bdf2f62685c88ff05d7dfc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 53YBALXkRnHMtJM/6dM0sdF/NEyDnNO1brjQkXw6zIvWBjdj3gFVWCRvb7gIOHn8foGCIoUTgrFhCBdJGWPBCQ==