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
- aaee0a52a9528efbc7fe9405fa91e4bc462647344891be23a5db226544d876bc
- request
- 542dd6ebcfdf17c3487a993015ec3c5a9aedd70aae2b433f0491e06fd0de530b
- transaction
- c2771a2083b2acfb162ca7ba0dab5cfb2e72d23d95fd511a42522be0053c1e5bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54410
the chainentry 54410
- sealed to the entry before
- b2c59cc3a06068d6e0fe9d05d07c3b2ff6272e3f6bd5d675e1af35ee4cb4034d
- this leaf
- 27cbf5ba3ef61bd9d082e9a8f5069901af1a37b4bd5ee38da4ca98f36620de0f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nLZZnHl76CmURsyOjEY6vnCs2kl19DiphlqNsK5ZL2K81qyR7/I9h9vFKxM7EmBmCsnWkzhFzHvS9sE2c0WyCg==