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
- d3cc48154f35d53677a2414d5a5d4ffac1d848ff41612ff5ac2a63d399cb4040
- request
- bf55946cb20d6b0fe2d3964921ab9dab5d917d514805de4a8114f0d9bca37829
- transaction
- b9e7743af85ca88b637a6859328a1f318335f11c19474c9cfc7d44eeb9ce3fd9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16708
the chainentry 16708
- sealed to the entry before
- 92eec66d4917a4c331331861f25381532c055fc00eb87a25b4f5aaf98e4e73c9
- this leaf
- 718adbe12a6e962426f837d8be44a6c65533d8cf57aedce987b8446a495ecd7a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3AD7bOYtKKWu77AN81tu6pm8MbQicC1daADP8u9ESUy/gltNPcU7WxKknjgEk/I/zG4vHKr+H33+OQIYYjetAQ==