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
- 1c17b1cc04e0f10acd53282d0e6669c0a3b446ea6fabc7d514052b643a6d3cc6
- request
- df1669de2c251dbaaa73d88e58ecde0d201a81b6945d9dbdc6bd48c4833e9a58
- transaction
- 1423b14f25f4582a49d513bf01bdb81f4aa8dff2c4219eac0fbc5e5b01462157computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60643
the chainentry 60643
- sealed to the entry before
- 5e83dbcab894d5b94ef4bda24a088995e9abe65f6ca4602bd56238f00508ed58
- this leaf
- 76ff49dfbfcac52b8f0ff54326f2cd18b052c889aab67f9ca655df5dda646a76
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GZgSSU89cxd10uD29co/4Qfk2ZcHx+UeoFparMsHhUJQpA2lpHJRc6df15BXl7tSH+tyxa5NYrne5GH9vi86Bw==