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
- 050939ff9def59e9d3697d3bd90f7368f4d2a37a0e27bd5b1143969320e91adf
- request
- 191daffde5b3318602432d00c7ab10e36d03206516ad7897e65a6e6cddefeb06
- transaction
- 613072daacada6d70f82a8ee8c35dc8b669fc414ea579a8c13db51c9c3f502d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67897
the chainentry 67897
- sealed to the entry before
- bf8086929d3e0e8ef1f73d2eab7f6df37aa44e58350a43e80fdbb8b77f5279e7
- this leaf
- cf5522bcb0b724d21eb782ffaf422b20a344d5767d25a3bb79e45126798ec339
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zil3FmvifTA3R528PIQDpYRW6LIb9w8xngUXgMjna5LjSF1sanz3ovoq87pXMgiBeqqT8W8fKgkctmJAnKrPBg==