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
- 054859d937fec8ecc1f5c83fed65de30955b30b08c65fc59b9f104ac03725298
- request
- c92186b2a6d808fb1b365c7724e4fd0079ea9380e6ccd0da3b090ac3db094f7c
- transaction
- fd10acfa0eace2385c71b1a8f7ff037c07e68681ece807a5ff4139f01ad3de01computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71547
the chainentry 71547
- sealed to the entry before
- 8c97f03f55adbd2b62409bc0237b9b48c7d87b781d3de14ed31679cc8b332aab
- this leaf
- 9a4a4b46b7333efa636d77851a5788d02adb9a8cc98516518f23905b3c9df7e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jJ2j5QSzbiOigGIiL4L6A0GoO27/M6836SsC9GttvZL4y7IwIHpto5/DxnxGje3n972dzNzVH9jU9469QC2ABA==