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
- 4c886f50cea5e83fd806f5a6206dc3e0a899610814e601f2adcd17477779cca4
- request
- ef7972587a299727c9bea2d1c42d6efdf398fe180c1cda2333d7d9f675ce67e8
- transaction
- 0b4b0fe9890f0032d68dc62e75f830402663b46a450b3121fe0d4a6ea2408c8ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35166
the chainentry 35166
- sealed to the entry before
- 632a709f0acf0cc3cad9be67490ce3c5f6eeeb641a32f0916e196994f8dc36ad
- this leaf
- ec5b17018f5b0e4c73ea8c3f70564558d86c4b7e53fdbad46e3462934d86b733
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UiBUYH++qTELJyRANXuResq9UqloikRQLjWymGixLqnMhkDnjTTadReYn2zNMt1P482JRsd62JOzkWndV7ojBg==