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
- 3dd296f44f4b6d175cda277d82f210066a9c6bfcb340340234488f74468fc25f
- request
- 3edf4efcf4e992a73cd90d63d1cc3470b4de746e33b9837aef7b9f39f9ea8961
- transaction
- 0c7639c2b73310d53756b162bd1a71923960ca92c8d80fd60bc061343960b8bdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50556
the chainentry 50556
- sealed to the entry before
- 77b1413d9e0df09d4684ee4946e9df01a1d2e5b621fc2f1d651d7b41b5b3d817
- this leaf
- f6fd6e2a384c0d4e6a9156c06de0631035ed2928cb391b44268aeb1f9b8cd7ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Whi5UKQgkfdm1oVU4ILHHqp+6GOjDpQFA9m9RIGaE70PdZNd/KFw33KuRANJBqr8QXkdmeJjdmHMwm/S4+hYCg==