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
- aad71bdc5685d6e747dff267b2160b81d0b041b90880be8f21584f9e1373d416
- request
- a80aabb6bbbdb6474f05120bca66ddf4b753b7224f74bd1f9dcdfa8121115ee4
- transaction
- 7d38ece17401d33e49cc57af7fb22d696babad5d5820c9690194f16c75737904computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52606
the chainentry 52606
- sealed to the entry before
- cb523e3efb42e5df0de8b9dff50cd369fdf0a95cff0c1ff26990dc64f099b19d
- this leaf
- 871c5769e51e3328a3b93bf5fa2f9d642470275bcf153bd5500470b2e4730459
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- biyvpj2php/rPCnc31zzbVLb6BBZRok57ONHm376aNfQOA1gno4CEba0VnNDif8xckrLgQ8J6D69OqtJyaMxDQ==