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
- e229357a0b21145e624883fe241f8f0da3462d8f2b14880a53ccecb6d37ef20d
- request
- d4ad241c441e31e203f085355c049404479050361e19b62096e4bb07d4efc472
- transaction
- 75d34f312b01d5b113f0aa23e468bd184f5c769a01776e4ff688361749c9a455computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19001
the chainentry 19001
- sealed to the entry before
- bdaaadd383572adbc7b3a8e4a12b0f683234e25f39533860ca3d03ad88064d36
- this leaf
- ae7968f64a881ac361c5378c5428a9ebe3314399ae7af32d9bfdfa8892b1b797
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9zcxAEKCUe5615hT0pPq5RZROVBjIB35IumZHM+f74sGT5bkCxvKbNBYmvocXwehIFtosMlpJRWw9KmJ3xGfDA==