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
- 174d2b4ea6c28c25afe8fde307d6e32be813f5c58c8fb95e29e0b42b340949e1
- request
- 2de12ccc3d69b3c016cd8ebbf867110c942dd08b76caa3e9610ab5d21f52224e
- transaction
- 5d2c9bb8f00bc24535b9e956430513bd0a3d6e5c20b852100b1522555ba0fefccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 436
the chainentry 436
- sealed to the entry before
- c2c86e318cad477663ee6005530a5b9da2e327e6c5138b2d0f26156df2939129
- this leaf
- 2b6fb501837799b33beb8de21c3ab8c520babf687bef3cd66096cd625782bcee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NsQekqIXoDqdfWw6i86z3zbdFed5B9yUTJGlBzSk+Fdu39J480cC6ekfR04n+RSuTV8Jv3b0gtbx0iGASYLPBg==