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
- 0c6ed141f362e13817def97c915c304e11f4a0c09acb57f5ca47cd784ff26ad2
- request
- 4b0a42b89c17f0f03099f667df4781f58296c7f6bd84395075dd755bcf2f44fa
- transaction
- 963b716560dc355693c5f9cfa6be7eb42e7165c88a0c60dfa6076e6118fc5168computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53309
the chainentry 53309
- sealed to the entry before
- c4adea679b691451bf10fa0a33e4c192f1587b88b4a6e40d45ba147a09ac85c5
- this leaf
- 2c74891d4d169e728d0097ca1a3984ede27be5b46623db945de1dce85e3d058f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9zvTZuNsa+qXlkX45AdVFYwdxRjbpGke9AAGm9oizeeHtFvY8a5rnXiqToljLPziTFJ1HikVqVOoGmu8dQSEDw==