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
- 463f85904baa6f8f820bc42c5fd22b5c677414fb3a477956a7772fa2b9392e69
- request
- dae703dfb7d2ac6ae4d00e5f73271ebc589d11c8a10f8e0b4c6f27f17fcb3179
- transaction
- ee5d96da85149e8e97a3ff0b97815bf688d7e797625873a3016f80503e635fddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70221
the chainentry 70221
- sealed to the entry before
- e7570f885acd5ad7773bdd14c14a442bac44a806addb79e6f2d2975934e99d12
- this leaf
- 09d2a3aaf63bc75e5d014f98fa166834ea09ba6d5492f50deeec9f369bbf1c73
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lJsVbMn9yloVt+4oSZeQqHU/6pe8Bf1MkV14LtCJ0zVuenwLJNEFhYSmSu3/9mJUopp7BZgQZo1DiHJcQngEDQ==