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
- f4c59d5aab0b50b41df4ae9eb3bb48a66b5245656405083781fdc89b5df1c654
- request
- 39de6803bb43d99f04be466fa516cc22297db435c69d61ea21e4f13acf629a1f
- transaction
- 33b03e48228090aa28a6574b5f7ae5798806b751f27650bcfedcdb86f4ed1eaecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27122
the chainentry 27122
- sealed to the entry before
- e557d6d9b5b382333c312174f4f4afb9e80682c0ab44a2bcda5ab6f4244dc409
- this leaf
- 6f6dee079b94f0b5fcee4ca2f6b4f0f71304ace599e0dc462e3efcb7caf35340
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qv8PFapq+hKKI9cIehwfNChVIOFVNSxGEDm2L1vfkQC/xI2eo77wVZBGxMEZSfNv78uSI6E7WJbzsvueGlFOAA==