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
- a248c5fd1c2e7d69b91c3bc4a735d7f8081f493f3c64b9df6be429440babe6c9
- request
- 8b9e5219d6a22589da73021dca7a038e8906d99abdd0f49d4d42dbb59708987b
- transaction
- 421e1eeb1a1b6a6625f4110b7392ac946efe1523ad768043e1800de5fcd66455computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77021
the chainentry 77021
- sealed to the entry before
- d6b103ab028dea5a0b11ec8cf970427881f1a9bde152c18524d18f606e40716f
- this leaf
- d67f9759820f428c219cd70774563eb1d25f60937b8361c57425251c02e7eb46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e1tjhnGfkyJ+JZxSfHU/li9pJJ5zEgg0COGtYCMHkzksxIIwc0qVbEah0JGvCRuDQ/l8Hm+cF11k34Ij+vI4Cw==