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
- e51a864e6ab524c8ecea825507e3e0175a86a869044604f0d421aed1b3cc1a03
- request
- 4be4054fa601bc4119877c732cfed854885159f55f16ff54198368be0fc4b88d
- transaction
- aa8eaa6745e2b79937d375550ce0ab70e1a397b69f9d3bfa909b0e470692ae51computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 771
the chainentry 771
- sealed to the entry before
- 4bf28a8a13bd373d4e63cf868d7cbe1adefb9f2ff7c26d196f6fea46845ef73b
- this leaf
- cdc639cd67a993c5f48e098770aa470d9ec7acd332c8a5a0116a29f7de1603b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- crvk2l8SRbvLHTFWNxRBq3VsVJG72Jnx3UsaIht6DhXlaTKlD49BSD6auiH9s5g5RFdP25K0V13hyyKlrYRLBg==