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
- 77404aeb13490c467673144e2460eaaa40dfac154a7ea585ced2652eaf463438
- request
- 65768cf3176ec94ddfe8f3d0e1ca0d82dcf7aba6bdf22ba3472b1d4446ab3a0c
- transaction
- fd8bb34a50a5e1ce9e7a7f2a1b6427f29812f438f6c38ef017f84c366a69cf7fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42079
the chainentry 42079
- sealed to the entry before
- d5e9c2f672c92ba71657e1566f863ba38291d7c76604e8ca6f3d08c9e4acf92d
- this leaf
- 388936e92e86e5a43a32965196d7fa9590b86a97188bb9f17a0168067990c8aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IN3azet6Pd7LGlmIGHdQ2U79uwgwk7CJGbY8xdYqxMX9ofSGOaqI+k2busuAFd6s1qoadNx7K0XSYdEL5yykAQ==