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
- c419ef43132179667d7a7736dc47ba15b7e893342f86308d1b92591eda2cb8b6
- request
- 80d016a3b083251329dae6d2af891dad65c8c4b2612d2384acb83bfa7bc67d84
- transaction
- 640d8791000c6b823f0982bfd8463cb5913237e03934dce3496479dd63293f9ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 781
the chainentry 781
- sealed to the entry before
- 7c84ff3dd9e7f7bbe923447e0310cbf33cfd20b3f8c0a6f5c62f50b1c6d6ced8
- this leaf
- 8e0a5a178e09139b9e823cb07b3285352207af533f4b1b98caf9805e068c6c1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5R3rrEFZ0GXN2g2zdgwGDynKMtPRlprn/PVPxWKAIZNJilHHH21QWi6eKP3fqxV34x2W5AP0UyTgXlSHJAgDBQ==