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
- d48762f9a755dde77c4b5db0aa279b644ecf7591f6205df91844f967013be24a
- request
- 03560a5155027b370faec5953fa41e06717e748aacde9fabb1afef1964f8b986
- transaction
- 83b83d0dce0ef4eccbbbb3168ce48204247de965321884e235505bd09f4acdfecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21105
the chainentry 21105
- sealed to the entry before
- 121d7d3b2099ea9b632d4d5ac2c2ef109470a9b8983afab802192e5d544cbc9f
- this leaf
- b82918aee4c12403604e84f1284c130932b69c9ce55b2e929725321ed688945e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dy2Jv/y7qH7xrZICy0BWsV8tq7ZBEh0SmL7tLC/LtaWd7paMX5E9kYzCLM6xYG1ayqLWvASb2wnEFiFqZ8ugBA==