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
- a9b37a989f8756e037e0be08072cf4d51134288e88b826b69127ac1cbd7796cb
- request
- ba1be685e55f6cd5641387328315549a39615cf4d5f18f14b81d06762d418751
- transaction
- 01d275fcd7033c940de0d0bc278349834945b0c95c4840602b74deb0c16fdc59computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4058
the chainentry 4058
- sealed to the entry before
- a3ed0f178b6e6354c333aacef262d3ab8363dc2b85bb40623bad9d9be1edd6bf
- this leaf
- e63422b3e19765d5f3d0765856de18fdd0cb18a5abc0f09f3584a467d89f1c6a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tvMfrhjQysz5pkfIEa6XfJUVlTOyOk8X7CbuCTIdcUPxbtS0ODNHHnOaSap0APn05QTz1Ccx8JYCEbbyX5uHCg==