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
- 06dc8c0af41f51f72deb4fd7ea42392388f529678d00dfac4c52650b4b393c5a
- request
- f3dbf79b9166e2c73b6bdc52d4e27082ee442eadf053f0c4bc6898652512cce7
- transaction
- 7ab17ec7606fece67d275900e83d0d2477a5aa1733ba041c7fb103841b20955fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28461
the chainentry 28461
- sealed to the entry before
- 5d1fb67222ca4cf77cd11f79eb7b664e861ed5e13ca7107cf1e3f3cfc1c909a4
- this leaf
- 08be6b6c6703e2d22f850bc669cbbcac591e10ece50e136dde3b107f7b6a855a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DQR+ocBSQBOYWF5naW7kodkDWsSPKGufyFXmwj+hanrqCw3ujBdgBu3NgqC77WdEMC6VP7yeslaupiD3dlR1CQ==