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
- 2c11b233accce14b6e7bf1f000e20e88eab08c7b1160ace44ecf566e4195dcb4
- request
- 72851ad9bcaafa5d6562e176fedf983d71763fc2d74ea487b453f0b2f559ffa1
- transaction
- 8fd846756077be4ec978b19a0e150795e470ef4fca148c3f1a3d85cd8ed10e79computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74173
the chainentry 74173
- sealed to the entry before
- a4e85c2c59e5d6655b9982f8bb5f2d6537781e1be6852c67c6658259de267da5
- this leaf
- 20ececa778411dd557432afc4de435b4a2e3167d60b653fd5f283ef43fc83e6f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q/Ap+9+RLubWtm7IAyjZ+QqL1f9geIRO2FM516f3sVRcXXllueTFUckzkkhYl5ov8uxD1TPLmH4WpS7Y/c7/Ag==