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
- 6a3e3beb9340abf1e1daa2493f66c861365e2f348b595445317e8eb3ed694610
- request
- dfd3f570762db69cd534c62b4a1ea913e0688abe07d449ca027ff85f32aa4121
- transaction
- 23c3aa60430c75076a64e8ee46f232054a4b2560667052a1096e0b6dafeffca4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1625
the chainentry 1625
- sealed to the entry before
- 94075957dadc5d405dbf94124dc4f0eda321b23e2f66d2fb1c8c8ba61e067981
- this leaf
- 65171a5d01a1c50d30ff93efbe45e9d910b5b34214205d0fba72a44d5367e701
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EGlbnvmGXSMYHDj31jbsylc1xG9k/WC7/gZo3P7CUIXK12kDwRvIngiNLRL4nyTCS0pIFFCRfcz4+nzxyv6UBw==