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
- c4f78f31269e1343335f65351a507f889646cdb953abeb867044bd4ae11b3c07
- request
- a003871d303858babe59c58b121e3c202bb8bae260a137797ce4da2230ffa25d
- transaction
- 092d8ebceb657bd937a53689f942ed92b0137dd7cc30186d2f2ee9c6c44f32cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10023
the chainentry 10023
- sealed to the entry before
- 7f2e4442352fef15a3b9c38be838a6b2defb07ea80d35c4774af2b07e9cad2c5
- this leaf
- de03e34cf49028aff815bec60803777b059e5e3c11d483b1c34528ef7e039cc8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fjnFaZZHXrugdWXNAyscFolh40vTYPxiCGhaMfWjnqdfdT0Gchp4e1hBI+Bw69OfkGn420nbLMgNt70d0sZjBQ==