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
- 18666b316c6b09eb784aee75a151a64f4e28ae13437ee78a57715c2ce9e7705e
- request
- d6b7c2d6e7df82d6d69940fff9bf33cc753c845782309cd33eb86a99281d0ea5
- transaction
- ee89266a036114a019b1e7d0871d2bb14373762f1aa0809fe9e6a9e3600a4490computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43318
the chainentry 43318
- sealed to the entry before
- 8e94e05bd60327bf83cc4135ac0a15f8ba5fc894ccc5e471ec5ea9792dbed4e2
- this leaf
- d062fbb81f6834ce72fc80007442b97a4d86d9510f68fffa66ee2c6332043d59
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- epvRGBHDeIO7u6jmQ5bHOLvBufIMwrMXkumZa5RBp2c6HwliOOnPIO0VTMx5uOWC0iOsT2C5PWJDJa653ZFhCQ==