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
- 9561de822c3d1471feca3c43f483e588e028e92d1e1c100601e7466caa52fd68
- request
- 6c54fa314d97653e5711914d83a5235545420ca544816896f53c3689c6bbec47
- transaction
- 594a527e014e54f63cd5ef09c8a96ad3fbf376587853c54fd8aa03c71b97f11dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55764
the chainentry 55764
- sealed to the entry before
- f5e51064c4fef86639d752bdc4c8bc6e29f5433b941e0db936509fa92f892c9b
- this leaf
- 21c43f30a473cf0e3589e368a7ced4d80f50f8a624c10bf28ca5b130e46affc4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KwT/2PC09FcRupnpmCIkXPVdUjcH8+Ci85vr9MdacvOdtVZ2ynkRK23dK9/6jzkx2v6iNFespvPasaVbQ5GeCg==