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
- b447694dfa04f51ebe3abfe666e05e2e0141beeca58fb6ec1a2e294f15631954
- request
- a47882aef0e964d3e7743a93c1a1078e8bd6250328dd00df0fcdec4bab89bb3b
- transaction
- 751bc10226f711a0489982e76a8e8f962827ae04eed64969c33ad19d4c894a3ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12299
the chainentry 12299
- sealed to the entry before
- 64c6ef38230b0ab482453cf8e7bcdb6bae04fc7159f9ccbafcb6f831b1645e15
- this leaf
- 5fa3dce38bf746ace5f64bb44bd7e002e815bcba5e303ca5cf27edc3b0728004
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lLQI9U1wtIF74bM92dBdy7dSFLNL7bvJijHW2x7IAdkUrhSOg2YeIj8Ha/pIXD52GVOVIevy3Ic91E5VPyepCQ==