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
- 3310e5b3910b31e0a192e9ced331fd3f8aaa826db5446e72efd64be50b76be7a
- request
- 958bcc05587cf9f81e3c3ccd81118b62b0cb44e8acdb5a1ce54d84b7bbe13ac5
- transaction
- 1e7cde22380cb6dba6e596ebb5cfed12af2716e828d1cb52f99b192d4466efd3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45659
the chainentry 45659
- sealed to the entry before
- 946f2caf0a17ed33b0e3c5a772085fa5c7afb674b65d3f58cde71d540332440a
- this leaf
- c35201188b87216bf7ce23048a9a267f6da5c57e64aa984b76490983d3b149f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TagRvGIbPPKQ0DjaIlusyGOG1pnjonuUJSjjrGKTDbsGLNGNu5X6FVxW9Kcu9Ogkn45Kyw4APpY1Hc17B9qDBQ==