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
- 9a35274c2bb72752e7056ca5e78cfde744cd51946c9287b50fae04374ab025a2
- request
- 22e46f818da3f4f642651b63dcda0d81431d234cb0b4c8eb8197c10514bf3c64
- transaction
- 6356fa5607fb1f801508bf4ccee454ad8db2814a7aa65546ea717e36640760c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28963
the chainentry 28963
- sealed to the entry before
- 3595fc0a146a1d87319b5c0e0066d45ebe88541e828e3ffd5a20c19fff0d1018
- this leaf
- b287331675ad6a95831124a599e3cd0588d38b168bbd7e2d2b0e68423ce2fc55
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q8V25ySBsxtKCjYThMD73J1gdXOjh3HCg643ut93027EhZQkvtWRzkGKCwn4M6C8vWBBi/ZV5jWt2AsFqOjIAA==