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
- 560f3f3318dd343238916f9e664e8c249367a07a96e157b6c6e3f5d4d65c154b
- request
- 17fb2a81bec427b848d0542ba4bcab88190ac449b2544d9258537515d28d911d
- transaction
- 6d6897960705b8decdf9d4fd429d326ac0aaec89fa57bf2769be2e301ab20b49computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61554
the chainentry 61554
- sealed to the entry before
- 8b0d67464b5d98fb554eb79c2a7bfa3d54e808a06186659b978c62104def1f55
- this leaf
- 5dedcbfa06b704d2f071275ee51ce799930475c0c2f0bbcf052bfdb2b9649711
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7W0Y5ZKPfMjsMWI323hZMrL1tOuB/eSg4hKPT2ngAeOcMc89F+SqHosrDKkGHeiitvK3MDwcRoVDKRqWZtSRBA==