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
- ecc58ac217b1468ba1071ba190c4c67c90ec9cfa9e68245663e0c0e492fe7cc9
- request
- 3c175a5127ed8171345795c2717b3353805f101f8148fd9bae808fd67c643a74
- transaction
- 86770472d111a3befe7ec53bdd21a2c48858357a1ff77a7102c86155dc47a1bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56083
the chainentry 56083
- sealed to the entry before
- 91906da259ab976fc5b0c1c099eb64b0a9bf03aa55cbaab1d15ffa575eb99da9
- this leaf
- ac512553197244f6c64e0eefd61e746e5441416e167b60ad21e80a912526a39e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L1yYpLOjrZxCGkFBCg2Z1QNAD6TU55t8WZarqPkgocDa7mahVqqb7xDF0XnX+Ne9s2hE1+79GZ8IY5heme5sAw==