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
- 5b3e20d1d1e1ce78102ef8cb701402b2e3ae7f32c88d009465f6d58532d877db
- request
- 8f2b2f9ffae8670bdf713a7dfc71d99d650112b3d323ccf82f04f79a9b361391
- transaction
- a943980903a098961808f50b7878885218414c046594708680f9ffa0a8feef1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2610
the chainentry 2610
- sealed to the entry before
- 9c28c6e0bb295fd8f944dd26d2eae9aaead159136fae829b5e78efaa87309864
- this leaf
- 847afd51562f2b4a42a32722621f820018fecd56f27ffcb6fbb364e67e31290b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CFqPSBX9fzMoGVRkJ98hIyNZXbq+/4m56xKrWIalkWukUtCTylbYHKW5TYqo8YMtWblTfun1FTi9PxBgZMZBDg==