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
- 02afcf256a9e69444f17845b10be7fa5b0af2c9469d7e32f8e5fa9a8dfd83ca1
- request
- 9d08b843f7fecf5ab4a0c794d408a805f1473cb35b8532c5a246bb90d9d996ee
- transaction
- 4e3b17bbb67450bbc18705012144dad8ee8281c34e8a681f3eab3952ea37f9bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20685
the chainentry 20685
- sealed to the entry before
- 3c4c8bccba7fbcf08ab44b572c5d8f1f381b981c5dc5bd92ecd14ea242c9bf54
- this leaf
- 66b8c721e9ff7667e4bafa8c54118d2e92a0cc11aa2812d3c9248b1ff940df14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SCmeTNaPhQXKdFl4vxWut24VbsRgJdd074O95cQ2FokJnP7DGEepcoqekaeUbLZr6yQPd2G8I8+CP8hyldNUAw==