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
- dc1de76c9bb0faabc4d2dc7b1bf170434309b3c4ed9fafa2ce98e9c4c28807bf
- request
- 9c9a93759f4d5cc92ab8e6565b97c31f465caa4f46f212795c03ef9d082a4b9a
- transaction
- f5dda21dbfd27e0ca19f15eda0714111bcfed3075e0df1ed1ca1488260606a1acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34730
the chainentry 34730
- sealed to the entry before
- eb31f67707e062cda09b5846767e89a2ada848e80f8ad0ab52392b63a0429eaa
- this leaf
- c921a17769b92d2f148812bbf53b2fac04f938d7db6be420fa2fb81322c957e6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ij8cWdvlVI7RAOFjFK4wenB/KKwJA8q/f4WwgQMfgzZIhdlIqYyKzjzePplGO5ZfToQmCN1Pd6vs46QihL7qCg==