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
- ff80b848f4a263a08f6249cff3019e3db58df605e2a97e1f650c7b2840edb9c3
- request
- 187e30325059c8bfbc907330c45596a44fa3887cb8c22cf82c90a8b083f97ee6
- transaction
- 38becbcb116e260319d1a295b09157483bd38361d0e872a0dbad9ac316f1034fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 968
the chainentry 968
- sealed to the entry before
- 89078e0a438595f1579428bbdcadd4d6bf1d4339ae8afb61080ef1cb0d999a75
- this leaf
- a91aaa83f3bf3d5d83b52009f95bd2d9b2773e5e17f47503658721208be008bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N36Wft35kPqmJTn6n4LmFsY/cebMTL0t9kHWrqqUQvM36Kmigmfc5S1RzI9bzzkQ8jS9oj7N/PQfdsOvHYSpCA==