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
- d6e9c33ab5492827551bd46cfc52a4313baa4c2793118637d11877a14d5d63b4
- request
- 6cff6d873a8892e1dc951ac2c095ea8b07de30d0d7462fdf535c520cb585d8e7
- transaction
- 2492cae626e1731795b11ceba9eabff6fa07bd54ad551367f6879326e1ee3d1acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72073
the chainentry 72073
- sealed to the entry before
- 940a4ea497bf01dffb898b5aed177d3c646e15ae43901c7524f99ccb4f40420f
- this leaf
- 4975a552b9ac6cbb9c9b7761f4486728f54fb71e95419aca805f103c6fedc6a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +9J+EL/qLRQjhg6im5Hpj5Awnl6Sg6DAmraEcbmXvxzDN89+WImmF0xPNZvSQjtXe9Bcb1/mVkhxB58KOMUeBw==