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
- 58a21a81b2123a1a0f866638fd37f0f9cb6eceb80e75037b2ce84ba8d917660f
- request
- 54bfe96111b30f2bbf68ccef77ce8594d0005420497426a3bbe0c38f449aef4e
- transaction
- 22c25ed5e302bf01ad7151b4dc78bb05befd85c6a0c07cbc0d4d7d16590312e6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51725
the chainentry 51725
- sealed to the entry before
- cccb1d45a41c947f4b589593c9e8ae547583e4416e2f463fcffb7d3f08062dc8
- this leaf
- 6a8a7a2ce1b7b66af04dd68e86ffef769afc2c14a70a8bb12b315509f60de8af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yF/OHwNJFe4Df9C46qvJHaY7+XNlJ21zT/16t+jjwizXyErYGSvykP7Eo2C7LqSHz6lXRg5rXho1FuWUPRflBg==