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
- 548c945c80d95ac9f183a7eb9ef67d2cdf258f82877e8f1605797cbea730610a
- request
- 29221846ec5e88d0940ab3158961daf7bf4b43717242556095d24bbd4725c1c1
- transaction
- fd40ae6d8547b492452a816da7ee84a8f98532f15fb4912a42cf290d0d2cbfebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51023
the chainentry 51023
- sealed to the entry before
- 6d43d9e6373dbc59b625a9858d180887d68db5f1b46c9e2ca4701edeb2f29f96
- this leaf
- d382c87c2562a6c8644c3d9812352da6d59e58758b61010feaad8d9d108be97a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 08Bb/EmCJoTvka3lmtqdGCNgIk2cPQ/VyfVA5NPf2rwD3sBeCEo6CqRoa/A67bGxn9shd9VUcIqH58J4zOkwCw==