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
- 0207acb44395aa69d0a1ecedec053849d80f79b696f1852e6493114096511b22
- request
- abd12c40ec04ee523da57932ef3b3b68eb5d77982fd95fe2771cc3c924e11a5b
- transaction
- 4145b74129f316ec3c8c3b2ac8fe0bc83664dbb5bf0de73ccb0558a0813b2d5dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8936
the chainentry 8936
- sealed to the entry before
- 81321a2c56bed3438f40ec322213b93290bd2a5a2417435c1a672a6a4d0c9167
- this leaf
- 0081460a64992059427e4b8d9b0a16607c96cca54b15f9c345d0cb301b9f1698
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8ILAM2uYkbdDIHHUUTydAZmt8HyZrEkw9C9+znqZOjQ0wJwz79OLVDO0LEQ9fmO+48OWMafPUkBfWRgPZAPUAw==