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
- a118dcc342f46fa7eaed5c7ad6945e5c1b34b5b080d329eeb00b3e4ac9de47ba
- request
- f33e85e3e4300766b12e8c8ed6b07505e89a3dc7240227d40fc8e6e2fed8a776
- transaction
- 89774494017e1d2963d02b4f21dcedd170d04b1ce2ece9a918635bee912414accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51443
the chainentry 51443
- sealed to the entry before
- 578aab825a3d65f08c06f9750613b91e19def94c20fdb32c207dd195adf9d209
- this leaf
- 6c8ff450b5862703e41c9a607d0dfa638926a4cc1c93635f37e5da01aefb08d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W1oH8ZGuTM9lomJnzihjSLW6h1XZgrft/ACvw8G81DCo2haqZcA1xfiLQC0BtSo9SoNP1lFHdteHSoPaqgJDCQ==