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
- 95acc992f671a355407de4003ac3053fe3cdd2b75b81bde2a4bab37e9dc68bf9
- request
- b8fefa549f8023021115af46b5d288fac261dab90c22db7f0b8f397481ee22de
- transaction
- 7997053a4ae4b6017c0559383dc09825f8dc382ce7d12d2e54d588233beb4714computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34827
the chainentry 34827
- sealed to the entry before
- e9d7d8ff9f68bfe3b80b2e08173fc4d43bf51b2910eb8da841efd4488ffc2197
- this leaf
- a8e48f559bf2f8bdb23da22b11763def63f8671f0312c9aa3446883205f79fcf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QQ84BaVRQPeWc8nZsniMNQHXijYudLUli/oR/TFBZS4d3Cth1cbmYSVuAzyaEYF4Eb425cB8qFVHsTzHfJKVAA==