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
- a9579711d21f3fb82668340fc6196943366b6795940bb135d2d7ceca891eade3
- request
- f832cb30597c72f990dfcb9f4fb2f88ca8c6a4790af0e38df91ae0b266248e68
- transaction
- 269b36c4826c878a69df755ed1a41c47a4220686a6ae44fac32cad9afcc36c51computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67289
the chainentry 67289
- sealed to the entry before
- 2705d874d34b9f111af21f8236bda87ef1b3a9cc4430079e51f118de3d1e3ed6
- this leaf
- 92d5bc99277f6e853f347ceea4f6ceddb93889a548d05c7126cd661a7e163d05
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Haxbwlab5l26JgzLSTbZjR0iANJonqJ0CRVg4gi7gdG+dvYBP482qQv6gJwYNQyHokSM70+rTA4L88CwIheSDw==