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
- 3d7305d5ecbe3fb5398e8c7ca784492f5f11e0f0684de6fa2415e762d6b41ed5
- request
- 069c8b36f791726a79b9d28d51686e2d1b5350073e823b5fc01bb2e88e9b83c4
- transaction
- 9b748eea066ce59bfe1e485cb79fa206c2ace5de77ceaeb9f5b298111e11d112computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32841
the chainentry 32841
- sealed to the entry before
- f7badac4f91e9659a79bd4b760c9f2ea6bbe9821755168b8a5f8f1a3f8d90223
- this leaf
- 5acf0c15abd28a1dec635e81630c5f5909df9b33f578ad6966ea3b30d515e7c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9lHirTKB+5ZxXuIQWnzoPF4TZ69T9t+v7A9xnP1PUGCIvER0ZJaXzeZ3pE94aWfttCL3899F2yveRsAETk2hAg==