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
- 8dcaef50080cfbe29d3b5e9ba9b0bf7c585bbe0a98f673c860d4ec4f2cdb638f
- request
- 0e8383113d4d22e068ae32bd5e13c45b596c0564b6535034163c1404a8d80dab
- transaction
- b97ac5f26fb15cdea0fdeb71e3838caa4bcf7b855d30e13450e119a27487d6facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30439
the chainentry 30439
- sealed to the entry before
- f68871bb0dd1a1411df889f007d34f1b8d9921693a5d9c902ec12e5c41c62e5a
- this leaf
- 35cdcce9510725136345aa3901308b969993cba2e54213c1c8b1af778c3da83a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HZBVhzDU1+yVBmPeJvtflEamUzQLgJPtiOEAghJX/TBS8lQGlJB+BeI+HaS5uGzR9VcgxjO1rKnpOhQNiUz7BQ==