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
- f03684e44c8f131e04de4db4e57e760be1312aa48612bc066ac2ba43e220f9eb
- request
- d8f382d7101cb66969823cd12ede2f14c3e18ec3fbd461b99c316594a479532e
- transaction
- 65be5e3a8452738483a1cb87554595b2f7ed8391394a6c650fb06728b626f65ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34172
the chainentry 34172
- sealed to the entry before
- 3fdc0ffaf143ba73cce63b82525d2caa2771b73fe701fab0d82da4f5934af445
- this leaf
- 5a1f463c31ac5b28d62bc725658d059d772088852921e01f6ad49b34604138f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IbDYmHnLrZzibGMroGIYUVoNCAlZUKCOHhVZ5jxueWP9fWPm2P0TryPyzjF9wwLrJIwdse4N1EXmmd9nYlGbAQ==