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
- b52726abdf24b9d24cc5a0bdede779f557393edd8bb54fa1ff254466e5108a2a
- request
- efae080ab32821f8ec438508333862b068c15f756e91218e4e391e91fda71975
- transaction
- 0a0f4e2c833679bf4e9888be7c419745e980b4ec9e7ffaad3891f64c199c7fdbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54233
the chainentry 54233
- sealed to the entry before
- 003e61b46978d1b9c06c61dc21efa5764c778f916de429e085a29e53a33f975b
- this leaf
- 35ba1ea9d961edcd7f4448999f970ed9845d4dfb157da1991496dfd07a320ae6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YyYdqNtEgI9VWJxhPtMcKepM5zQuzVxqDGoAFt8b3Yq8utGV6Njh3jKicUBse8vIwf7HkBrp5HB6xe1OZKNVDQ==