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
- bc9ea92493ffdee52e6b1f1c2535055d27d8db24bc0d7b6eea7afe4158f85122
- request
- 9f98f25464128d4522668567effa2730b119a15b09b9cfd148a79ef0fc6215df
- transaction
- 9101a60af3f3741dfe98bcaf45796a1b9e14900dbac91757966ddc0c1362d744computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18038
the chainentry 18038
- sealed to the entry before
- 7bc314e86f0f8dcd7ebb2d67499a892ba9167f5e36edbf71268f93190a41d8b4
- this leaf
- a1a93e11909bd1d087a1d8e2c41c7283ec199f107950fd0cf8e27d723c1c7d43
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eDVsMv61s4pWZ9F7NsHNCydcciulMBVNoH1y7ZRln3eXjy88LuodhKOPsI18vXOUjcJ3+arRBnv7fFaR7+rQCg==