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
- bf4124b78e4319dd657bd331127a9f0011edb2c5e5b2b45788ebd615cf5566f8
- request
- 9f3bb7ee6ec6bd3ea7eb3b4c1d43427926ba32b82333f893aa16567261bb634a
- transaction
- e1b350c0697b3d8db2ac8d7a9c833863db46a9c3be5f86b7dd48f3f7a031a296computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72159
the chainentry 72159
- sealed to the entry before
- 8ad050d4d77b3f0058d4556dda346bffbebbf975d427c6986efbeb96157a8886
- this leaf
- 2d64ce1f59b857df92122cf9860d6de7da824b37f1519a5bcd1b1491f3da1657
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l+e3heVjFduNZSMrSkHk2ST7d6qUGQ0fEFhQE59UmHJcmGL1Ujvu1AKFrqY3Pei8VvWfa7146Sy/dOcbSTV6DQ==