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
- 6f0643afab25920a4c8b538bdb5978f19558cbbdd3769cbc1d5c2492edb1f612
- request
- ff949d4ea8d921d8461e168538124798e8b3390b999e667d9847d2dbcd451fac
- transaction
- 2e07c686783e6fd6c6bdc7fd189b50333b7b9fd3e41012c6cc7ba27496564e17computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8469
the chainentry 8469
- sealed to the entry before
- 4a573e0e922788eee2c5c91af03c2825fa20d77328ac7b2b8f29f43db8726ebb
- this leaf
- 5798f16df63af7f5b3aa294d27e691fdf77e48c2bce1192b4d13b13e6fe0f1b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u7aVJ5g4Ap/jODlGMfbEhkf0/t3HKaiwJ4txmzVGKFXGjPHGvRRxbc32gfGaeSxz1tF3FJi0lkuZmOhtCsWRCA==