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
- dea94ba62ddb4e7b523ae32662f82e383ebb561d506c50bc467fc1c997758c07
- request
- 3e9b7c7413809c4a80b50943db40e7f5ab31394f05caf745ef1cf676d833e37d
- transaction
- bece2869b57cc6d566b13b29f4a350cd591c77fbada75dc8a71fd9d8984b1af2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49003
the chainentry 49003
- sealed to the entry before
- f8ab127272575c2123ac1771e0010eb1778c651513eabdfd9ae9db51ea6676d2
- this leaf
- 725fba256c16ef6667c7ba92e9858b45d66edf0c610e4b2d5640f57191068cee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CP4dWr4tF3BwbClXtEfYo2qsjwBKqmhxuajWNA/qa+ePs25c59ugh9tpwE19Swr8i+lQN7xVVT6WROxliCoMDA==