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
- cd8861d86278de5c3bdd05350e506b1576d2d7442600bea917858d7cf5ae4f8e
- request
- c13b268774ef6a5dd9b66ac75cd5f89c6ffbb7adb1a023a5dea042fb90dd7ea3
- transaction
- c92f51ae87e94cd78d44d7e63d33a7e0eab48d86d9eec42c8f67a411a8adcfcfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 466
the chainentry 466
- sealed to the entry before
- 434ce976880f4d71f415d8b12c819a4f743d0276546c359f7965f4a81d42adf7
- this leaf
- 0d4b4286a2e00fe7fec130c9954dba912a13837bc3b601855baee8cac165ddf3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QmtlfxnzD7pFG8VQUpnfiba5gP+W/pWgRp/9RkO0ot4wOdKGMNSnL9UqYrZ9g90LSIZhjmwZZWw3SszV+UcZBQ==