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
- a0931409aaa8f66365441d0463c34b2ce5daa151985e1df07c4dc635340932c6
- request
- 9320c128300362ad83a09c3f02c45bbeecc39ed4f628e620d686dd1cf66a56db
- transaction
- 86d07b9978bbe103f78e53bb50249f206099e06864c417c499d60ae676ce126acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61003
the chainentry 61003
- sealed to the entry before
- b992cbaca9f4e8f72fa002f358f9271bbc3754d770cbdcc7ce2db9c639a0219b
- this leaf
- 9035ed6dbfcd6aefdedc0334f2a15198bd7a4001c929944f4a0203c682fd8fa5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aaoimGrZfbR6xHev8nTChT6CgHpuXWxZzOBvFGjhWT4+sRkB1ncBUujvkBAZieXggnIwJCOb6cV3C3kXNxsnDQ==