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
- f0fe5ff78c7d304197fa20f0fd42d22e2cb26b576ce632aa01b50e2bc5d08290
- request
- 49ac5fbbd315bafc3399e678fa20e73d504c51a178a16b1cf0b18fa140eb8b55
- transaction
- 31f2bf9e6e3d14a34de4706c8e76718876b95df9b199222da76bcab6a3ccf459computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69433
the chainentry 69433
- sealed to the entry before
- eb9e61877f9405db6823b8690d31f61ad806d8794e393c7e744632fc3f31e21a
- this leaf
- 16082cb6af601633f8ad622584f83e95f9e448bfd6f34b4f62ff3af503682e88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wYgoRz6XX4dMfgLydyXz4N3suqxANsu4L8kMtWWoCHtj3f6jRl7BKLosTsERXxGklQl8l4Tcb5Ipw3z+UerQBQ==