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
- 260f743f570cae4727cbf63844067d793f952390058949d88efeefd8803822e9
- request
- 2fc1e0f4e17ed39d42dc895fbef0cf19b7a5803787fb29781e1e375e3e02d6b0
- transaction
- 0ed55a3ac37163159b3b93dc6f0177afc97ac03101bc1e2cd3d2433507b894bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55426
the chainentry 55426
- sealed to the entry before
- 58860e49aea639091b213a32fc2e3f798715ad6514599a82362310d541dc4aeb
- this leaf
- d2037a9805a140c837e3965683bd398c804a56420a3c7c9f626e687ec24fef65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1hFQeBHOMiROcvmC83+yB8Qm3nqeYU5Y2A0lIyP8kUkHpueB6dCVj9zljO1+PNAC5AaxEg1GJccnwTLYOMLICw==