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
- 55c3932b835bb36f84cd4ec2aa73f33b1a64a7871669645ff4d8bf300ec7af96
- request
- 8c322a4b687a2d5bdd493f393695e8a63d5801d134b70d6e979bb5518a4730d8
- transaction
- c6f007b4ab2a81adaa9a110f8839a49487f19f7612d0cadf2d33aaf6765ce102computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3955
the chainentry 3955
- sealed to the entry before
- 1f1b9d8ba230076adc6885d37a06e5108365cfbf5755c9477033686ff2c68b2e
- this leaf
- 833414722a6414bcb6c57da5e6712fc92909e9b6fed3d362ccf2273826983518
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kfswSPGqISSRua44mlINTRHb4q5PZlKaeYaKyW0fWf+H7mL0fLlTbwJ/sikjxAI2lMP2SgjPsRLz/QZlh/X5Bw==