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
- 4efbe08707dd1471def4e451bf3b831956e8b8cee151db1b3ebbc00a80ea8582
- request
- a3d24655c27bf410e1ced346012ce9acdbfebfacbbdd4fb45b71c942820674d0
- transaction
- 4f16bd35d60d187eabc949d35e8b7abc707efa29ebc70e0770a6320795845070computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47069
the chainentry 47069
- sealed to the entry before
- dd503b27e86ccb54316d39bba21997466adaaf51b55ee20786d8243e82b7ef3e
- this leaf
- 2444dbdc6fac0f29acbfa18df8294e52cc7e96fbfd796dbea70187398bd3f97b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0sEJIEnTqO8J9H2j2PlPieztExOJ0Mn6Y7PUwzxHcscVKzi2LUsO5KvMUUhXV3DqLr/YnSNNtHTvOqS+hbPMAA==