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
- 3c15a82f82beb693d71e88e278d1bd55713cd7eed1d67204ee6c927224b71d99
- request
- 14831b4114f8c65bd82514b5a2756cb62421c4080021767b89adaaaa86e970ec
- transaction
- 97d55a1c2104e36e3ea46ac9b8ee44db9e69c8857607ad672de5fadf43952b37computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11022
the chainentry 11022
- sealed to the entry before
- 0c985e642ec9bc8377ecc770c7235b1ac243855b05e462a9dca85eb956f0c8de
- this leaf
- 3b424f3fdafcb5f013268ed7521d08c6260b3dbbabb1920bacbca6adeabbbdd5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JN6dGMxwq8tHFO6c3iGaokz4Zb9PIVoC5by3GF6YLk3d6GDrHBcdFozQJevmjv4RQuQaKGhkRfZ994/IGcrBBg==