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
- 3ec8adeb0ea7d11f8167f32791f18fd456cc7099ff127d79a2dabdc58257bb1c
- request
- 94147c506c8e5223969a211977d0dfc46961d94ddd20528037cdb278bbf86f67
- transaction
- edf3fd886d84d953ff8dfe1e6f05d630be13a88e80f106e3b71e61080a7804c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57583
the chainentry 57583
- sealed to the entry before
- 4ec64832da8b27ff3f4ea3a6f23a7ce5fe1d5d650f360327989860d6113dc633
- this leaf
- c22347befe6c28b0b40f130801cdafa92efcda3a0c00b1bfbd42dd466a07db4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- voh0pIbhyYxADtFmzfi+FPvSKv3Xct44c+hgC9H2QXBTQzPE8hqcE3XXuD9WpHkW1vJAZ5UU257bgIjdnO/kAQ==