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
- 32d21ab76af4cc863fa36dac55f6d43b23f9d21440c5c2799aec79bc8f53a139
- request
- ba95090c2f67a830ecc630710e754a0653584232f0eab1cd57ffb873db0c005f
- transaction
- 3fe4ff43e8a0ce7f5bb6b73c2781b4371331fae41918d589a7137eb1d6527107computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42602
the chainentry 42602
- sealed to the entry before
- 21b12d32e2a0aa9e11dc67a8fbec111c36fcee4253d36becda8bc7e24519df23
- this leaf
- ecf66db338ec9ca9f8f9262e8bf5a1f4bc202124e43afbd2c488af3e5e1fc0a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dk94U//PQm+gwjMw0uEVTQUyfCT+B+MU5+uH1S34Db0NNYDEpyRkAjsAT470HI3ak6A9xvG5kJltyGU37zbgCw==