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
- 3a4e7308dce8b0ad083403b884228955d1c4c85dbe81195c843a8b84fe30653a
- request
- 4f6b14f323b17744922c401ffad2a8ea58110baf1d0c9976942cd2843e229446
- transaction
- 3403e52c657224afc515b72ea7b8813514fa3c3957e2196d0e26310baf6bea81computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20501
the chainentry 20501
- sealed to the entry before
- a91e1bee6a26346dbaf18f8db289041bcbff9729c4cb5cd74fa37c3d27a8e28c
- this leaf
- 27a0aa150e4d2e509f2b4b1dee4db310eaec97cd9d0e8c24bcf58c0cce8b043a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- erBv7UzqJ8UMOabEKOQ5XYBG6yw4xIU1XUkX+0UC8TXQ5l+5TffqETDhofpnlYRTsiyA28yC6lFBFUlx6+huBA==