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
- 61da9179037f4f2b081abca5df2333e029c42480ce92568dcbfb62caa8df08da
- request
- 62ceb2e6c12eb89e65c4b1459b1265f11443bc40c453f41e24f789c6c4139a57
- transaction
- c9eeb629765ba8bc239052e7178906df4a7d51d44b72db40862ddb778f6f8204computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44569
the chainentry 44569
- sealed to the entry before
- c63cb991012563e77f6fd702cf9f9143ebb5e8e7baa199e886ac3488cf1472ee
- this leaf
- d5753604d4b50ab08b015f7c909eda367112b3a5f7b64bdedc4bfb60fb433c7e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nAq1LElxLpAMCbh9PxZ27TiZQiQb48qIYe/bpgwfAx1SFGkUfCgBKL5TJkJGD0BKZYZMdkt8CA4j+ycI+tB3Bg==