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
- 530b05a6815718a1468b433f70f82421e4b8a188635320dc3b68cc641dab0a86
- request
- ca3d126b937a38aac9be99decc56aeb0dd57f9ec6687d635663d9d957ad0d22d
- transaction
- 84bce224ad4e65752ca1e7f99f2928cabdbe583e409d46247bda5ef5e91b7e22computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10686
the chainentry 10686
- sealed to the entry before
- a335b0301176e048891cc245557b76e80c77cd9c7ce8007c032510d79263d4ae
- this leaf
- dcb056dffdc383b6df1148633910b510bc189cf8545ac40e2eb2f7b6ab660f35
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- safW5b1JpG2izVA5P0oPUl2GrwK1e8MPet9yB/Ui0FJ4Ep45R9j2twYpxIbyNTZgj1E/p/thIGtnAYOgLyW0DQ==