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
- 4c088a41cd464577a29662f862ab6412061c5b7a955d0396296ee4f51d8c46b1
- request
- fe68addb283ec38daa9036878d9eadb83c65f4bb7f3a2871a9a85a105c250f15
- transaction
- 0772546207c82e35e52892252faa4ca60ad6281d51b3d10ed967836c424484ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41977
the chainentry 41977
- sealed to the entry before
- 81071516e49fb5f4a3b956c6299f51d24ad19fb70447ca7ba1ffbb5b6205faa7
- this leaf
- 0d4ac29ad9c06725e4e0ea76358d168b31f7de100c53cb94451ea5cec0b0b9f2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0ZwQ86oyLc9Uxg52BJoqfKkXqBXEfgGf70Bjz6yEEoS7fGbMmYM2hnUVl+CtJW7xq0IEesfGArMGQqTeVgCdDw==