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
- 3d5bf2b89fccabf57e50f404d2bbc2aee954231d12e783443fbd754d83e3421a
- request
- 26a939166da785c91c0d84b1a35a89f1c0268ea3026af3b43c3183a3ef05f55d
- transaction
- 73ff5f83bb3fd23b227de357a35a97f10d32d7b6f7f75d3a151eee6f98a03641computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62006
the chainentry 62006
- sealed to the entry before
- cfb55c415b6158c1e904236ca74c72c15f26ce8fe50c989296fd678f96f574ce
- this leaf
- 940fc5d515d7ca0f4ec9d1202c496d470b81a3b809b519181544e048fe202113
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2aal7lQK0CZ2hvcUn9AZ72qHhvX0dUVuFsjuQ7krNAD/TxRCiXT7zEqDwVOF7EZjdOerEKuG3a5udBR9GP4PAg==