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
- 6903cbd5b9befaf2a0d1584064c3f9cae157b44a77d550bd9c9b727cbf9735f9
- request
- 833f4f2ee4438aed55dc36d7215265a751053b6950a98fe1e679ac6759dcc75c
- transaction
- 4aa4faf0dc286d604e075c6dcc447710b4481ca5b75e78ba3dbc4085f2d1cd04computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28480
the chainentry 28480
- sealed to the entry before
- 82efd52a68f5342ae789db3eea68548c7b7265db7a6aaca4945bbd7b445f3117
- this leaf
- d59e55474b6bfaea9f1e0c43b837c46074b91f9c01258e7a49b96c6d5dc64ca2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3raG8PMO9nq/3Dr3HkOzx4QYvpfmskUTnNYbthha4uS55vg9WbFzHeYJgTvOulCQU9+uU5tJPlflZbmFES9ZAg==