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
- 4580ba90305dc6c72a94d813e385ddf50daffeca2ccd2128990419f580a10b6f
- request
- 78fdde59bd2daf02c9a42140dc72db003a2fb5766c3b497876386aec98760187
- transaction
- 3a09a16adeb550cd9b2a99bd5d85445c369c91cb8eb971916345285dbdde036ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48118
the chainentry 48118
- sealed to the entry before
- eea2dd104f46a355f5c2c0441fc6c2d9d8586d84aacfb18e992cc47e09a841e7
- this leaf
- b54d9fafaa44c123d167c6fb87451547eb6b535d7dc348c33fdd6eda85cdcd4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FxPGFHeQdtY7hFqu0BW4zXfN+QsCy3V7ZV23bmNDs9lJ8LrntKjecT2ebDGtDfEzW8rPsEbGRAbwxiqOm9B1BA==