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
- f38fdd90e736542f38db02494dd34748dfa88801e9cebc5658092ee788452048
- request
- 15b2a399ddb37874505776c0c1ed142e8bf4d196252109baabc3d881312c1164
- transaction
- 671d941627b6830651a4960f7d12aa1369ea998a9ba0fbdd74243b9ba66d6474computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60261
the chainentry 60261
- sealed to the entry before
- 5ddca4d53c0709dfdce8caf470a7307d11de6531358cc5313a524f4f0b851da0
- this leaf
- 71765217ce7b9be288b8b61142d2c575b0ecb58cd6f186dab24dbf4903c38fea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0zWh9sNyiWU7quWT/DoIqh+75e3J2eNgM8cNo8EfXJELIgt6YnuWjOgnS/GsLf0+iaNYj+4M16kpF30cZkqEBQ==