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
- a75955e7d4b3b5676c6617342a98ab3657958f254762bc1ed122591570608959
- request
- e81b3a4ec1de3f0fe4f00d800ab825325dac301a6c4646080f3ae3d328bbb199
- transaction
- 9676e453e06dc656d188c2231afdbeb5cb5425bd3b5abc80d01f8d1fd70a2452computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23327
the chainentry 23327
- sealed to the entry before
- a11f480af9df5874ff15078ee5bab4479022ca8eeead09e0b5fd9a3bbb6b719d
- this leaf
- b5146a89e3c8da2e9a0895c1dabadf1b418767b55ab6afe80923f786c1e5f54f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5/JWEZoq7WGAXEZEzr3DPL2/B8OdbQQGVTKNDX2wnsR5+oD3/N7Jt9THhtDT/iW1tlFAshYQlZvYzJTFuqkWCA==