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
- 0ef21aecb761c8127db6bc71a4ca557aba775857a2f2cfc0de5dec1603e1d1d5
- request
- 64253677a5e384523535d05910ef40c95d83fd582d2ace7b1398dabede969267
- transaction
- ed6fcc05faba3b690f31095fddda1306f1b8a197e84ec759e638d657151f528fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23333
the chainentry 23333
- sealed to the entry before
- c2e975ef09b134917f39486d0468a8c3f88183c1441c7e02c9180676bd7f6b68
- this leaf
- 55e8d930998ab9b4690705fa0cb82cd6947ef1e62ed30542491b6d2942898f73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- faK+ips09Jjc0qQY7DQ/yCpHZSK3QhV3+DsQoMx+AFd5+KQ7E9TRNYkW5AQMhtqqwwhc5qUh7PvhIm8EhaPhBA==