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
- 774fe5164c969212f9bcbf759c385f23c52d85a98cb7820768a47f98326ec629
- request
- fc3e3dcdb90e8d2e6fed2d147d68234629d3eddb8600b422bc1372592fe4439a
- transaction
- 358c8be6347fd283c4e9f9c90f0910b420fb94f9ecfcef2f706323827afd61eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41010
the chainentry 41010
- sealed to the entry before
- 4df05963ffb461ee4cb0915c3e6aefe9dc27789eaa56b0c5a8e94b4456e75f42
- this leaf
- a75657b5412c0de2ae2ea95dd6696ee6c1b76a57efe35f577e93bd81d5ec149e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4CZJJwkeC0QG1idaqqDqkI80KkOULwm40LgtDa+ony2xOCb5FS6e5JQGo5Dmeb0uKFAFW4RgDblbFZDJs6giCw==