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
- 275cc8b51400bc241e08923a47e80ee0787da036c701fd8a61842d4c29826aa9
- request
- 2e214787ca831ea36df74d393fb8b3e1ba5d70df397720fae479de6f42fbe58e
- transaction
- e47c26bd1d2a4ee09f4f21708ca0c0b47b4aeb05350a3844bbb268dc58714cf0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44346
the chainentry 44346
- sealed to the entry before
- de093b43cd665ca0f2b63fd4d371113ca2fd00d26a3d5c3e9aae4e348c7abab6
- this leaf
- fa844960e21d85e9cd9b6bc1c3676432209c0ff4d26f702e5c1219e20ff3a95f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vv9gCbzgfaVCI62b2zeTwCijdxJiUQvYxH86ZqFTBcMnz8swpc0zHWlre60+NjQXvtZ87XrpmyzGf7tKkQd0DQ==