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
- 53bf38b62d27c83ff545d6ab0636cc91ef65d46055bf943989aa55bd794aad0f
- request
- ca4cfc63a4281502172e64b1998af2c1092f411393d5eff7517ab7d1dbb8a9e2
- transaction
- 5efff21ff5800aa0387c1de7f5d316f8d8c739a6d2d157bf66815aa5043d185ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65849
the chainentry 65849
- sealed to the entry before
- 0d1ed556300b4b19a70992b3cfce9734311da6e1532f18fae6970db47cab6efc
- this leaf
- 8b64b1bdaafe4fa8448bdb807b55b14f43a4daceff29a50c8b997557f8ea1343
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 26cGLShrCcZ1AF28TFBZlo0yRntUnY9QH12lYH/6EdQVVr4PlyiM9aUblMCKsdSP1dOFh3JirIuuPSBOt3EGBA==