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
- 4a8e41d274d8b9f8beeb401abc2292b177d3ce05a7f9869a06ab918c423d68bc
- request
- 5108cdb733374a7e6b695a60188ad8962beed88bb1e27a02774ae451b39d1cee
- transaction
- d6a674d04c8a333223baf78bccee8256edc69f38afafd1adb7409b5d01946a6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76620
the chainentry 76620
- sealed to the entry before
- 60c143522f059371807be473bf50a5ea80bb866733385f8148590165cf7fe046
- this leaf
- 2c759be6b6f685b5e2923c8f3a1be55adf9a03c2f9c9a60f4d723211b293d488
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y1ScH8tu2qkSUBUK/eSrVkLIMVrbUr/41XCPydqcyWpQiOpbuLLbjCA0sKhsrYBVXscbDeb06U2mtG8l1M3BCA==