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
- 5cde598f5d9628ec1e4b97b787c16c8b98e21705c7dbfb145d66c8f3faab9a66
- request
- 6900ab738303be268666f703499ac89da42f62e6bd26d6755b5e66f4118d5c9e
- transaction
- 021a0a4873cdd18e3a31c0650bb1c1920863116791428339bdfed25742179321computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 846
the chainentry 846
- sealed to the entry before
- 33f9a516acdc6a8123b43296d582de1bacca3d5db69d19c8ddc326e9519df279
- this leaf
- bca0d06409a3dea01987c66ea9b7c0bc1b3363436f78442335bb0cfe05138960
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- trEAGIOp6l5Hb03fgdgFfsEXSqBOH5E6Ak2YMOuZMxqwYFM7VdOZM2RMq7jyXE17XflcbH06S0rOMnjULAkDCg==