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
- d777d6cfed988403eb0e895bda928c95ce5cdf2d910f164ff74a9da4ed6659ae
- request
- b5524ee676ceb1d4e4625c9ea644844a452dddc59c5cace45093ea6e6d7b9b96
- transaction
- d7c5b29c8e418ef00ea0ae03637abb69edee72057233fbfdb34a35372fe9ec83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6414
the chainentry 6414
- sealed to the entry before
- d517f7971dbfe2b977f923575ac42a2163b51f42828d31420e792f58dd1b3e43
- this leaf
- be899d5362ab0125c0a752ccea01a90f11f01458d23e11b2b8aa31c0d6c20f0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lHCERBr9zA0FCqPNozrm0O1a0XhO68+PcBhb1zaMMTam1aH70/Ufk8ig6/jpjRJxe45RAAJtc67gmcDOvjjmDA==