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
- 2c34ed53ef35330def0b7d6ca1772d58b0dee70e0d84b5589cc99af0041ff81c
- request
- 8f6ab7f8d24edccecc1518226a098dfa220e58cd4beebac4fca6cef10f52857a
- transaction
- a0d70ab11133e6f29419d47a4f1177d8f71251e455551031e64a4c967b48ef6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63328
the chainentry 63328
- sealed to the entry before
- dc99ca9a8d3d55a71471970b1bdd273864cc8cb0ac2bb8be5b59d6c784b72e48
- this leaf
- cdb30cbff65e084faa92d8283bbf7ba1840a2760306df6ac03664a38a0a2e696
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cxCNcdW3mYRTqSRXTsxwO8qG4PNsOvaMovM2lLrYyBKqaDvMsU+kv54+pmKSOoRxQSOiIOgVLgKYneJzyXq/Dw==