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
- c445f6a806cc92bd5b39f118d60c7c8a91f6d898317a676570b7230b09788cad
- request
- 69d17c82615a6d7d783a9b53e060da04ec1d006269d8e77fbeca194c9f98f8ea
- transaction
- f1d202571860a95313972f66ee2293fa088838e61e308c8fe37c753f4a76228dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25310
the chainentry 25310
- sealed to the entry before
- cb50d839b4cb0fc5b5259c83bb24a60bdd016f18f6dd5022dd50d037e0f36fc3
- this leaf
- 7cc0283b823e8dcf9c6ed61562f124c58cbe40a7d150ae1de964c4ffa760d4a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LCAhLqtKjDPoLwbHYQrQOYccaQ2HTrJ1NsijJ6Oxav8ig4QafmCNg6m1kV7DGINJs5NRtD80YACr19f2Zv8GBg==