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
- 469cdad3cfecb1ef2fdeca30c79db4a50178d6c225d12ffa799e81c983bf8699
- request
- fe93182786ce705acce454124f9e8056cdd66269a81c984fb2c329ce7cd5851d
- transaction
- 0af0c98c1826c8bbe455e9b21c06af5b3798847903425e38936e4349ea35ddaecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1093
the chainentry 1093
- sealed to the entry before
- 6ffba43ec0e1145867c64508d851f96af36cff3dfd5d3c996e77a6be71b99a93
- this leaf
- 15fa64e706e3682499225e88cd8622c4a8d683c4093c01cfc39496e97ba5ab0e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XTjOQXdCO/H1oG0fiK9/SrixjO270ZfHU4j/4aSF4kc7wuGihM61ydT++x9w8SOhuoTr7w7xVD4ir830og5fCg==