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
- d02e463292f69a3272d55454c28fce7247d89d685b8f5c36681dad4ba19ee418
- request
- d91ab4a83262dd082e203db54327b546c738acc09243f20f99182770fbb33e52
- transaction
- c77308d9bf6ba2d164ad3690339e95b7d109fec304f81521e01ddd72071b9fadcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15112
the chainentry 15112
- sealed to the entry before
- adb84b56aa39f2b7918d4249ddb7d72c58ea0da3d9603db9ebd06af3addc3c25
- this leaf
- 57f47d92a2263a10635330b290b1fc917de9d089be5b3038d3e644e27127e397
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0KT13D5Vu3xC5kuEnaTnsyGIulC6FUbYg7MhYhx4bXJXwxs4hF15Q0eGef3bRKwLqo/PEShlgAyDbSYbD78IBg==