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
- 33c914994981e2b55fbf5f5bc175327621dcec64a37884e0ba7af4a77476ad1d
- request
- 821e02da3ea69ef96eb34f70f4d9b6c33e3d8b1fd0b349cff4d70bbd05026ad2
- transaction
- 6dde869a74e084c8f985c602be686b40d8b7b0231244c00197300a853eaa6445computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44127
the chainentry 44127
- sealed to the entry before
- 7e1cdc7f886439e058dad3bb7e86bb6755e51b3f0c8bd353c33a36d68c944050
- this leaf
- f53ba68929e8a0ab259ba89eef4ce7486d8c469619f317208863ec54b0c18b56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3+xCy52Y5YVfvaORO5gKxn9wNJkctAwI/YNic5/so0ZDJK8ii4LkdeqI1xgCz5jMDsi+/8FEuwokHqBZZGDABA==