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
- a6cc7c31dfa50ef18ab12db54f52a088a9b211557a61cf2067059abe4dc41f9c
- request
- 944814d24fad8a54d5fda68b4f6eb34d750d103606aec17d470e3e812d466e0b
- transaction
- a2890ad0a128d6e1ccee810bcddadbc4f6f51d7ec9aed21ac68dfd6df625c8c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56430
the chainentry 56430
- sealed to the entry before
- eb4828d996791c82e78e661c944be7ed22b2ba793ea1bc6c2aa9c7b1b0fbdd50
- this leaf
- 0de197a49a148565e5309cc15d948898388ee1ae32587822042120bdb4185427
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cAu1n7/XlUK9QrM6OeHXgKywlssxNJpaokIqtbtBhstzdFYtkg13165A6pCzC45kgIO6Uti3ce9Gose746P3AA==