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
- 79c4c22498d60b00d67dc71f35628e1abc306454543787693150aea67b750f08
- request
- b492138fd0f27fe5601e70b902479102bdcd26f6cea77d239aa9da00ab7c6ed2
- transaction
- 72c3c3d54e1bd3db71d8e11eb89d0002ca480deec3cebee9b58f01976f4b615ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23705
the chainentry 23705
- sealed to the entry before
- 9c88c88d620c9d53cc4ba64d5a94b66621b849fd180e0aedc9a8e00c81c73c36
- this leaf
- 04eb6369d3e20ca99c0924801779c74a847b9a68692bea1345fbdcded8af5933
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G5jTgM4iSkfW5VlhJV6BIyCAKZXhuyq6wAgeosscH+nnrBhzH1LEURFWqpzDScUAyntGXODgf7s0P+mCNsDzBQ==