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
- 329540dd9830b0eb53c6d939a0b1d442f9bfaa77c9c6bb0d5ba60d630447f31c
- request
- e17d3ebedd5bd4ef867995eebd1c903653fc58b41ea534a57bab35f41cbd84c8
- transaction
- c3739f08571a0e715278f364384958071e2d1dbdc63602d4114d52132e239687computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40296
the chainentry 40296
- sealed to the entry before
- 04118cb49e6b5a57d04ad0692cde054ce9059a18816c96aa59f9ad9ce4c7ce61
- this leaf
- 4fe23cb2d842e14cb8ba196fe5f12e7dd54ffd959e3b59f3e0b38761fb0a326e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FfxGvLnijrghF1qt5Kue4kDeKL/iJMV7QCI6oQRLJTpo9H+xu7alLsscbeo1QsokHLSLcLGSXhlX/ZfGu90yAQ==