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
- ff3d04b1eb917539e8ef2430a5c45ef41dcf48eb8cfcccc3186c721f13811d7d
- request
- ab0246e538f1c2d0e1a2be58d1eab6f6a374ffe28ec4f1225b7a6fb30d87e2bb
- transaction
- bd4423b81d6c0c5919ad15aabc22bdec74447d5f0949fdadecb7f478dfd9bbbbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42338
the chainentry 42338
- sealed to the entry before
- 2b11217e08befa48c77037a0cac2d80d42c3840fc7ceb433d929d0666f8f2f0f
- this leaf
- 0d4d7dfa583d760d796187a6288b755c64f82992bfba15d8e47d7d0fcef0f1e2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6EKjNkaBK7rG6rMlaFagR6IZZmdsSkoL+oF23A2uBOICIR32FMKQG7JjqJo1yr6l2hW010eJrAOeb7D97SJDAA==