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
- 172d596548bde42b966cbaa7be6f9af4abbddfc67ec59e76f59715f8c21ec0af
- request
- 3505f691debc26145962faf6deee670e815244978d2851302b31bdea346df0fb
- transaction
- 9557d623794b59daa96df4fbd02b968217eb4e220b509c14c42d9351e4b9165acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23780
the chainentry 23780
- sealed to the entry before
- 5c0a3bca631cad7c67516d548bd3b69a26ae00fa3eaf7790522da35f24ea1f14
- this leaf
- 5bcd4e7f9f7ebf0f99cc397faf9920941bf3f450fecdb36e03f3176bf1ebb20e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0Ta0JmwBfaRDI5b4iS2qZYWxxwrSSVXcHXzxLSWNiiMudNKeS/hyOejXaUUtOI4zCKEkRe14DhD//O4c+tBFDA==