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
- 62fa2cab5e3464710be02a03c4e2a49d89dc14338431be2b184a5d5cd9962c9f
- request
- f63ac718e80d36c18c2435e0149fcb7cd3a2190e4edf2bfa55cbf4ca72416298
- transaction
- 77dddbff95ffe1c5b7f757a12d3f6243bf1cab3c1d06fc0d9ca9ca16388b1cd7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72749
the chainentry 72749
- sealed to the entry before
- 9e575a6fc3bae5e5811b324e0d08bc08598f7897e05ae3a587d2185898beb15a
- this leaf
- 4980a0d1f4cd006434dabfa679fe79df78cf81e8b72f8497bd60958c02c82d2b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YpQKp455EK/bT1cqYMlSUIOFuxW4R5IN2JTdq85pvyLMefGt1KHkwz4LAh420F8Ne2aAviJpsyAzYYe0G+83Cw==