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
- 390e6e5f66f30b5ea6a55371ac357dc4637d678db87b1f875dfad5d44cca883c
- request
- ac64e4fe9c0003604d64bf694b17f485c0d96b5333b6ba6e8d22051e65641dd9
- transaction
- fb004376092597c557faa14c94898b0d14fc7899fdc970e31a4c9598630b0ff6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35227
the chainentry 35227
- sealed to the entry before
- adb1098c29cf8a742466f70afadae73314b698f8643f69bb872fbde0fb260b74
- this leaf
- e862a1d17aa9fa438a165aa3c1f1f2a598ecea62bb4c1a2bc841917924e336cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sPwbpK44b7v1IShUiEEfc75JnbFB5N0/QXYfPyKHTPUKQ/n4OvbKjvZ+Ct+Uf5vfH+H7GloUon30mMDp7j04Cg==