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
- 9bec3a371dc04e614b20ca197ef0ff7905543f2e6ec87142a0ba3b93037ea163
- request
- c0567702c50bb7a177015b8039295e6938fc1e4b6611a02491686a447604d1ac
- transaction
- 0572ccb31dd20b1c2f920c53ced4bd04281c90a9f59669f9bbfd4b55780ba2ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17564
the chainentry 17564
- sealed to the entry before
- 8e7821d1088c57a645f95cebd315b1e9f7a0a84e20ed43e0c6234b4c097a15bf
- this leaf
- 86fcae261120411bdd06168cca365c9a0cfd27e15ff1d759a09210ccbc64994f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KFi3+2WKFObgXkuTNPrwWNal3A69///RUZgsE2knP4AYBoTyuE7kLFZ01j5CS6s29vdnjv34OD7DJboVnNz8DQ==