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
- 180fcc81b21699cb3b0baf211402f50d7451b8f5086a4f0ab916cfc18c873401
- request
- 31d6c171576428ef97de331084d93539bb8be1394c5d32b77a99c124af8901f7
- transaction
- e0b4542c1fbe30424f2f86275524e3508b36fc377dfba6da6d3e42b855cb34afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39664
the chainentry 39664
- sealed to the entry before
- 44dcf02a281704a6aef3b97d570c33c7829626568060e1002e817cc38cbb2c47
- this leaf
- e660ec969429b6b83dd4c26a7641304cad78b824274699fcef39f6078b4ad655
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ghy57MSTPPAMlYymBM9cFGBYWRhu1Q9qshOuxxsfWHLXSIIISwR0ixDNQ0D776J8ZnGFESS76FYyzYxWPBvSBA==