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
- cb9c14e0d3cee2102ec78ecb391c6aaa6ccce77196b0bb96b9e058e3bb635bbd
- request
- 3a1ecc1762c953902ff406001760c6d68ffa8cdc056d6afeb99587bbf9a7df5d
- transaction
- 93bf25e6535632ad92ec7c7a44dd03500b6ba774e71471a031f47f79d802ed04computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21357
the chainentry 21357
- sealed to the entry before
- 8204c43cc4ea04e7e47a78222d30a79501c90246c35a190c7e5815a5fa6e03db
- this leaf
- 75d0912b31b269b3f0d9afc6f05e910b2cdd08016da830f2350bcdc8788e9ce2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZzJkbQmEKuaCjW2Z19ZLL1F6PBcXe3UH1dZhFA8fvsXbGwI+ckw7U+XVJJnj38QlWBa8Qp7sd+Pgo5ME5lNhBw==