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
- 36856aea7b719c97dc2daa02eb7cfa54b14155b85261e8aa9c13574459bfc2f9
- request
- b901e9bd34754d80d255e510bedd6bb204558d2691b94468ab68f90d97b4a2eb
- transaction
- 4e34692891888e806a49066562f93632696350d8f08961f5177d3cf1dc020e3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33832
the chainentry 33832
- sealed to the entry before
- 76e10148ce3ec187d4bcd5ac6b34084ae97d46130bc05dba9499f5f92c7a2a5a
- this leaf
- 44a68b7b255178162c0b38631db083c7804583ce9feed1b41fc7a6f780a3c2dc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L7Xpr/kHsNzTK3dNliGLRFasp4guNJdzWl+4JTaecjz3KzXvVkohC2Jy8DhSuA8UgBfF26CA9a8wQ54DPJ4zDA==