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
- 2b4c9b9a4c6192525b2f64ea45380b6f3683fb8ff7d5b9bd8b9fbc8ba0bd9c6a
- request
- 544199cc554e47a44094869bde8f51053b05e963dce39a91906b5837a42e5a52
- transaction
- 4bdfa891f9031240964098ceb2984515e9ae987f792e781325f381498aa828ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37029
the chainentry 37029
- sealed to the entry before
- 7cc6caab3eab7dfff2ab890bbda39dcf747c07eab8e410c4ef46a35b83e5b590
- this leaf
- 79d4c9bb096a1e1bfa0eb1fb146efaf82f0d38c32220268d4f2ca1a116cfab81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z6KGthK45fkNAO4vRAClfIZpzpdFcJ11mLIi2hriDaqu85EDwMpUygCkabWWDvuFPOOkeP3W/1fURA5p/8euAQ==