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
- cb96dbabbbe018e7d5b61e78268e66ae9b989db6c5659f950a289304893e9a76
- request
- e80fd2331456d1faea7f1e36a5bc12fc5f5d99e55b80d0898d18c76b0310c42d
- transaction
- fc36da8ad4b3318642ec46c3d0bea8be95cca960f2de06f6f8826b02f12f89b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54850
the chainentry 54850
- sealed to the entry before
- 83295530fd59236a7383dc512ed74db6f6af62e94580af199d4d7d268c054835
- this leaf
- 76fd2e9aaeb13d4f42b9510e5db03614a62c9a35a165aadaab0167316d27dd16
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1qMQu43fmuAi+hFQjQQtS4IWcxIIH1WJwnGPNRjPuca38quhNYegI0G8ZVziHGS0FrKI6lwjOkNw6wXeoBvaBA==