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
- ea6941dfcccdb48b670e04f21362ab83209d9d3c2986bded0723634471a94c37
- request
- fc683a0c3d53873ddf5333e2a313fa3a1ac208d971e4328b55706394622d5234
- transaction
- 8011b124ba585001bd65e2e1f4a873b4f2c62973d6dd7782de82035ea2f04ab4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75067
the chainentry 75067
- sealed to the entry before
- 29566c4da060bcf032c7ddf310cbb8ed74b5b8dfc42c6b1200870b655defb113
- this leaf
- c71d04f342d8fc9567c936c18d1d3a4a8e3958b46cd531752771db4c105db383
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UDshnabD30mi5OZIn+GNbUYQX+QQ+gr8TVID/zF8wmyx27d3jbSmCGkFpHhe7JKOtO6O/9d33OEOEbd5zwQTCg==