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
- 277f2b409c8fe790a989ffe3cbe0e4a3008a242c0d32d68f3d54f8d22f339f2d
- request
- 865419a9365faa3bbf5cbf3d52ca63cca7ea33d89bb8086778c91b3923a38e12
- transaction
- 93021ed522d60539574a2ce70db80c99ed9bba8fd48dc475f8cf5dfe7b155b70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71095
the chainentry 71095
- sealed to the entry before
- f2bf8d19aec6f201a4fd1d76f8c5f8bd830c88ddd1852e902a99a710980d14a2
- this leaf
- 8e3b3c24bf4f34a7f6563269b42f9feaa61d74bd26a6387a83e694286c901209
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HngAzOHSNEeUgDWH+AFArr6Rjo/nPY6/ehJIC05sXAwPT++iUQMe96sErNb3m20dQUPZv85xrADXCzTTocfLCg==