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
- 363f87e55c33efba287e1daa9221bf0c3db97cbdb685ed96733a244e9dc8634d
- request
- 9d6d1396e54f28c3d4bb6aa164ca52671feb7c9e73b037fd34b736b54d6c6d04
- transaction
- fafd5ec344e109f99a47fb10b054a00a3be752bfcab8b4a31bb31fb057b8690bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16465
the chainentry 16465
- sealed to the entry before
- 25d489dec6c170a2f3c4157aeff8df0e1521cf64e80e776000dd25c09a9efc00
- this leaf
- 477f510aa30d0219a7d34e3e2f9f29e0e0f223bc92e0d6da7387dfc2f73e91aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H5QOhh1KFznnJnHRDGBMmjnrCz7D8byL0VCHEPGWfrrclBsl+wT/TJX8QCuujsrpkdXyh/Bkg845dziTZjPODg==