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
- 29cf14e408cf6075e6fffde44acb919f67afc8fdd97d00f5c2084c0aaf5dbbae
- request
- 62b670054b05622ddda5e3aeeebd7747a735921af14245a858ea9df80570ae02
- transaction
- b356d3e9e4071680ecd389fa9453213db1a10b790d165f3cabf645193b1e2ebecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63075
the chainentry 63075
- sealed to the entry before
- f424c79fffd2b73b5989b5e0a2dd7186b6030a13e4c4897aa17ca67e07a01496
- this leaf
- 4c5137e035c5ba8add831f6188dd8abf42740e642577bd25da097937ea3867a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cGn4z61/UJvZeeD+t/Q69DRKiPNSV3YGexDyd9Hx8Yqwi/e1/nFctroTPSIsQuOAb9iBWFYEGdHLjempiqcEAQ==