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
- 12f1fa0d72d6c15749b509285f51194ed7feca1e0fa2adf6a5e229b98233bb8e
- request
- b89478c2286b709160b5ae7c741c723a95e242bdc32fc1e74100d83e740cba7d
- transaction
- 587e525a84b32de95d93d71300ed32ced2933a48d87200bd4035fa20f3c1d7f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50981
the chainentry 50981
- sealed to the entry before
- 9218879b08a53af49ca81926aea42ef129d1f5441cc30b787120feab8816f0e5
- this leaf
- 637bc86e50c824db6b1844d79d3fe7d00ad155f79f6f38802bd00beb278f4091
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IM9Ufvhqu/0HcFiI7dmQFPNikT+G2FmydnyQaFoSnOi0Q71X50RBfhgzpAGoNdiy1aK7oqIb4AfR2Yw1GWFTBw==