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
- 83b17dec615bcc6c6e2ec16b3e69d315a694db610d6a1596cc5afb37d571a347
- request
- 3d014c010de67f74128c4044100a22828fa498e86339288c3b1700ec976c9aa8
- transaction
- 5d9395764fba5bc0ca80f7836f19de42b99e47b70cb51c42768abfe060640184computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39103
the chainentry 39103
- sealed to the entry before
- 2313339009a800c614bae8f965b154c9bf7acdfc18bd06f35b8564353b6c2f40
- this leaf
- 2ef8830c6f12dcab5af8a37087167cb758f1920b992ab950c649785e9f32ee65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iq7r15CT94W3dTK9liTHJkWrnrZt8u3/f0fFUyhw4CFY7yjtDNpVvDYB9/oSsRDJ0iihR1KwfY7aF3kYUMXbBA==