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
- cae50459b46d911c2e28fc4133e668f07d9538ec14d7af01d56770fd9b58464b
- request
- 2cf7642f8881b1a501481fca81e6739aff3acfeac13664d6490118230bcdfbcf
- transaction
- c2d2729a36311e386ed4d20fa7d5799666781ee976e7841d5f0896e37e6bb733computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32718
the chainentry 32718
- sealed to the entry before
- 4664af20cec83c20d9056ad393d504f0ea42b12cb228d09164708fb499a8e208
- this leaf
- 165722443b21092516487b33251ab68d7ead01033b8594ad88b157be78c6cf4e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tUnVICTscMEc1WhEyJvqa70FjX2EY5uRley14fvM+4j6C7VMkjHc611x1Ylv0R1hwc6ThNFLJ72ixrE8/R61BQ==